Siebel System Administration Guide > Siebel Application Configuration Parameters >

Description of Siebel Application Parameters

Table 32 defines Siebel application parameters that appear in the section [Siebel].

These parameters apply only to Siebel Mobile Web Client. For the Siebel Web Client, the parameters are defined as server parameters on the Application Object Manager.

Table 32. Siebel Client Application Parameters


Specifies the directory where Microsoft Access is installed.


Name of the application object in the repository to use, such as Siebel Sales or Siebel Service. ApplicationName determines which splash screen appears and which set of menus is enabled.


Text that appears on a splash screen when starting up a Siebel application.

The default varies by the application. If you are starting Siebel Sales, for example, ApplicationSplashText is set to Siebel Sales by default.


Changing the text in the ApplicationTitle parameter in the configuration file changes the Application Title value in the multi-value group applets and the Title that appears on the left side of the application title bar.

As necessary, make this change in the appropriate configuration file for the intended application. For example, for Siebel Call Center, this parameter would be set, in the file uagent.cfg, to Siebel Call Center.


Allows customizing of the title in the upper left corner of the Siebel client application. Reads Siebel by default.


Specifies the directory where the Siebel client software is installed.


Specifies the Siebel Anywhere configuration that should be used during version check. Navigate to the Siebel Anywhere Administration screen, then the Configurations view to see the configurations.

Change the setting for this parameter if you want this configuration file to be version-checked by a specific Siebel Anywhere configuration.

For example, if you want to check the version of Siebel Business Applications used at one facility with the version used at another facility, create two Siebel Anywhere configurations appropriately named. Then, in the configuration file for each set of users, enter a different value for the ComponentName parameter.

It is recommended that you use only alphanumeric characters plus dashes and normal parentheses for the ComponentName parameter. If you want to use the Priority upgrade feature, the maximum character length for the Upgrade Component name should be 40.


Name of the default data source that appears in the Connect to drop-down list in the Siebel login screen. Must correspond to an existing data source defined in the configuration file. By default, this parameter is set to Local.


Font name specification for chart applets. Defaults to Arial-10 normal.


Allows the application to read repository information straight from the database, rather than from the Siebel repository file (SRF) file. The value should match the repository used for compiling the SRF file.


Must be set to TRUE to activate the personalization (content targeting) functionality.

Siebel workflow processes will not execute properly until personalization events are reloaded.


TRUE or FALSE. Enables use of Siebel Visual Basic or Siebel eScript.

Setting this parameter to false also disables browser scripts in addition to server scripts.


Name of the ODBC data source that is set up to access the local database. It is used by a variety of features in the Siebel Business Applications and in Siebel Tools. It should not need to be modified because it is correctly configured by the installation program.


TRUE or FALSE. Enables multicurrency support.


Add the following to the configuration file to view a log of all personalization activity:

PersonalizationLog = "C:\personalization.txt"

where C: is the drive where you want to store the log. The log may assist in the process of debugging your rules, events, and actions.


TRUE or FALSE. TRUE indicates that searches are performed on a remote machine; FALSE indicates that searches are performed on a local machine.


Indicates the name of the remote machine that performs searches.


Directory where reports are installed. It is typically left blank.


Name of ODBC data source used to connect to modules such as Crystal Reports.


Name of the Siebel SRF file to use.

RepositoryFile specifies the physical file that contains all the run-time object definitions. Where appropriate, this parameter can optionally specify the absolute path to the SRF file, in order to use the SRF file in a different language directory-such as to display the user interface in a different language than that specified by Language Code. For more information about multilingual Siebel deployments, see Siebel Global Deployment Guide.


Name of the shared library that implements Siebel Visual Basic or Siebel eScript. If the Siebel Server runs on a UNIX server machine, and you plan to use eScript, set the value of ScriptingDLL to


Search definition from Siebel Tools to be used for searching. For more information about search, see Siebel Search Administration Guide.


Defines the search engine to use for search. You set this parameter to the value that identifies the search engine.

If your search engine is Oracle Secure Enterprise Search (Oracle SES) you set it to SES.

For more information about search engine administration, see Siebel Search Administration Guide.


Set this parameter to the directory where your search engine is installed. For more information about search engine administration, see Siebel Search Administration Guide.


Directory where user preference files are stored. It is typically left blank, otherwise it must be set to a directory under a network shared drive, but it cannot be set to the shared drive itself.

For example, if \\yourserver\common is the network shared drive, you cannot set SharedModeUsersDir to \\yourserver\common. Instead, set SharedModeUsersDir to a directory under \common.


Directory where temporary files should be created.


Represents version of file. This parameter is for internal use only and is automatically maintained by Siebel Anywhere. When you create an upgrade kit for the configuration file, Siebel Anywhere increments this version string appropriately, based on the version information from the Upgrade Components screen.

NOTE:  When you perform a Siebel Anywhere upgrade, you must manually upgrade files from the upgraded Siebel client directory to the Siebel Server directory.

Siebel System Administration Guide Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.