Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Session Initiation Protocol (SIP) applications > Administer SIP applications > Configure the SIP container
Performing controlled failover of SIP applications
We can take an active application out of the loop via a controlled failover.
SipContainerMBean is used to initiate a server quiesce through wsadmin (command line interface). This MBean is used to set the container's weight to 0, which prevents new messages from being routed to it.
WAS PMI is used to monitor the server's active sessions. The remaining active sessions can be watched by enabling a counter on the server being quiesced. The server can be shut down once the number of active sessions reaches an acceptable level. A script can be written to monitor active sessions and shut down the server when an acceptable threshold is achieved.
Quiescing a single server
- On an ND machine, start the wsadmin utility:
- Go to <nd_installation_path>/bin
- Run the command: ./setupCmdLine.sh
- Run the command: ./wsadmin.sh
- Verify that received: wsadmin>
- Run the command: set scBean [$AdminControl queryNames type=SipContainerMBean,process= <server name>,*]
- Run the command: $AdminControl invoke $scBean quiesce true
From the admin console, command line or scripts
Use the following commands to stop application servers from the admin console, command line or scripts:
- Stop: Quiesces the application server. The sessions will failover to another server. It is important to manually quiesce the server on shutdown.
- Immediate Stop: Stops the server, but bypasses the normal server quiesce process that supports in-flight requests to complete before shutting down the entire server process. This shutdown mode is faster than the normal server stop processing, but some application clients can receive exceptions.
- Terminate: Deletes the application server process. Use this if immediate stop fails to stop the server.