Bookshelf v7.5: Name Server Parameters

Parameters for the Name Server of the Siebel Gateway can be set at one or more of the enterprise, server, or component levels. They are set in the Server Administration screen of a Siebel employee application such as Siebel Call Center.

Parameters you set at the enterprise level configure all Application Object Managers throughout the enterprise. Parameters set at the server level configure all Application Object Managers on a specific Siebel Server. Parameters set at the component level configure all the tasks, or instances, of a specific component.

For purposes of authentication, all of the components of interest are Application Object Managers, such as the Call Center Object Manager or the eService Object Manager.

A particular parameter set at a lower level overrides the same parameter set at a higher level. For example, if Security Adapter Name = LDAP at the enterprise level, and Security Adapter Name = ADSI at the component level for the eService Object Manager component, then the ADSI security adapter is used for Siebel eService.

Table 16. Name Server Parameters
Subsystem	Parameter	Description	Set at Enterprise Level	Set at Server Level	Set at Component Level
Object Manager	`OM - Configuration File`	Name of an application's (Application Object Manager's) configuration file, such as eservice.cfg, from which other parameter values are applied, as described in Siebel Application Configuration File Parameters.	X	X	X
	`OM - Data Source`	The data source, such as ServerDataSrc, in the file specified by `OM - Configuration File`, to which these parameters apply.	X		X
	`OM - Proxy Employee`	User ID of the proxy employee. For information about the proxy employee, see Seed Data.	X	X	X
	`Security Adapter Name`	The name of the security adapter you implement, as it appears as a section in the application configuration file defined by `OM - Configuration File`. For example, enter `LDAP` if the section of security adapter parameters is the [LDAP] section.	X	X	X
	`OM - Username BC Field`	This parameter is used only if you implement an adapter-defined username. It specifies the field of the User business component that populates the attribute in the directory defined by the `UsernameAttributeType` parameter in the application's configuration file. That is, when the user ID (LoginName field in the User business component) is not the identity key, this field is. If this parameter is not present in the parameters list, you must add it.	X	X	X
Infrastructure Objmgr configu	`Application Encrypt Password`	This parameter is useful for preventing users from logging directly into the server database using a non-Siebel application such as SQL*Plus. If `TRUE` in a database authentication environment, the password entered by the user at login is encrypted before being passed to the database. If `TRUE` in an external authentication environment, the password entered by the user or passed to the SWSE by a third-party authentication client is encrypted before being compared with the password stored for the user in the directory. When enabled, a Siebel-supplied encryption algorithm is applied to the password before it is used to authenticate. To function properly, the database account or directory password with which it is compared must also be set up with the encrypted version of the password. This parameter is not supported for Mobile Web Client. If you are using the Dedicated Web Client, include an `EncryptPassword` parameter in the [Siebel] section of the application .cfg file (for example, `EncryptPassword = "TRUE"`)		X	X