Bookshelf v7.5: Editing Parameter Values in the Application Configuration File

Provide the parameter values as indicated by the guidelines in Table 13 in the configuration file for the Siebel application you are implementing. For a list of Siebel application configuration files, refer to Siebel Server Administration Guide.

NOTE: You can use a text editor to make changes to an application configuration file or you can use the LDAP/ADSI Configuration Utility to make these changes. For more information, see Using the LDAP/ADSI Configuration Utility.

Table 13. Siebel Application Configuration File Parameter Values
Section	Parameter	Guidelines for Siebel ADSI Adapter
[SWE]	`AllowAnonUsers`	Enter `TRUE`. Note: If you do not set this parameter to `TRUE`, browser looping behavior may occur.
[SWE]	`SecureLogin`	Enter `TRUE` or `FALSE`. If `TRUE`, the login form completed by the user is transmitted over a Secure Sockets Layer (SSL). For information about other requirements for secure login, see Secure Login.
[SecurityAdapters]	Add a line for each security adapter you may implement; most likely there is only one.	Suggested entry `ADSI = ADSI`
The section for the particular security adapter you implement, for example [ADSI]	`DllName`	Enter `sscfadsi.dll`
	`ServerName`	Enter the name of the machine on which the ADS server runs. Note: This parameter must be populated with the ADS server's complete machine name, not its IP address—otherwise, users will be unable to change their passwords through the Siebel application. This restriction is due to a limitation of the ADSI client library used by the Siebel ADSI security adapter.
	`Port`	You set the port at the ADS directory level, not as a configuration parameter. If this parameter is present, comment it out, or you can delete the line from the file.
	`BaseDN`	The Base Distinguished Name is the root of the tree under which users are stored. Users can be added directly or indirectly below this subdirectory. Suggested entry (including quotes): "CN=Users, DC=machine, DC=domain, DC=com" Domain Component (DC) entries are the nested domains that locate this server. Common Name (CN) entries are the specific paths for the user objects in the directory. Therefore, adjust the number of CN and DC entries to represent your architecture.
	`UserNameAttributeType`	Suggested entry: `sAMAccountName` If you use a different attribute in the directory for the Siebel user ID, enter that attribute name.
	`PasswordAttributeType`	ADS does not store the password in an attribute, so this parameter is not used with the Siebel ADSI adapter. If this parameter is present, comment it out, or delete the line from the file.
	`CredentialsAttributeType`	Suggested entry: `dbaccount` If you used a different attribute in the directory for the database account, enter that attribute name.
	`ApplicationUser`	Suggested entry (including quotes): "CN=APPUSER, CN=Users, DC=machine, DC=domain, DC=com" Adjust your entry if your implementation uses a different attribute for the user name, a different user name for the application user, or a different base DN.
	`ApplicationPassword`	Enter `APPUSERPW` or the password you assigned to the application user.
	`SingleSignOn`	Enter `TRUE`.
	`TrustToken`	Enter the TrustToken value that you provided for the same variable in the eapps.cfg file.
	`RolesAttributeType` `SslDatabase` `UseSSL` `EncryptCredentialsPassword` `EncryptApplicationPassword` `SharedCredentialsDN` `UseAdapterUsername` `SiebelUsernameAttributeType` `UseRemoteConfig`	If these parameters are present, comment out each with a semicolon at the beginning of the line. Alternatively, you can delete these parameter lines from the file.