Go to primary content
Siebel CRM System Administration Guide
Siebel 2018
E24823-01
  Go to Documentation Home
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
    View PDF

About the Siebel Gateway

The Siebel Gateway coordinates the Siebel Enterprise Server and Siebel Servers. A single Siebel Gateway can support a single Siebel Enterprise Server. The Siebel Gateway provides the persistent backing of Siebel Enterprise Server configuration information, including:

Because this information changes, such as during the configuration of a Siebel Server, it is written to the Siebel Gateway registry. At startup, the Siebel Server obtains its configuration information from the Siebel Gateway registry.

The Siebel Gateway provides the dynamic registry for Siebel Server and component availability information. At startup, a Siebel Server within the Siebel Enterprise Server notifies the Siebel Gateway of its availability and stores its connectivity information, such as network addresses, in the Siebel Gateway's nonpersistent (volatile) store. For information about backing up and restoring the Siebel Gateway registry, see "Backing Up and Restoring the Siebel Gateway Registry".

Enterprise components (including the Server Manager) query the Siebel Gateway for Siebel Server availability and connectivity information. When a Siebel Server shuts down, this nonpersistent information is cleared from the Siebel Gateway.

In a Windows environment, the Siebel Gateway runs as a Windows service. In a UNIX environment, the Siebel Gateway runs as a daemon process. The system process for the Siebel Gateway is siebsvc.exe on Windows and siebsvc on UNIX. Each running Siebel Server has a corresponding Siebel Gateway system process. For information about running the Siebel Gateway, see "Administering the Siebel Gateway System Service".

The Siebel Gateway also includes an application container. The application container process for the Siebel Gateway is tomcat8.exe on Windows and javaw on UNIX. For more information, see the Siebel Installation Guide for the operating system you are using. See also "Starting and Shutting Down a Siebel CRM Deployment".


Note:

Each Siebel Gateway can support only one Siebel Enterprise and one Siebel database. For more information, see the Siebel Installation Guide for the operating system you are using and Siebel Deployment Planning Guide.

Impact of Failure

When the Siebel Gateway goes down, service to active user connections is not immediately interrupted. All of the Siebel Server components, including Application Object Managers, that are currently running continue to do so. However, no new Siebel Server components can be started or added. Server administration functions become limited.

As of Siebel CRM 18.5 Update, Siebel CRM supports an optional native clustering feature for Siebel Gateway to provide high availability benefits to Siebel CRM customers. For more information, see the Siebel Installation Guide for the operating system you are using.