Siebel Application Configuration Parameters

A separate configuration exists for each Siebel application for each language. The parameters for each Siebel application determine how the user interacts with the Application Object Manager and with the security adapter. The application configuration that controls a particular user session depends on the client with which a user connects as follows:

Configuration parameters for Siebel Server (Siebel Web Client). For users connecting with the standard Siebel Web Client, application configuration is located in the SIEBSRVR_ROOT\bin\LANGUAGE subdirectory. For example, eservice.cfg is provided for Siebel eService, for implementation in U.S. English, in the SIEBSRVR_ROOT\bin\ENU directory.
Note: Most of the security-related parameters applicable to Siebel Servers (and, consequently, Siebel Web Clients) are stored in the Siebel Gateway, not in the application configuration file.
See Server Parameters for Siebel Gateway for a description of the parameters applicable to Siebel Web Clients.
Configuration parameters for Siebel Tools, Mobile Web Client, or Developer Web Client. Application configuration is located in the SIEBEL_CLIENT_ROOT\bin\LANGUAGE subdirectory on the client. For example, eservice.cfg is provided for Siebel eService and tools.cfg for Siebel Tools, for implementation in U.S. English, in the SIEBEL_CLIENT_ROOT\bin\ENU directory.

Siebel Mobile Web Client connects directly to the local database and bypasses the Siebel Server.

Siebel Developer Web Client connects directly to the server database and bypasses the Siebel Server.

The parameters in the following table apply to Siebel Tools, Mobile Web Clients, and Developer Web Clients.

Caution: The parameter values that reference directory attributes that you provide for the Siebel LDAP security adapter are case-sensitive. The values must match the attribute names in the directory.

Parameter	Description
SecAdptMode For more information about setting this parameter, see the Enterprise Security Authentication Profile (Security Adapter Mode) parameter in the table in Parameters for Configuring Security Adapter Authentication.	Specifies the security adapter mode. The options are: For database authentication, specify DB (which is the default value). For LDAP authentication, specify LDAP. For a custom security adapter, specify CUSTOM. If you implement a custom, non-Siebel security adapter, then you must configure your adapter to interpret the parameters used by the Siebel adapters if you want to use those parameters.
SecAdptName For more information about setting this parameter, see the Security Adapter Name (named subsystem) parameter in the table in Parameters for Configuring Security Adapter Authentication.	Specifies the name of the security adapter. For database authentication, specify DBSecAdpt (which is the default value). For Mobile or Developer Web Client configuration, the DBSecAdpt is created in the configuration. For LDAP authentication, specify LDAPSecAdpt (or a name of your choice). For Developer Web Client configuration, the LDAPSecAdpt is created by default in the configuration if you configure LDAP using the Siebel Management Console. For a custom security adapter, specify a name such as SecAdpt_Custom. You must add the applicable section to the file yourself. For example, [SecAdpt_Custom].
UseRemoteConfig This parameter applies only to the Siebel Developer Web Client, and is not available in the Siebel Management Console.	Specifies the path to a configuration file that contains only parameters for a security adapter, that is, it contains parameters as they would be formatted if they were included in a section such as `[LDAPSecAdpt]` in an application’s configuration file. You must provide the path in universal naming convention (UNC) format, that is, for example, in a form like `\\server\vol\path\ldap_remote.cfg`. For detailed information about using this parameter, Security Adapters and the Siebel Developer Web Client.

Parameter

Description

SecAdptMode

For more information about setting this parameter, see the Enterprise Security Authentication Profile (Security Adapter Mode) parameter in the table in Parameters for Configuring Security Adapter Authentication.

Specifies the security adapter mode. The options are:

For database authentication, specify DB (which is the default value).
For LDAP authentication, specify LDAP.
For a custom security adapter, specify CUSTOM.

If you implement a custom, non-Siebel security adapter, then you must configure your adapter to interpret the parameters used by the Siebel adapters if you want to use those parameters.

SecAdptName

For more information about setting this parameter, see the Security Adapter Name (named subsystem) parameter in the table in Parameters for Configuring Security Adapter Authentication.

Specifies the name of the security adapter.

For database authentication, specify DBSecAdpt (which is the default value).
For Mobile or Developer Web Client configuration, the DBSecAdpt is created in the configuration.
For LDAP authentication, specify LDAPSecAdpt (or a name of your choice).

For Developer Web Client configuration, the LDAPSecAdpt is created by default in the configuration if you configure LDAP using the Siebel Management Console.
For a custom security adapter, specify a name such as SecAdpt_Custom.
You must add the applicable section to the file yourself. For example, [SecAdpt_Custom].

UseRemoteConfig

This parameter applies only to the Siebel Developer Web Client, and is not available in the Siebel Management Console.

Specifies the path to a configuration file that contains only parameters for a security adapter, that is, it contains parameters as they would be formatted if they were included in a section such as [LDAPSecAdpt] in an application’s configuration file.

You must provide the path in universal naming convention (UNC) format, that is, for example, in a form like \\server\vol\path\ldap_remote.cfg.

For detailed information about using this parameter, Security Adapters and the Siebel Developer Web Client.

Changes to an application configuration are not active until you restart the Siebel Server or Siebel client. For more information about working with configuration information, see Siebel System Administration Guide.