Siebel Installation Guide for Microsoft Windows > Additional Postinstallation and Configuration Tasks >

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.

As of Siebel CRM 18.8 Update, 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. You can also configure autostart for Siebel Gateway or Siebel Server system services, as described in Siebel Installation Guide for 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:  Recommendations about whether to install Siebel CRM modules together or separately using the Siebel Enterprise installer are based in part on 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.

Troubleshooting Task Sequence When Siebel Application Containers Are Not Running

When any of the application containers are not running, follow all applicable steps as follows:

1. Stop the application container for the Siebel Application Interface.
2. Stop the Siebel Server system service.
3. Stop the application container for the Siebel Server (Configuration Agent), if the Siebel Gateway and the Siebel Server are not collocated.
4. Stop the application container for the Siebel Gateway.
5. Stop the Siebel Gateway system service.
6. Start the Siebel Gateway system service.
7. Start the application container for the Siebel Gateway.
8. Start the application container for the Siebel Server (Configuration Agent), if the Siebel Gateway and the Siebel Server are not collocated.
9. Start the Siebel Server system service.
10. Start the application container for the Siebel Application Interface.

Stopping the Siebel Application Container

To shut down the application container, do one of the following:

• Microsoft Windows. Run the Service Control Manager (services.msc), locate the service named like Apache Tomcat 8.5 SiebelApplicationContainer_OracleHome_BuildNumber, and click the Stop button on the toolbar.

  In the preceding service name, OracleHome is the Oracle home for the Siebel CRM installation (such as SES or SIEBEL_AI) and BuildNumber is the software build number. The service name is automatically defined in this format at the time the service is created.

• UNIX. Navigate to the directory $SIEBEL_HOME/applicationcontainer/bin, and then execute the command ./shutdown.sh.

  On UNIX operating systems, the shutdown.sh and startup.sh commands are provided in the following locations. (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.)

  • Siebel Gateway. SIEBGTWY_ROOT/applicationcontainer/bin
  • Siebel Server. SIEBSRVR_ROOT/applicationcontainer/bin
  • Siebel Application Interface. SIEBEL_AI_ROOT/applicationcontainer/bin

Starting the Siebel Application Container

To start the application container, do one of the following:

• Microsoft Windows. Run the Service Control Manager (services.msc), locate the service named like Apache Tomcat 8.5 SiebelApplicationContainer_OracleHome_BuildNumber, and click the Start button on the toolbar.

  In the preceding service name, OracleHome is the Oracle home for the Siebel CRM installation (such as SES or SIEBEL_AI) and BuildNumber is the software build number. The service name is automatically defined in this format at the time the service is created.

  NOTE:  Where you need to manually start any application container in your Siebel CRM deployment, do so only in the manner described here.

• UNIX. Navigate to the directory $SIEBEL_HOME/applicationcontainer/bin, and then execute the command ./startup.sh.

  NOTE:  It is strongly recommended to configure all application containers in your Siebel CRM deployment to start automatically, or else configure none of them to start automatically. For more information, see Siebel Installation Guide for UNIX.

Related Topics

Starting the Siebel Gateway

Starting the Siebel Server Service

Verifying Installation for Siebel CRM

Troubleshooting Installation and Configuration for Siebel CRM

Related Books

Siebel System Administration Guide