3.10. Installing Additional Servers for High Availability

JBoss ON can be configured to run in a high availability cloud by configuring multiple server instances which all use the same SQL database backend. Because all of the servers share a backend, they all have the same set of data and inventory to use and all communicate with the same agents.

Installing an Additional Server with an Agent and Storage Node

  1. 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 3.6.2, Section 3.6.2, “Attributes in the Properties File”.
  2. The rhq-server.properties file must be edited to use unique jboss.tx.node.id values.
    Important
    All JON servers in HA environment must be configured to use unique jboss.tx.node.id values.
  3. After editing the properties file for the database and HA identifier settings, the server can be installed as normal:
    [jsmith@server ~]# serverRoot/jon-server-3.3.2.GA/bin/rhqctl install --start

Installing an Additional Server with a Separate Storage Node

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.

  1. Additional servers must be installed with the same SQL database information as the first JBoss ON server instance. Edit the rhq-server.properties file to use the same database configuration as the original instance; the database properties are listed in Section 3.6.2, Section 3.6.2, “Attributes in the Properties File”.
  2. Edit the rhq-server.properties file to use unique jboss.tx.node.id values.
    Important
    All JON servers in the same HA environment must be configured to use unique jboss.tx.node.id values.
  3. 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.
  4. On the new server machine, before installing the server, edit the rhq-server.properties file to include the connection information for the storage nodes.
    Add each storage node in a comma-separated listed to the rhq.storage.nodes parameter. Then, add the client and gossip port values.
    [jsmith@server ~]# vim serverRoot/jon-server-3.3.2.GA/bin/rhq-server.properties
    
    rhq.storage.nodes=192.168.0.1,192.168.0.2,192.168.0.3
    rhq.storage.cql-port=9142
    rhq.storage.gossip-port=7100
  5. Install the server and an agent. Specifying the --server and --agent options only installs those two components; the storage database is excluded.
    [jsmith@server ~]# serverRoot/jon-server-3.3.2.GA/bin/rhqctl install --server --agent --start