Federating the proxy server node into the cell

After you install the SIP and XMPP proxy server node, you must federate the node into the deployment manager's cell so that the proxy server becomes part of the cluster.

Before you begin

Expected state: The deployment manager is running.

About this task

To federate or add the proxy server node into the cell, you run the addnode command on the proxy server node and specify the hostname of the deployment manager.

For additional information about default paths, see Directory conventions.

Procedure

Log into the proxy server node's operating system.
IBM i only: On the command line, run the STRQSH (Start Qshell) command.
Synchronize the system clocks on the deployment manager and the proxy node so that they are within five minutes of one another and are set for the same time zone.
Federation fails if the clocks are not synchronized within five minutes of each other.
On the proxy server node, open a command window and navigate to the profile_root\bin directory.
IBM i only: Run the following command to obtain the SOAP_CONNECTOR_ADDRESS port number. Make a note of the port number as you will need it to add nodes to the cluster:
```
dspwasinst
```
Run the following command to add the proxy server node to the deployment manager's cell:
Linux™
```
./addNode.sh DM_server_host_name DM_port_number -includeapps
```
Windows™
```
addNode.bat DM_hostname DM_port_number -includeapps
```
where:
- DM_server_host_name is the resolvable host name of the deployment manager.
- DM_SOAP_portis the port that the deployment manager's SOAP port is listening on.
- WAS_Admin_user_name_on_DM is the user ID of the WebSphere® Application Server administrator account on the deployment manager.
- WAS_Admin_password_on_DM is the password associated with the WebSphere Application Server administrator account.
For example:
```
addNode gateway_dm.example.com 8879 -includeapps -username wasadmin -password waspassword
```
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 MyProxyNode has been successfully federated.
```
Verify that the proxy servers are installed correctly:
1. Log into the Integrated Solutions Console.
  If you already logged in, you must log out and then log in again before you can see changes.
2. Click Servers > Server Types > WebSphere proxy servers and verify that the SIP proxy server appears in the list.
3. Click Servers > Server Types > WebSphere application servers and verify that the XMPP proxy server appears in the list.