Load balancing with the Session Initiation Protocol proxy server
Load Balancer for IBM WAS can help maximize the potential of your Web site by providing a powerful, flexible, and scalable solution to peak-demand problems. The Session Initiation Protocol (SIP) proxy server must be running before completing these steps.
Procedure
- In the Load Balancer console, view the load balancer configuration panel and configure the cluster address and the address in which incoming traffic that is directed to the backend servers is received.
- Include the servers that the Load Balancer will proxy traffic to in the load balancer configuration. Complete this task by adding servers to the predefined cluster. In the configuration, the load-balanced server is the proxy server for your WAS configuration.
- For the servers that are associated with the cluster, (for instance, the proxy server), alias the address for the predefined cluster to the loopback adapter for that server.
- To ensure that the servers are up and healthy, start the manager on the Load Balancer. When the manager starts, also start the advisor. For example, for HTTP traffic, start the HTTP advisor. For SIP traffic, start the SIP advisor. The advisor tells the manager whether or not a certain port (a user-defined port) is accepting traffic.
- In the console, click Servers > Proxy Servers > proxy server name > SIP Proxy Server Settings > SIP proxy settings.
- A configuration console that details the general properties for the SIP Proxy displays.
- Select Enable TCP sprayer, Enable SSL sprayer, and Enable UDP sprayer, and enter the host and port information for your load balancer.
- Click Apply.
- Restart the proxy server to save your changes.
Related tasks
Installing a Session Initiation Protocol proxy server