Configure an IBM
® proxy server to perform routing and caching tasks for a cluster of IBM Sametime
® servers running on WebSphere
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
- Meeting Server
- Conference Manager
- SIP Proxy and Registrar
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.
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.
- Log in to the Deployment Manager's (the Sametime System Console) Integrated Solutions Console as the WebSphere administrator.
- In the navigation tree, click Servers -> Server Types -> WebSphere proxy servers.
- In the proxy servers table, click the New button at the top of the table.
- In the "Create a new proxy server entry" dialog box, do the following:
- 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.
- Type a name for the new proxy server; for example "was_proxy1", and then click Next.
- In the "Specify server specific properties" box, select the appropriate "Support protocol" settings for your cluster, select Generate unique ports, and then click Next.
In the "Select a server template" box, select proxy_server_foundation (the WebSphere Default Proxy Server Template), and then click Next.
In the "Confirm new server" box, click Finish.
- If you are configuring this WebSphere proxy server for a Meeting Server cluster: deselect the SIP protocol.
- If you are configuring this Sphere proxy server for a SIP Proxy and 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.
Save the changes by clicking the Save link in the "Messages" box at the top of the page.
Resynchronize the nodes:
(Conference Manager cluster, SIP Proxy and Registrar cluster) Assign the new proxy server to the cluster:
- On the Deployment Manager, log in to the Integrated Solutions Console as the WebSphere administrator.
- Click System Administration -> Nodes.
- Select all of the nodes in the cluster.
- Click Full Resynchronize.
Now start the new WebSphere proxy server:
- Click Servers -> Server Types -> Websphere proxy servers -> proxy_server_name -> SIP Proxy Server Settings -> SIP proxy settings.
- In the "Default cluster" field, select the cluster that you are configuring this WebSphere proxy server to work with.
- Click Apply.
- Save the changes by clicking the Save link in the "Messages" box at the top of the page.
Parent topic: Setting up a WebSphere proxy server for the Conference Manager cluster
Previous topic: (Optional) Adding a stand-alone WebSphere proxy server to the Conference Manager cluster
Next topic: Adding ports to the Deployment Manager's virtual host alias
- Again in the Integrated Solutions Console's navigation tree, click Servers -> Server Types -> Websphere proxy servers.
- In the "WebSphere proxy servers" page, select the new proxy server from the list.
- Click the Start button above the list of proxy servers.