Integrate the SIP on demand router with Load Balancer

Integrate the SIP on demand router with Load Balancer

We can integrate the Session Initiation Protocol(SIP) on demand router (ODR) with Load Balancer. Load Balancer for IBM WAS can help maximize the potential of the website by providing a powerful, flexible, and scalable solution to peak-demand problems.

(zos) Restriction: Intelligent Management does not support SIP features on the z/OS operating system.
Install Load Balancer for IBM WebSphere Application Server. See the Edge Components Information Center for installation information.
The SIP ODR is stabilized, and is currently not recommended. Use the SIP proxy server instead.gotcha
Start the Load Balancer.

From the command prompt, type dsserver start.

Then type lbadmin to start the console for the Load Balancer.

From the console, right click Dispatcher, and then select Connect to host.

Right click the hostname and select Start executor.

Start the configuration wizard for the load balancer. Right-click Dispatch > Start configuration wizard.

Select default host.

Type a cluster address. The cluster address is not available before the executor starts. Specify this same value for host when creating a user-defined port.

Type a port number, such as 5060.

Add servers to the port. Add each server to which the load balancer will proxy traffic. In the configuration, the load-balanced server is the ODR server for the WAS configuration.

Start an advisor by clicking Yes. For example, for HTTP traffic, start the HTTP advisor. For SIP traffic, start the SIP advisor. The advisor tells the manager whether a specific port is accepting traffic.
Alias the cluster address on the SIP on demand router loopback adapter. For example, type lb-alias.sh cluster_ip_address:
#!/bin/sh  CLUSTER=$1
 if [ -f /proc/sys/net/ipv4/conf/all/arp_ignore -a -f /proc/sys/net/ipv4/conf/all/arp_announce ]
then echo Using arp_ignore
echo "3" >/proc/sys/net/ipv4/conf/all/arp_ignore
echo "2" >/proc/sys/net/ipv4/conf/all/arp_announce
ip addr add $CLUSTER/32 scope host dev lo
elif [ -f /proc/sys/net/ipv4/conf/all/hidden -a -f /proc/sys/net/ipv4/conf/lo/hidden ]
then echo Using hidden echo "1" > /proc/sys/net/ipv4/conf/all/hidden
echo "1" > /proc/sys/net/ipv4/conf/lo/hidden
ip addr add $CLUSTER/32 dev lo
elif [ ! -z "$( which arptables )" ]
then echo Using arptables
arptables -A IN -s $CLUSTER -j DROP
arptables -A OUT -s $CLUSTER -j mangle --mangle-ip-s $(hostname)
ip addr add $CLUSTER/32 dev lo
else
echo Using iptables
iptables -t nat -A PREROUTING -d $CLUSTER -j REDIRECT
fi
Load Balancer Administration Guide for more information.

Define SIP ODR custom properties from the Intelligent Management console.

From the console, click Servers > Server types > On demand routers > odr_name > SIP on demand router settings.

Under General Properties, in the Additional Properties section, click Custom properties.

Create the following SIP ODR custom properties:

LBIPAddr : The IP address of the load balancer machine.

SIPAdvisorMethodName: The type of messages sent by the Load Balancer advisory. This name is INFO.

serverUDPInterface: The IP address of the server machine.

serverUDPPort : Specify an unused port number. For example, 5080.

udp.IPSprayer.host: You specified this value in step 2b.

Create a user-defined port from the Intelligent Management console.

From the console, click Servers > Server types > On demand routers > on_demand_router > Communications > > Ports.

Click New.

Select User-defined port.

Enter SIP_LB_Address for the Port name.

Enter a value for the Host. You specified this value in step 2b.

Enter a value for the Port. You specified this value in step 2c. Click OK. Save changes.

Under Ports, modify the PROXY_SIP_ADDRESS from * to the actual host name of the proxy server machine.

Click Apply, and then click Save.

Modify the SIP on demand router transports.

From the console, click Servers > Server types > On demand routers > odr_name > SIP on demand router settings > SIP on demand router transports > UDP_SIP_PROXY_CHAIN > UDPInbound Channel (UDP_1).

From the Port drop-down list, select SIP_LB_Address.

Click Apply, and then click Save.

Verify that the host name of the ODR machine is set for the PROXY_SIP_ADDRESS. To verify from the console, click Servers > Server types > On demand routers > odr_name > Communications > Port > PROXY_SIP_ADDRESS.

Create a UDP transport chain. Click Servers > Server types > On demand routers > odr_name > SIP on demand router settings > SIP on demand router transports > New.

Type a name for the new chain, such as ODR_SIP_PROXY_CHAIN.

In the drop-down list, select Proxy-UDP.

Click Next.

Select Use existing port and PROXY_SIP_ADDRESS. Click Next and then Finish on the summary page. If PROXY_SIP_ADDRESS does not show in the list of existing ports, select any of the ports to complete the transport chain creation, then modify the UDP inbound channel of the new chain. Select the new transport chain, then select the UDP inbound channel and change the port to PROXY_SIP_ADDRESS.

Create a TCP transport chain. Click Servers > Server types > On demand routers > odr_name > SIP on demand router settings > SIP on demand router transports > New.

Type a name for the new chain, such as TCP_SIP_PROXY_CHAIN.

In the drop-down list, select SIP_LB_Address.

Click Next and then Finish on the summary page.

Restart the ODR to pick up the changes.

Create a system property named clientUDPInterface on each ODR and set it to the IP address of the cluster address. To create the system property, select Servers > Server types > On demand routers > odr_name > Java and process management > Process definition > Java Virtual Machine > Custom properties > New.

Save and synchronize the configuration.

Restart the ODR.
Related concepts

Overview of request flow prioritization

Related tasks

Create ODRs
Configure a Web server as a trusted proxy server
Install a Session Initiation Protocol proxy server

Related information:

Intelligent Management: on demand router system and custom properties