Add the primary node to the IBM® Sametime® Gateway deployment
manager's cell. Federating the primary node enables you to administer
it through the deployment manager's IBM WebSphere® Integrated Solutions
Console. You will not be able log into the primary node's Integrated
Solutions Console after this step.
Procedure
- Make sure that the system clocks on the deployment manager
and the primary node are within five minutes of each other and are
set for the same time zone.
Federation fails if the
clocks are not synchronized within five minutes.
- Ping the deployment manager node from the primary node
to make sure the host name is resolvable.
- On the primary node, open a command window and navigate
to the
profile_root\bin
directory.
If the deployment manager and the primary node are installed on the
same computer, the default profile directory is RTCGW_Profile1 (not
RTCGW_Profile). - Run the following command to add the primary node to the
deployment manager's cell:
addNode.bat DM_hostname DM_port_number -includeapps
Where DM_hostname is
the host name of the deployment manager server. For example:
addNode.bat gateway_dm.example.com 8879 -includeapps
Port
8879 is the default port on which the deployment manager listens.
- When prompted, provide the deployment manager's administrative
user ID and password.
Wait for the operation to
complete before proceeding. Look for a success message similar to
the following when complete:
Node MyserverNodePrimary has been successfully federated.
- To verify that the primary node has joined the deployment
manager's cell, log into the deployment manager's Integrated Solutions
Console as the WebSphere administrator
and click . Make sure you can see the primary
node's information.
If you already logged in, you must
log out and then log in again before you can see changes.