The following sections describe how to start and stop servers in a WebLogic SIP Server domain:
Note: | WebLogic SIP Server start scripts use default values for many JVM parameters that affect performance. For example, JVM garbage collection and heap size parameters may be omitted, or may use values that are acceptable only for evaluation or development purposes. In a production system, you must rigorously profile your applications with different heap size and garbage collection settings in order to realize adequate performance. See “Tuning JVM Garbage Collection for Production Deployments” on page C-1 for suggestions about maximizing JVM performance in a production domain. |
WARNING: | When you configure a domain with multiple engine and data tier servers, you must accurately synchronize all system clocks to a common time source (to within one or two milliseconds) in order for the SIP protocol stack to function properly. See Configuring NTP for Accurate SIP Timers in the Configuration Guide for more information. |
Because a typical WebLogic SIP Server domain contains numerous engine and data tier servers, with dependencies between the different server types, you should generally follow this sequence when starting up a domain:
startAdminServer.cmd
script installed with the Configuration Wizard, or a custom startup script.
You generally start each data tier server by using either the startManagedWebLogic.cmd
script installed with the Configuration Wizard, or a custom startup script. startManagedWebLogic.cmd
requires that you specify the name of the server to startup, as well as the URL of the Administration Server for the domain, as in:
startManagedWebLogic.cmd datanode0-0 t3://adminhost:7001
startManagedWebLogic.cmd
script or a custom startup script.Following the above startup sequence ensures that all Managed Servers use the latest SIP Servlet container and data tier configuration. This sequence also avoids engine tier error messages that are generated when servers in the data tier are unavailable.
The Administration Server in a WebLogic SIP Server 2.0.2 installation is required only for configuring, deploying, and monitoring J2EE services and applications; all SIP container configuration is performed using the container's sipserver.xml
configuration file.
Note: | If an Administration Server fails due to a hardware, software, or network problem, only management, deployment, and monitoring operations are affected. Managed Servers do not require the Administration Server for continuing operation; J2EE applications and SIP features running on Managed Server instances continue to function even if the Administration Server fails. |
BEA recommends the following best practices for configuring Administration Server and Managed Server instances in your WebLogic SIP Server domain:
Should an Administration Server instance or machine fail, remember that only configuration, deployment, and monitoring features are affected, but Managed Servers continue to operate and process client requests. Potential losses incurred due to an Administration Server failure include:
To resume normal management activities, restart the failed Administration Server instance as soon as possible.