Federating a primary or secondary node running on Windows™ to an IBM® Sametime® Bandwidth
Manager cluster allows a central point of administration for the network
deployment.
Before you begin
Expected state: the deployment manager is running.
About this task
Follow these steps to federate a primary or secondary node
to a Bandwidth Manager cluster.
Procedure
- Set the system clock to exactly the same time as the deployment
manager's system clock.
- Ping the deployment manager node from the node to make
sure the host name is resolvable.
- On the node, open a command window and navigate to the
bwm_profile_root\bin
directory.
- Run the following command, according to platform, to add
the node to the deployment manager's cell:
Windows:
addNode.bat DM_hostname DM_port_number -includeapps
For
example:
addNode.bat bwm_dm.example.com 8879 -includeapps
Linux:
addNode.sh DM_hostname DM_port_number -includeapps
Where DM_hostname is
the host name of the deployment manager server.
Port 8879 is
the default port on which the deployment manager listens.
Note: After
upgrading, the default port on which the deployment manager listens
changes. The list of default ports can be found in the file for the
deployment manager profile.
Windows:
bwm_profile_root\logs\AboutThisProfile.txt
Linux:
/bwmprofile/logs/AboutThisProfile.txt
For
example,
/opt/IBM/WebSphere/AppServer/profiles/Appsrv01/logs/AboutThisProfile.txt
- When prompted, provide the deployment manager's administrative
user ID and password. Click OK.
Wait
for the operation to complete before proceeding. Look for a success
message similar to the following when complete:
Node ServerNode has been successfully federated.
- To verify that the node has joined the deployment manager's
cell, log into the deployment manager's Integrated Solutions Console
using your administrative user ID and password. The URL for the deployment
manager is http://server name:9060;ibm/console
Note: In the deployment manager's URL, the port for https is
9040.
Click Log in.
- Click . Confirm that 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.
- If your configuration contains more than one WebSphere® proxy server, federate the additional WebSphere proxy servers. Complete
steps 1 - 7 for each WebSphere proxy
server in your configuration.