Starting and Shutting Down

The engine portion of SIP Servlet Engine (SIP servlet container) is closely linked with WebLogic Server, and its life cycle is also synchronized with the instance of WebLogic Server. Accordingly, if WebLogic Server is started, SIP Servlet Engine is also started. When WebLogic Server is shut down, SIP Servlet Engine is also shut down.

SIP Servlet Engine 3.0 implements this feature by making use of the Startup Class and the Shutdown Class of WebLogic Server.

For details of startup and shutdown classes, see here.

Starting SIP Servlet Engine

As has been described above, SIP Servlet Engine starts up automatically by starting up WebLogic Server. However, a startup script is provided, for the following reasons.

• It is necessary to set the class to be used for startup of SIP Servlet Engine explicitly as CLASSPATH environment variable.
• To specify the files for setting log output and security.

The following four scripts are provided. Choose the one that matches the server to be started up. These files are all located in the same directory as startWebLogic.sh, as shown below.

$WL_HOME/user_projects/domain/mydomain

Here, mydomain refers to the domain name specified for installation.

For details of starting the administration server, see "Administration Console Online Help: Starting Administration Servers."

Also, for details of starting the managed server, see "Administration Console Online Help: Starting Managed Servers From a WebLogic Server Script."

There are also various other ways for starting WebLogic Server. When starting with method other than one of the above, the same settings as specified in the script should be explicitly specified.

Shutting Down SIP Servlet Engine

The method of shutting down CenterStage-AP conforms to the method of shutting down WebLogic Server.

For details, see "Administration Console Online Help: Shutting Down Instances of WebLogic Server."