Installing an additional Sametime server as a secondary node

Install an IBM® Sametime® product server as a secondary node. The product you install as the basis for the IBM WebSphere® proxy server must match the product used by the cluster it will serve.

About this task

The first stage in deploying a stand-alone IBM WebSphere Proxy Server is to create a deployment plan for a secondary node, and then use the Sametime System Console to install a new Sametime server. You must install the same product that is used in the cluster. For example, if you are installing a WebSphere Proxy Server to operate with a cluster of Sametime Meeting Servers, then your first task is to install a Sametime Meeting Server using the secondary node option so it can be federated to System Console. Later you will remove the Sametime Meeting Server software from the node, leaving only the underlying WebSphere Proxy server functionality.

Attention: To upgrade a stand-alone WebSphere proxy server that was installed using this process, you must run a newer Sametime installation for the original Sametime component. Because the Sametime application was removed during the initial installation of the stand-alone proxy server, it cannot be found during the upgrade, and the upgrade fails. To work around this issue you will need to temporarily recreate the Sametime application in the WebSphere Integrated Solution Console and assign it to the node being upgraded. After the upgrade successfully completes, you can remove the Sametime application. For detailed steps on resolving this upgrade issue, see the IBM TechNote Issue while upgrading a stand-alone WebSphere proxy server using the Sametime installation program.