2.9. Installing Additional Servers for High Availability
At a minimum, additional servers must be installed with the same SQL database information as the first JBoss ON server instance. The rhq-server.properties file must be edited to use the same database configuration as the original instance; the database properties are listed in Section 2.6.2, “Attributes in the Properties File”. After editing the properties file for the database settings, the server can be installed as normal:
[root@server ~]# serverRoot/jon-server-3.2.0.GA/bin/rhqctl.sh install --start
With the default install command, a server, agent, and storage node are installed. In some high availability deployments, a storage node may not be installed with every server. In that case, the configuration for the existing storage node must be added to the server configuration as part of its installation process.
- On the original server machine, check the Administration >Storage Nodes area for the list of IP addresses or hostnames for the storage nodes and for the client and gossip ports used by the nodes.
- On the new server machine, before installing the server, edit the
rhq-server.propertiesfile to include the connection information for the storage nodes.Add each storage node in a comma-separated listed to therhq.storage.nodesparameter. Then, add the client and gossip port values.[root@server ~]# vim serverRoot/jon-server-3.2.0.GA/bin/rhq-server.properties rhq.storage.nodes=192.68.0.0,192.68.0.1,192.68.0.2 rhq.storage.cql-port=9142 rhq.storage.gossip-port=7100
- Install the server and an agent. Specifying the
--serverand--agentoptions only installs those two components; the storage database is excluded.[root@server ~]# serverRoot/jon-server-3.2.0.GA/bin/rhqctl.sh install --server --agent --start

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.