The Siebel Gateway maintains the configuration information
for the components in the Siebel CRM environment. For example, it
monitors where each Siebel Enterprise Server (SES) and Siebel Application
Interface (SAI) instance is running, which components should be run
on which physical servers, and so on.
Do the following to configure the gateway:
- Navigate to the Siebel Management Console (SMC) at https://myserver.company.com/siebel/smc.
This is the server where you installed the SAI components. If
you configured a HTTPS port number different from the default value,
then include this in the URL.
- Enter the credentials that you defined when installing
the SAI.
The SMC automatically determines that a Siebel Gateway has not
yet been configured and starts the Gateway configuration process.
- Enter the requested information.
For more information, see
Siebel Installation Guide for Microsoft
Windows or
Siebel Installation Guide for UNIX as appropriate. The following
are key attributes:
Host Name: HTTPS Port
Host Name. This is the host name where
the SES components are installed and where you intend to run the Gateway.
This host name must match one of the Subject Alternative Names in
the Secure Sockets Layer (SSL) certificate previously generated and
signed.
HTTPS Port. This is the HTTPS port you
selected when you installed the SES components, not SAI. For example:
myserver.mycompany.com:9010
Security Profile. This sets up the security
mechanism used to authenticate connections to SMC. For the Gateway,
you can name it, for example, Gateway Security Profile. For a development
instance, you typically use database authentication, so you must specify
the database type, for example, Oracle or Microsoft SQL Server. You
also must specify the connection information, such as the location
of database server, port for TNS Listener, and so on.
Testing. Enter the credentials for SADMIN.
These are the same credentials as those used when executing the grantusr.sql
script. This password may be different than the one used during the
installation of SAI.
- If the test is successful, then SMC logs out, and prompts
for login credentials. At this point, use the SADMIN credentials defined
by the grantusr.sql script, and not those used during the installation
of SAI.
- The configuration wizard prompts you for service user credentials.
These are the credentials under which the Gateway Service runs (either
as a Windows Service or as a UNIX process).
Note: For Windows-based systems, this should be a domain user
who is also a local administrator.
Results:
When you complete these steps, the Siebel Gateway service
will be created, and the Siebel Deployment Hierarchy page opens.