Siebel System Administration Guide > Administering Server System Services >

Starting and Shutting Down a Siebel Deployment


It is important to follow the correct sequence when starting or shutting down a Siebel deployment, because several dependencies require that certain servers are running before others. Perform the following procedures to start or shut down your Siebel deployment.

To start a Siebel deployment

  1. Start the Siebel Database.

    Refer to your database documentation for detailed information on this procedure.

  2. Start the Siebel Gateway Name Server System Service.

    Refer to Administering the Siebel Gateway Name Server System Service for detailed information on this procedure.

  3. Start the third-party load balancing software, if applicable. For further information on load balancing, see Siebel Deployment Planning Guide.
  4. Start any other third-party software, if applicable.
  5. Start the Siebel Server System Service.

    The Siebel Server must connect to the Siebel Gateway Name Server and Siebel Database on startup. Refer to Administering the Siebel Server System Service for detailed information on starting the Siebel Server System Service.

  6. Start the Siebel Management Agent Service.

    The Siebel Management Agent must connect to the Siebel Gateway Name Server. Refer to Administering Siebel Management Agents for detailed information on starting a Siebel Management Agent System Service.

    NOTE:  If you use database authentication to authenticate users who request access to the Siebel Management Agent, then your Siebel Management Agent must also connect to the Siebel Database. For more information on authentication options, refer to the Siebel Security Guide.

  7. Start the Siebel Management Server Service.

    The Siebel Management Server must connect to the Siebel Gateway Name Server. Refer to Administering the Siebel Management Server System Service for detailed information on starting the Siebel Management Server System Service.

    NOTE:  If you use database authentication to authenticate users who request access to the Siebel Management Server, then your Siebel Management Server must also connect to the Siebel Database. For more information on authentication options, refer to the Siebel Security Guide.

To shut down a Siebel deployment

  1. Shut down the Siebel Server System Service.

    When the Siebel Server System Service is shut down, it shuts down server components and tasks before shutting down itself. Refer to Administering the Siebel Server System Service for detailed information on the shutdown procedure.

    NOTE:  To make sure server components shut down properly, shut down Siebel Servers before shutting down the Siebel Server System Service. See Siebel Server Management Commands for the command-line interface command. See Shutting Down a Siebel Server for the GUI-based command.

  2. Shut down the Siebel Management Agent Service.

    Refer to Administering the Siebel Management Server System Service for detailed information on this procedure.

  3. Shut down the Siebel Management Server Service.

    Refer to Administering Siebel Management Agents for detailed information on this procedure.

  4. Shut down the third-party load balancing software and any other third-party software, if applicable. For further information on load balancing, see Siebel Deployment Planning Guide.
  5. Shut down the Siebel Gateway Name Server service.

    For detailed information on this procedure, see Administering the Siebel Gateway Name Server System Service.

    NOTE:  Make sure all Siebel Servers are shut down before shutting down the Siebel Gateway Name Server service.

  6. Shut down the Siebel Database.

    Refer to your database documentation for detailed information on this procedure.

Siebel System Administration Guide Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.