Configuring a WebSphere proxy server for the cluster

Configure an IBM® WebSphere® proxy server to perform routing and caching tasks for a cluster of IBM Sametime® Bandwidth Managers. This task is required regardless of where you install the WebSphere proxy server.

Before you begin

Create a cluster of Sametime Bandwidth Managers running on WebSphere Application Server; start the deployment manager as well as all node agents and application servers in the cluster. .

If you are configuring the proxy server on a dedicated computer, note that an IBM Sametime Bandwidth Manager cluster supports two IBM WebSphere Application Server nodes. Even if you think you only need one node, you should install two nodes now and federate them to the cell. Attempting to add a second federated node later might result in lost data. You can optionally host the secondary node on the same computer as the cluster's primary node.

About this task

A cluster uses a WebSphere proxy server to manage routing and caching tasks. To ensure redundancy in the case of a proxy server failure, you might want to configure multiple proxy servers for the cluster. You can host a WebSphere proxy server on any node in the cluster but because it uses a lot of system resources, you might want to host it on a dedicated computer.
Note: If you install multiple WebSphere proxy servers, you will need a load balancer to divide the incoming load among the proxy servers. For information abut installing the IBM Load Balancer, see the topic Installing IBM Load Balancer.

Procedure

  1. If this proxy server is installed on a dedicated computer, set the system clock to exactly the same time as the deployment manager's system clock.
  2. Log in to the deployment manager's Integrated Solutions Console as the WebSphere administrator.
  3. In the navigation tree, click Servers > Server Types > WebSphere proxy servers.
  4. In the Proxy servers table, click the New button at the beginning of the table.
  5. On the Create a new proxy server entry page, do the following:
    1. In the Select a node list, select the node that will host the WebSphere proxy server.

      Be sure to select a node that belongs to the Bandwidth Manager cluster. This is the WebSphere proxy server node that was created in the Bandwidth Manager cluster when the WebSphere proxy server was federated into the Deployment Manager.

    2. Type a descriptive name for the new proxy server (for example, BWMproxy1).
    3. Click Next.
  6. On the Specify server specific properties page, do the following:
    1. Select both HTTP and SIP protocols for your cluster.
    2. Select Generate unique ports.
    3. Click Next.
  7. On the Select a server template page, select proxy_server_foundation (the WebSphere Default Proxy Server Template), and then click Next.
  8. On the Confirm new server page, click Finish.

    This message displays: New server is created successfully.

  9. Click Apply and then click the Save link in the Messages box at the beginning of the page.
  10. Synchronize the nodes in the cluster:
    1. Click System Administration > Nodes.
    2. Select both nodes, and then click Full Resynchronization.
  11. Assign the new proxy server to the cluster:
    1. In the navigation tree, click Servers > Server Types > Websphere proxy servers.
    2. Select the proxy_server_name.
    3. Click SIP Proxy Server Settings > SIP proxy settings.
    4. In the Default cluster field, select the Bandwidth Manager cluster that you are configuring this WebSphere proxy server to work with. Click OK.
    5. Click Apply and then save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
  12. Synchronize the nodes in the cluster:
    1. Click System Administration > Nodes.
    2. Select both nodes, and then click Full Resynchronization.
  13. Start the new proxy server:
    1. Again in the navigation tree, click Servers > Server Types > WebSphere Proxy Servers.
    2. On the Proxy Servers page, select the new proxy server from the list.
    3. Click the Start button at the beginning of the table.
  14. Refresh the server status by clicking Status.
  15. If you have more than one WebSphere proxy server in your configuration. repeat this procedure for each WebSphere proxy server.