Adding ports to the virtual host alias

After creating a Sametime® Media Manager SIP Proxy/Registrar cluster, add the SIP ports of each cluster member to the virtual host alias. This step is required.

Before you begin

Create a cluster of SIP Proxy/Registrar components. Adding the SIP ports of each cluster member to the virtual host alias is required to ensure that the cluster operates properly.

About this task

On the cluster's deployment manager (the Sametime System Console), update the sip_proxyreg_host virtual host with a unique set of web access ports. Such a configuration lets a single host computer resemble multiple host computers.

Tip: Print this page and use the table to record the port settings as you look them up in steps 1 and 2:

Table 1. Write down the port numbers used for these settings in every cluster member
	SIP_ DEFAULTHOST	SIP_DEFAULTHOST_ SECURE	PROXY_SIP_ ADDRESS	PROXY_SIPS_ ADDRESS
Cluster member 1
Cluster member 2
Cluster member 3
Cluster member 4
Cluster member 5

Procedure

Determine the ports used by every cluster member:
1. On the computer where the deployment manager is installed, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
  Note: Typically, the Sametime System Console serves as the deployment manager.
2. Click Servers > Server Types > WebSphere application servers.
3. In the table listing the servers, click the name of the cluster member.
  This displays the cluster member's "Configuration" page.
4. On the "Configuration" page, look under "Communication", and expand Ports.
5. Look in the Ports table and write down the following port settings for use in the next step:
  - SIP_DEFAULTHOST
  - SIP_DEFAULTHOST_SECURE
6. Repeat this process for every cluster member.
Next, determine the ports used by every WebSphere® proxy server that operates with this cluster.
1. In the deployment manager's (the Sametime System Console) Integrated Solutions Console, click Servers > Server Types > WebSphere proxy servers.
2. In the table listing the servers, click the name of the WebSphere proxy server.
  This displays the cluster member's "Configuration" page.
3. On the "Configuration" page, look under "Communication", and expand Ports.
4. Look in the Ports table and write down the following port settings for use in the next step:
  - PROXY_SIP_ADDRESS
  - PROXY_SIPS_ADDRESS
5. Repeat this process for every WebSphere proxy server used by the cluster.
Now add the ports used by all the cluster members and all of the WebSphere proxy servers to the deployment manager's Virtual Hosts table.
1. Now return to the Integrated Solutions Console navigation tree and click Environment > Virtual Hosts.
2. In the Virtual Hosts table, click the host called sip_proxyreg_host.
  This displays the "Configuration" page for the sip_proxyreg_host.
3. Under "Additional Properties", click Host Aliases.
4. In the "Host Aliases" table, add the ports used by all of the cluster members (the information you collected in Steps 1 and 2):
  Remember that you have information on the two ports for each cluster member; however if a port is already listed in the table, you do not need to add it again.
  To add a port:
  1. Click the New button at the beginning of the table.
  2. In the Host Name field, type *.
  3. In the Port field, type a port from your list.
  4. Click OK.
  5. Repeat this for the two ports for every cluster member (unless a port is already listed in this table).
5. Now delete all of the table entries that do not use * as the Host Name.
  To delete an entry, click on the check box preceding it, and then click the Delete button at the beginning of the table.
6. Save the new port settings to the master configuration and synchronize the nodes in the cluster:
  WebSphere Application Server displays a message prompting you to save changes to the master configuration. Click Preference > Synchronize nodes option before clicking the Save button.