Stopping and Starting the Siebel Application Container

If it is deemed necessary, then you can stop (shut down) and restart the Siebel application container using the methods in this topic. The application container for Siebel Gateway, Siebel Server (for Configuration Agent), Siebel Application Interface, and any other application container hosting Siebel CRM functionality are automatically started after installation. If application containers are not running, then you can perform the manual tasks listed in the troubleshooting sequence shown in this topic.

Application containers (Apache Tomcat) provided in installations of Siebel Gateway, Siebel Server (Configuration Agent), and Siebel Application Interface run as a service on Microsoft Windows, while the corresponding system process is named tomcat8.exe. On UNIX operating systems, the system process for Apache Tomcat is named javaw.

Note the following behavior for Microsoft Windows and for UNIX operating systems:

On Microsoft Windows, when the computer restarts, for each applicable Siebel CRM installation, the Siebel Gateway system service (Siebel Gateway Name Server) starts automatically, followed by the application container for all installed Siebel CRM modules, followed by the Siebel Server system service, if also present.
On UNIX operating systems, you can configure autostart for application containers, as described in Configuring Siebel Application Containers for Automatic Start on UNIX. You can also configure autostart for Siebel Gateway or Siebel Server system services, as described in Configuring the Siebel Gateway for Automatic Start on UNIX and Configuring the Siebel Server for Automatic Start on UNIX.

Caution: If you think you might need to shut down and then restart an application container, then, before you attempt to restart it, you must first check that the application container has shut down completely, for example, by using the Service Control Manager or the Task Manager in Windows. Otherwise, a port conflict failure might impede proper startup of the application container. Sometimes, examining logs might be the only way to indicate the nature of the problem.

Note: Decisions about whether to install Siebel CRM modules together or separately using the Siebel CRM installer must take into account the fact that modules installed together share the application container. Install modules separately to eliminate such dependencies and maintain availability for your Siebel CRM modules. If the Siebel Gateway and Siebel Server are collocated, then they share the same application container and do not require separate operations to stop or start the application container.

This topic includes the following information:

Related Books

Siebel System Administration Guide

Related Topics

Related Books