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 on the 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 on the Siebel Mobile Web Client or Developer Web Client. For users connecting through the Siebel Mobile Web Client or Developer Web Client, the configuration is located in the SIEBEL_CLIENT_ROOT\bin\LANGUAGE subdirectory on the client. For example, eservice.cfg is provided for Siebel eService, for implementation in U.S. English, in the SIEBEL_CLIENT_ROOT\bin\ENU directory.

  • The Siebel Mobile Web Client connects directly to the local database; it bypasses the Siebel Server.

  • The Siebel Developer Web Client connects directly to the server database; it bypasses the Siebel Server.

  The parameters in Table A-9 apply to Siebel Mobile Web Clients and Developer Web Clients:

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.

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.

Table A-9 Parameters for Siebel Mobile Clients and Developer Web Clients

Parameter	Description
SecAdptMode For more information about setting this parameter, see the Enterprise Security Authentication Profile (Security Adapter Mode) parameter in Table A-1.	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 Table A-1.	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, see "Security Adapters and the Siebel Developer Web Client".

Parameters for Database Security Adapter (DBSecAdpt)

You define database authentication parameters for the following named subsystems:

• InfraSecAdpt_DB. That is, for the DBSecAdpt named subsystem or a similar security adapter with a nondefault name.

• InfraDataSource. That is, for the ServerDataSrc named subsystem or another data source.

The named subsystem is specified as the value for the data source Security Adapter Name parameter for the database security adapter.

The following parameters apply when defining a database security adapter:

• Name

• Type

• Host Name

• Port

• SQL Style of Database

• Database Service Name

• Table Owner

• Enterprise Security Authentication Profile (Security Adapter Mode)

• Security Adapter Name (named subsystem)

• Database Security Adapter Data Source

• Database Security Adapter Propagate Changes

For more information about these parameters, see "Parameters for Configuring Security Adapter Authentication".

Note: Starting from Java 8, the odbc-jdbc driver is not supported. Because of this limitation, you must specify raw database connection details (like server host, port, database service name, and so on) instead of ODBC details when defining a database security profile.

Parameters for LDAP Security Adapter (LDAPSecAdpt)

You define LDAP authentication parameters for the following named subsystems:

• InfraSecAdpt_LDAP. That is, for the LDAPSecAdpt named subsystem or a similar security adapter with a nondefault name.

The named subsystem is specified as the value for the data source Security Adapter Name parameter for the LDAP security adapter.

The following parameters apply when defining an LDAP security adapter:

• Name

• Type

• Host Name

• Port

• Enterprise Security Authentication Profile (Security Adapter Mode)

• Security Adapter Name (named subsystem)

• Application User Distinguished Name (DN)

• Application Password

• Base Distinguished Name (DN)

• Credentials Attribute

• Hash Algorithm

• Hash DB Password

• Hash User Password

• Password Attribute Type

• Propagate Change

• Roles Attribute (optional)

• Shared Databases Account Distinguished Name (fully qualified domain name)

• Shared DB User Name

• Shared DB Password

• Security Adapter Mapped User Name

• Siebel Username Attribute

• SSL

• Enable SSL

• Configure Web Single Sign-On

• Trust Token

• Wallet Password

• Salt Attribute Type

• Salt User Password

• User Name Attribute Type

For more information about these parameters, see "Parameters for Configuring Security Adapter Authentication".

Parameters for Custom Security Adapter (CustSecAdpt)

You define custom authentication parameters for the following named subsystems:

• InfraSecAdpt_Custom. That is, for the CustSecAdpt named subsystem or a similar security adapter with a nondefault name.

The named subsystem is specified as the value for the data source Security Adapter Name parameter for the custom security adapter.

The following parameters apply when defining an Custom security adapter:

• Enterprise Security Authentication Profile (Security Adapter Mode)

• Security Adapter Name (named subsystem)

• Application User Distinguished Name (DN)

• Application Password

• Base Distinguished Name (DN)

• Custom Library

• SQL Style of Database

• CRC Checksum

• Credentials Attribute

• Hash Algorithm

• Hash DB Password

• Hash User Password

• Password Attribute Type

• Propagate Change

• Roles Attribute

• Shared Databases Account Distinguished Name

• Shared DB User Name

• Shared DB Password

• Security Adapter Mapped User Name

• Siebel Username Attribute

• SSL

• Enable SSL

• Configure Web Single Sign-On

• Trust Token

• Wallet Password

• Salt Attribute Type

• Salt User Password

• User Name Attribute Type

For more information about these parameters, see "Parameters for Configuring Security Adapter Authentication".