On the new host, ensure the Appendix B, Prerequisites have been followed.

On all existing nodes, update the /etc/tungsten/tungsten.ini configuration file adding the new host to the list of connectors.

shell> vi /etc/tungsten/tungsten.ini

[alpha]
...
connectors=host4

Run the tpm command to update the software with the INI-based configuration:

shell> tpm query staging
tungsten@db1:/opt/continuent/software/tungsten-clustering-7.0.3-141

shell> echo The staging DIRECTORY is `tpm query staging| cut -d: -f2`
The staging DIRECTORY is /opt/continuent/software/tungsten-clustering-7.0.3-141

shell> cd {STAGING_DIRECTORY}

shell> ./tools/tpm update --no-connectors

For information about making updates when using an INI file, please see Section 10.2.4, “Configuration Changes with an INI file”.

Using the --no-connectors option updates the current deployment without restarting the existing connectors.

During a period when it is safe to restart the connectors:

shell> ./tools/tpm promote-connector

Copy the /etc/tungsten/tungsten.ini from an existing node to the new connector being configured.

Install the Tungsten Cluster package or download the Tungsten Cluster tarball, and unpack it on the new Connector host:

shell> cd /opt/continuent/software
shell> tar zxf tungsten-clustering-7.0.3-141.tar.gz

Change to the Tungsten Cluster directory:

shell> cd tungsten-clustering-7.0.3-141

Run tpm to validate the installation. Providing no errors are return, you can then continue to install the software.

shell > ./tools/tpm validate
shell > ./tools/tpm install

If your connectors are using Proxy, you will need to copy the user.map file from an existing connector to ensure aiuthentication of clients succeeds

If you supplied start-and-report=true the software will be running, if this wasn't included, you can now start the software as follows:

shell > connector start