Configuring a WebSphere proxy server

Configure an IBM® WebSphere® proxy server to perform routing and caching tasks for a cluster of IBM Sametime® servers running on WebSphere Application Server.

Before you begin

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

Use these instructions to configure a WebSphere proxy server that operates with the following Sametime server clusters:

  • Meeting Server
  • Conference Manager
  • SIP Proxy/Registrar
  • SIP Edge Proxy

About this task

A cluster of Sametime servers that run on WebSphere Application Server can use a WebSphere proxy server to manage routing and caching tasks. To ensure redundancy in the case of a proxy server failure, you may want to configure multiple proxy servers for the cluster. Use a Load Balancer in that case to divide the incoming load between the proxy servers. You can host a WebSphere proxy server on any node in the cluster (except the Sametime System Console) but because it uses a lot of system resources, you may want to host it on its own computer.
Note: If you install multiple WebSphere proxy servers, you will need a Load Balancer to divide the incoming load among the proxy servers. Installing IBM Load Balancer is discussed later in this section.

Procedure

  1. Log in to the deployment manager's (the Sametime System Console) Integrated Solutions Console as the WebSphere administrator.
  2. In the navigation tree, click Servers > Server Types > WebSphere proxy servers.
  3. In the proxy servers table, click the New button at the beginning of the table.
  4. In the "Create a new proxy server entry" dialog box, do the following:
    1. In the "Select a node" box, select the node that will host the WebSphere proxy server.

      Be sure to select a node that belongs to the appropriate cluster.

    2. Type a name for the new proxy server; for example "was_proxy1", and then click Next.
    3. In the "Specify server specific properties" box, select the appropriate "Support protocol" settings for your cluster, select Generate unique ports, and then click Next.
      • If you are configuring this WebSphere proxy server for a Meeting Server cluster: deselect the SIP protocol.
      • If you are configuring this WebSphere proxy server for a SIP Proxy/Registrar cluster: accept both HTTP and SIP protocols.
      • If you are configuring this WebSphere proxy server for a Conference Manager cluster: accept both HTTP and SIP protocols.
      • If you are configuring this WebSphere proxy server for a SIP Edge Proxy cluster: accept both HTTP and SIP protocols.
    4. In the "Select a server template" box, select proxy_server_foundation (the WebSphere Default Proxy Server Template), and then click Next.
    5. In the "Confirm new server" box, click Finish.
  5. Save the changes by clicking the Save link in the "Messages" box at the beginning of the page.
  6. Resynchronize the nodes:
    1. On the deployment manager, log in to the Integrated Solutions Console as the WebSphere administrator.
    2. Click System Administration > Nodes.
    3. Select all of the nodes in the cluster.
    4. Click Full Resynchronize.
  7. (Conference Manager cluster, SIP Proxy/Registrar cluster, SIP Edge Proxy cluster) Assign the new proxy server to the cluster:
    1. Click Servers > Server Types > Websphere proxy servers > proxy_server_name > SIP Proxy Server Settings > SIP proxy settings.
    2. In the Default cluster field, select the cluster that you are configuring this WebSphere proxy server to work with.
    3. Click Apply.
    4. Save the changes by clicking the Save link in the "Messages" box at the beginning of the page.
  8. Now start the new WebSphere proxy server:
    1. Again in the Integrated Solutions Console's navigation tree, click Servers > Server Types > Websphere proxy servers.
    2. In the "WebSphere proxy servers" page, select the new proxy server from the list.
    3. Click the Start button.