Starting the Siebel Gateway

You must make sure that the Siebel Gateway system service is started when you do any of the following:

• Start any application container for Siebel CRM modules

• Start the Siebel Server system service

• Configure the Security profile

• Create and deploy the Siebel Enterprise profile

• Create and deploy a Siebel Server profile

• Create and deploy a Siebel Application Interface profile

• Create and deploy a Siebel Migration profile

• Operate any of the Siebel applications

• Remove the configuration for any of the Siebel CRM modules mentioned. (These are tasks that you might perform when you are uninstalling the software.)

Note: It is recommended that you review the Siebel Gateway log files, which are found in the SIEBEL_GATEWAY_ROOT\LOG directory.

To start the Siebel Gateway manually on Windows

1. Navigate to Control Panel, Administrative Tools, and then Services.

2. If the Siebel Gateway Name Server system service is not started, then click Action, and then Start.

   Note: For compatibility with prior releases, the actual name of the system service is Siebel Gateway Name Server (in contrast to the current usage of the name Siebel Gateway for the module itself).

To verify that the Siebel Gateway has started on UNIX

• Navigate to the $SIEBEL_ROOT/gtwysrvr directory and source the following environment setup file. Use one of the following commands, depending on the type of shell that you use:

  C shell

  source siebenv.csh
  

  Bourne or Korn shell

  ./siebenv.sh
  

  This step sets the Siebel environment variables and path information required to use Siebel utilities.

  To configure the Siebel environment shell script to source automatically whenever a Siebel administrator logs on, specify the shell as the default for administrator accounts. Then, add this command to the startup file for the administrator’s account.

To verify that the Siebel Gateway started successfully and is running on UNIX

1. Enter the following command:

   list_ns
   

   If the Siebel Gateway Name Server system service is running, then you receive a response like the following, which shows the pid (process ID) of the running process:

   started at Mon May 01 20:06:55 2017, pid: 4024, autostart: yes
   

   If the Siebel Gateway Name Server system service is stopped, then you receive a response like this:

   stopped at Mon May 01 20:06:55 2017, autostart: no
   

2. If the Siebel Gateway Name Server system service is stopped, then do the following:

   • Execute the start_ns command to start the Siebel Gateway Name Server system service. For more information, see Siebel System Administration Guide.

   • Execute list_ns to verify that it is operating correctly.

Related Topics

Installing Siebel CRM using the User Interface

Configuring Siebel Application Containers for Automatic Start on UNIX

Configuring the Siebel Gateway for Automatic Start on UNIX

Configuring the Siebel Server for Automatic Start on UNIX

Starting the Siebel Server Service on Windows

Verifying Installation for Siebel CRM

Verifying That the Siebel Gateway Has Started