11Parameters in Siebel Application Configuration Files
Parameters in Siebel Application Configuration Files
This chapter includes information about some of the parameters in Siebel application configuration files. It includes the following topics:
Overview of Parameters in Siebel Application Configuration Files
This chapter includes information about the Siebel application configuration files and some of the parameters that these files might contain. Most of the parameters that are documented here are used by Siebel applications in the Siebel Mobile Web Client, or by Siebel Tools Client (using tools.cfg file).
In general, for Siebel Web Client applications connecting to an Application Object Manager component, the enterprise, server, component, or data source parameters stored in the Siebel Gateway registry, for example, are used instead of the corresponding parameters in the configuration file located on the Siebel Server. However, the Application Object Manager or Siebel Server might still use some configuration file parameters.
Where you configure parameters for Siebel applications depends on your type of client deployment:
For a Siebel Mobile Web Client deployment, you configure parameters in a configuration file (.cfg). Examples of configuration files include siebel.cfg, used by Siebel Sales, and uagent.cfg, used by Siebel Call Center. For more information, see About Siebel Application Configuration Files and Editing Siebel Application Configuration Files.
For a Siebel Web Client deployment, you primarily configure parameters as component parameters for the Application Object Manager component or as named subsystem parameters. In either case, you use the Siebel Server Manager to configure the parameter. For more information, see About Application Object Manager Parameters.
The remaining topics in this chapter include the following:
About Siebel Application Configuration Files lists some configuration files and their associated Siebel applications.
Editing Siebel Application Configuration Files describes how you can edit a Siebel application configuration file.
Configuration Parameters Index provides a partial list of configuration parameters and provides references to where they are documented in more detail.
In many cases, when you set the equivalent parameter for an Application Object Manager component, for Siebel Web Clients, the alias of the parameter that appears in the Siebel Server Manager GUI is prefixed by CFG. The full parameter name also appears in the GUI.
For example, for Siebel Mobile Web Clients, you set the parameter ApplicationSplashText in the configuration file to determine the text that appears on a splash screen when a user starts a Siebel application. For a Siebel Web Clients, you set the parameter Application Splashtext (alias CFGApplicationSplashText) on the relevant Application Object Manager component.
Description of Siebel Application Parameters describes some of the parameters that are listed in Configuration Parameters Index.
Data Source Parameters describes some of the data source parameters that are listed in Configuration Parameters Index.
[ServerDataSrc]
section of an application configuration file appears as Data source Connect String (alias DSConnectString) for the Server Datasource named subsystem in the Siebel Server Manager GUI.
About Siebel Application Configuration Files
The following information lists several configuration files and their associated Siebel CRM applications. Your installation might contain additional configuration files besides those listed.
The configuration files are located in the SIEBEL_CLIENT_ROOT\bin\LANGUAGE
directory on the Siebel Mobile Web Client. The name of the configuration file varies, depending on the application that you are using. Separate configuration files are provided for each supported language.
Table Some Siebel Applications and Associated Configuration Files
Siebel Application |
Configuration File |
---|---|
Siebel Call Center |
uagent.cfg |
Siebel Marketing |
market.cfg |
Siebel Partner Manager |
pmanager.cfg |
Siebel Sales |
siebel.cfg |
Siebel Service |
sfs.cfg |
The initial values for the parameters in the configuration files are either predefined by Siebel CRM or defined using the values that you specify during the initial configuration or at other times.
Some parameter values might include the notation $(param_name). These parameter values are substituted automatically, for example, during a client installation or local database initialization. For example, the value of the ConnectString parameter for a data source that has not yet been configured appears as follows:
ConnectString = $(ConnectString)
This parameter value is updated when you initialize the local database for a Siebel Mobile Web Client. For more information about initializing the local database, see Siebel Remote and Replication Manager Administration Guide. See also the Siebel Installation Guide for the operating system you are using.
Editing Siebel Application Configuration Files
The Siebel application configuration files are plain-text files, and can be edited manually using a text editor. You can add parameters and their values or change values for existing parameters.
There are many reasons why you might edit configuration files. For example, you might want to do so at some point after the installation and initial configuration in order to enable or disable certain functionality and features. You must make changes in all of the configuration files for the applications that you are using. For each new application that you create, you must copy and edit a configuration file to suit your needs.
To edit a Siebel application configuration file
Create a backup copy of the existing configuration file for which you want to edit parameter values, and save that file as a backup file.
Using any suitable text editor, such as Notepad, open the default version of the configuration file.
Edit parameter values, as necessary, to obtain the application behavior that you require.
Run a test using the configuration file that you edited.
If there is an error in your test, then correct the error and try again, or restore the configuration file from the backup file.
If no error occurs and the edit that you made has the result that you wanted, then use the modified configuration file.
Configuration Parameters Index
The following table contains an alphabetical listing of some of the configuration parameters from Siebel application configuration files such as siebel.cfg or uagent.cfg. This list shows the name of the section in which each parameter can be found and identifies where the parameter is documented (in tables in Description of Siebel Application Parameters and Parameters for Individual Data Source Sections). This list is not comprehensive.
Table Index of Configuration Parameters
Configuration Parameter Name |
Section Name |
Where Documented and Description |
---|---|---|
AccessDir |
|
|
AllowAnonUsers |
|
Siebel Security Guide |
ApplicationName |
|
|
ApplicationPassword |
Applicable security adapter sections, such as:
|
Siebel Security Guide |
ApplicationSplashText |
|
|
ApplicationTitle |
|
|
ApplicationUser |
Applicable security adapter sections |
Siebel Security Guide |
BaseDN |
Applicable security adapter sections |
Siebel Security Guide |
CancelQueryTimeOut |
|
Siebel Applications Administration Guide |
CaptionPrefix |
|
|
CaseInsensitive |
Applicable data source sections, including:
|
|
ClientRootDir |
|
|
CommConfigCache |
|
Siebel CTI Administration Guide |
CommConfigManager |
|
Siebel CTI Administration Guide |
CommConfigManagerName |
|
Siebel CTI Administration Guide |
CommEnable |
|
Siebel CTI Administration Guide |
CommLocalDriver |
|
Siebel CTI Administration Guide |
CommLogDebug |
|
Siebel CTI Administration Guide |
CommLogFile |
|
Siebel CTI Administration Guide |
CommMaxLogKB |
|
Siebel CTI Administration Guide |
CommMaxMsgQ |
|
Siebel CTI Administration Guide |
CommReleaseLogHandle |
|
Siebel CTI Administration Guide |
CommReqTimeout |
|
Siebel CTI Administration Guide |
ComponentName |
|
|
ConnectString |
Applicable data source sections, including:
|
Parameters for Individual Data Source Sections (data sources) |
ContactLogin |
Applicable data source sections |
|
CredentialsAttributeType |
Applicable security adapter sections |
Siebel Security Guide |
DataSource |
|
|
DebugLevel |
|
Siebel Email Administration Guide |
DefaultMailClient |
|
Siebel Email Administration Guide |
DisableExecuteRetry |
|
|
DisableReverseProxy |
|
Siebel Security Guide |
DLL |
Applicable data source sections, including:
|
|
Docked |
Applicable data source sections, including:
|
|
DockConnString |
Applicable data source sections, including:
|
|
DockRecvTxnsPerCommit |
Applicable data source sections |
|
DockRepositoryName |
|
|
DockTxnsPerCommit |
Applicable data source sections, including:
|
|
EditFieldCaption |
|
Configuring Siebel Business Applications |
EditFieldType |
|
Configuring Siebel Business Applications |
Enable |
|
Siebel Data Quality Administration Guide |
EnableFQDN |
|
Siebel Installation Guide for the operating system you are using |
EnableInlineForList |
|
If the applet mode property is set to Edit List, then the functions Edit, New, and Query work in-line, that is, in the list applet, when EnableInlineForList is set to True. The default value is True. Set to False to turn off this behavior. |
EnablePersonalization |
|
|
EnableScripting |
|
|
EnterpriseServer |
Applicable data source sections, including:
|
|
eProdCfgNumbOfCachedCatalogs |
|
Siebel Performance Tuning Guide |
eProdCfgNumbofCachedWorkers |
|
Siebel Performance Tuning Guide |
eProdCfgNumOfCachedAttrs |
|
Siebel Performance Tuning Guide |
eProdCfgNumOfCachedClasses |
|
Siebel Performance Tuning Guide |
eProdCfgSnapshotFlg |
|
Siebel Performance Tuning Guide |
FileSystem |
Applicable data source sections, including:
|
|
FQDN |
|
Siebel Installation Guide for the operating system you are using |
GatewayAddress |
Applicable data source sections, including:
|
|
GatewayDataSrc |
|
|
Hidden |
Applicable data source sections, including:
|
|
InsensitivityFactor |
Applicable data source sections, including:
|
|
InsUpdAllCols |
Applicable data source sections |
|
IntegratedSecurity |
Applicable data source sections |
|
Local |
|
|
LocalDbODBCDataSource |
|
|
LoginView |
|
Siebel Security Guide |
MaxCachedCursors |
Applicable data source sections, including:
|
|
MaxCachedDataSets |
Applicable data source sections, including:
|
|
MaxConnections |
Applicable data source sections |
|
MaxCursorSize |
Applicable data source sections, including:
|
|
MaxDepthOfTheQuery |
|
|
MessageBarUpdateInterval |
|
Siebel Applications Administration Guide |
MultiCurrency |
|
|
NonSQL |
Applicable data source sections |
|
NumberOfListRows |
|
Siebel Object Types Reference |
PasswordAttributeType |
Applicable security adapter sections |
Siebel Security Guide |
PersonalizationLog |
|
|
Port |
Applicable security adapter sections |
Siebel Security Guide |
PrefetchSize |
Applicable data source sections, including:
|
|
PrimaryEnterprise |
Applicable data source sections, including:
|
|
RemoteSearchServer |
|
|
RemoteSearchServerPath |
|
|
ReportDataDir |
|
Siebel Reports Guide |
ReportOutputDir |
|
Siebel Reports Guide |
ReportsDir |
|
|
ReportsODBCDataSource |
|
|
RepositoryFile |
|
|
RequestServerName |
|
This parameter is the name of the Siebel Server that services requests from the Siebel client. |
RequiredIndicator |
|
Siebel Developer's Reference |
ReverseFillThreshold |
Applicable data source sections, including:
|
|
RolesAttributeType |
Applicable security adapter sections |
Siebel Security Guide |
Sample |
|
|
ScriptingDLL |
|
|
SearchDefName |
|
|
SearchEngine |
|
|
SearchInstallDir |
|
|
SecAdptDllName |
Applicable security adapter sections |
Siebel Security Guide |
SecAdptMode |
|
Siebel Security Guide |
SecAdptName |
|
Siebel Security Guide |
ServerDataSrc |
|
|
ServerName |
Applicable security adapter sections |
Siebel Security Guide |
SharedCredentialsDN |
Applicable security adapter sections |
Siebel Security Guide |
SharedModeUsersDir |
|
|
ShowMessageBar |
|
Siebel Applications Administration Guide |
ShowWriteRecord |
|
Siebel Partner Relationship Management Administration Guide |
SiebelExtMailClientAttDir |
|
Siebel Email Administration Guide |
SiebelUsernameAttributeType |
Applicable security adapter sections |
Siebel Security Guide |
SingleSignOn |
Applicable security adapter sections |
Siebel Security Guide |
SqlStyle |
Applicable data source sections, including:
|
|
SslDatabase |
Applicable security adapter sections |
Siebel Security Guide |
SystemSWFName |
|
Configuring Siebel Business Applications |
SystemSWSName |
|
Configuring Siebel Business Applications |
TableOwner |
Applicable data source sections, including:
|
|
TempDir |
|
|
TreeNodeX (several parameters that are similarly named, for example, TreeNodeCollapseCaption) |
|
Configuring Siebel Business Applications |
TrustToken |
Applicable security adapter sections |
Siebel Security Guide |
Type |
|
Siebel Data Quality Administration Guide |
UpperCaseLogin |
Applicable data source sections |
|
UseDictionaryinTransactionLogging |
Applicable data source sections |
|
UseAdapterUsername |
Applicable security adapter sections |
Siebel Security Guide |
UseRemoteConfig |
Applicable security adapter sections |
Siebel Security Guide |
UsernameAttributeType |
Applicable security adapter sections |
Siebel Security Guide |
UserSWFName |
|
Configuring Siebel Business Applications |
UserSWSName |
|
Configuring Siebel Business Applications |
Version |
|
|
WebTemplatesVersion |
|
Siebel Performance Tuning Guide |
XdoDir |
|
Siebel Reports Guide |
Description of Siebel Application Parameters
The following table describes several Siebel application parameters. These parameters appear in the [Siebel] section of the configuration file and apply to Siebel Mobile Web Client or Siebel Developer Web Client.
For the Siebel Web Client, the parameters are defined as server parameters on the Application Object Manager, rather than defined in a configuration file. Some parameters also apply to Siebel Tools and might be defined in the tools.cfg file.
Table Siebel Application Parameters
Name |
Description |
---|---|
AccessDir |
Specifies the directory where Microsoft Access is installed. |
ApplicationName |
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. |
ApplicationSplashText |
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, then ApplicationSplashText is set to Siebel Sales by default. |
ApplicationTitle |
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 is set, in the file uagent.cfg, to Siebel Call Center. |
CaptionPrefix |
Allows customizing of the title in the upper-left corner of the Siebel client application. Reads Siebel by default. |
ClientRootDir |
Specifies the directory where the Siebel client software is installed. |
ComponentName |
Specifies the Siebel Anywhere configuration that is used during version check. Navigate to the Administration - Siebel Anywhere 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 CRM applications used at one facility with the version used at another facility, then 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, then the maximum character length for the Upgrade Component name is 40. |
DataSource |
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. |
DockRepositoryName |
The value matches the Siebel repository used for generating the Siebel runtime repository. |
EnablePersonalization |
Must be set to True to activate the personalization (content targeting) functionality. Siebel workflow processes will not execute properly until personalization events are reloaded. |
EnableScripting |
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. |
LocalDbODBCDataSource |
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 CRM applications and in Siebel Tools. Do not modify it, because it is already correctly configured for the Siebel client or Siebel Tools. |
MaxDepthOfTheQuery |
Allows you to increase the maximum parse depth of a query with a large search specification, including, for example, a large number of OR or AND clauses. You can set this parameter in the application configuration file for the Siebel Mobile Web Client or Developer Web Client, or set it in the tools.cfg file for Siebel Tools. Set it in the [InfraObjMgr] section. Alternatively, you can set this parameter for the Siebel Enterprise. The full name of the server parameter is Maximum depth of the query. For more information about this parameter, see Siebel Enterprise, Server, and Component Parameters (see Generic Parameters). |
MultiCurrency |
True or False. Enables multicurrency support. |
PersonalizationLog |
Add the following to the configuration file to view a log of all personalization activity:
where C: is the drive where you want to store the log. The log can help you debug your rules, events, and actions. |
RemoteSearchServer |
True or False. True indicates that searches are performed on a remote computer. False indicates that searches are performed on a local computer. |
RemoteSearchServerPath |
Indicates the name of the remote computer that performs searches. |
ReportsDir |
Directory where reports are installed. It is typically left blank. |
ReportsODBCDataSource |
Name of ODBC data source used to connect to external modules. |
RepositoryFile |
Name of the Siebel runtime repository to use. |
ScriptingDLL |
Name of the shared library that implements Siebel Visual Basic or Siebel eScript. If the Siebel Server runs on a UNIX server computer, and you plan to use Siebel eScript, then set the value of ScriptingDLL to sscfjs.so. |
SearchDefName |
Search definition from Siebel Tools to be used for searching. For more information about search, see Siebel Search Administration Guide. |
SearchEngine |
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, then you set it to |
SearchInstallDir |
Set this parameter to the directory where your search engine is installed. For more information about search engine administration, see Siebel Search Administration Guide. |
SharedModeUsersDir |
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 |
TempDir |
Directory where temporary files are created. |
Version |
Represents the version of a 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 view. Note: When you perform a Siebel Anywhere upgrade, you must manually upgrade files from the upgraded Siebel client directory to the Siebel Server directory. |
Data Source Parameters
This topic describes parameters that pertain to the [DataSources] section of the configuration file and to the individual data source sections that follow.
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.
This topic contains the following information:
Parameters for Data Sources Section
The following table lists data sources in the Siebel configuration file, which appear in the [DataSources] section. Each data source also has its own section specifying parameters that apply to this data source.
Table Data Sources
Name |
Function |
---|---|
Local |
Defines parameters for connecting to the local database. |
Sample |
Defines parameters for connecting to the sample database. |
ServerDataSrc |
Defines parameters for connecting to the Siebel database. |
GatewayDataSrc |
Defines Siebel Gateway parameters. |
//Sample = Sample
.
Parameters for Individual Data Source Sections
The following table lists parameters that specify properties associated with the different data sources listed under [DataSources]. Each data source section defines the properties of the particular data source.
Table Data Source Parameters
Name |
Comment |
---|---|
CaseInsensitive |
True or False. If it is True, then the client is notified to work with the database in case-insensitive mode. See also the description of the InsensitivityFactor parameter for data sources. Note: Queries against fields of type DTYPE_ID are always case-sensitive, even if the CaseInsensitive parameter is set to True. For more information, see Siebel Applications Administration Guide. |
ConnectString |
Database-dependent string that defines how to connect to the database (also referred to as the connection string). The ConnectString parameter is also used to specify the Siebel Gateway computer in the GatewayDataSrc section. In the Siebel Mobile Web Client's configuration file, you must specify the Siebel Gateway's hostname, preferably in a fully qualified form like node.domain. For more information about using connection strings for different server databases, see the Siebel Installation Guide for the operating system you are using. |
ContactLogin |
True or False. If it is True, then it indicates that the corresponding data source uses contact login, rather than employee login. Because a contact user is generally not associated one-to-one with a database account, you must use a security adapter to support contact users. If it is False, then the data source is using employee login, rather than contact login. |
DisableExecuteRetry |
True or False. When set to True, this parameter prevents the client from resending a query to the database layer if an error occurs such as a network error or session kill. |
DLL |
Name of the DLL file to use for the database connector code. The names differ depending upon whether you are using Oracle Database, Microsoft SQL Server, IBM DB2, and so on. |
Docked |
Determines which database connection the application login screen for a Mobile Web Client defaults to. For example, if Docked is True in the [ServerDataSrc] section of the configuration file and Docked is False in the [LOCAL_XE] section of the configuration file, then the application login screen defaults to the server database rather than the local database. The values used in this example are the default values. |
DockConnString |
Name of the docking server (Siebel Remote Server). It is the computer name of the Siebel Server against which the Mobile Web Client synchronizes. For information about how to format the values for this parameter, see Siebel Remote and Replication Manager Administration Guide. |
DockRecvTxnsPerCommit |
Number of transactions received by the Mobile Web Client before a commit is issued to the database. The default value for this parameter is 10. Change the setting to:
|
DockTxnsPerCommit |
Number of transactions processed before a commit is issued to the database. |
EnterpriseServer |
Name of the Siebel Enterprise Server. |
FileSystem |
Specifies how the Mobile or Siebel Developer Web Client (for administrative purposes) accesses the Siebel File System. The value of this parameter cannot exceed 2048 characters. Generally, FileSystem and other parameters identified in this table are set during the Siebel client installation. Mobile Web Client. The following scenario for setting the FileSystem parameter applies to the Siebel Mobile Web Client. Install the Siebel File System locally on a Mobile Web Client, so that it is accessible when the client is not connected to the network and can be synchronized using Siebel Remote: Set the following parameter, where FS_location is a UNC location or a drive-letter path to the location on the client computer where the local Siebel File System was installed: FileSystem = FS_location Developer Web Client. The following scenarios for setting the FileSystem parameter apply to the Siebel Developer Web Client when used for administrative purposes. Make sure that users on the Siebel Developer Web Client have physical access privileges for the Siebel File System directories:
If your networked Siebel File System resides on a UNIX server, then you require a cross-platform NFS file system mounting tool to connect from Siebel Developer Web Clients running on Windows computers. |
GatewayAddress |
Host name or IP address of the Siebel Gateway. |
Hidden |
True or False. Determines if the data source shows up in the login screen's picklist of data sources. |
InsensitivityFactor |
Set to a positive integer value (default is 2). Applies only when the CaseInsensitive parameter is True for the data source. The value controls the number of characters in each string that are treated as case-insensitive in a query. Not all database vendors support case-insensitivity efficiently, so this feature provides an approximate solution. See also the description of the CaseInsensitive parameter for data sources. The following is an example SQL WHERE clause generated when searching for an opportunity named New, when InsensitivityFactor is set to 2. WHERE ((S_OPTY.NAME LIKE 'ne%' OR S_OPTY.NAME LIKE 'Ne%'OR S_OPTY.NAME LIKE 'nE%'OR S_OPTY.NAME LIKE 'NE%') AND UPPER(S_OPTY.NAME)=UPPER('New')) This example shows that all of the permutations of the first two letters of the string New are checked. With a higher factor, the number of permutations grows exponentially, and performance suffers. Note: Do not set this parameter to a value higher than 13. |
InsUpdAllCols |
True or False. Ordinarily, when the Siebel application generates INSERT or UPDATE statements to send to the database, the actual statement contains only the columns where data is present or has changed. When there are situations where you generate many statements on a particular table, the differences in the values being updated might prevent you from using an array interface supported by the DBMS. When this feature is set to True, all of the columns are present in all INSERT and UPDATE statements. Where two statements are issued against the same table in the same business component as part of a batch operation, this setting automatically enables the statements to use any existing array feature of the DBMS. |
IntegratedSecurity |
True or False. When True, the Siebel client is prevented from prompting the user for a user name and password when the user logs in. Facilities provided in your existing data server infrastructure determine whether the user is allowed to log into the database. This parameter is set for your server data source. However, it is supported for Oracle Database and Microsoft SQL Server databases only. The default value is False. For additional information, refer to your third-party documentation. For Oracle Database, refer to the OPS$ and REMOTE_OS_AUTHENT features. For Microsoft SQL Server, refer to Integrated Security. |
MaxCachedCursors |
Specifies the maximum number of SQL cursors that can be cached in memory for a database connection. The default is 16. Caching SQL cursors can improve response time and CPU usage because an SQL cursor does not have to be prepared each time it is executed. If memory usage is not a concern, then you might consider increasing the value of this parameter. |
MaxCachedDataSets |
Specifies the maximum number of data sets that can be cached in memory for a database connection. The default is 16. A data set is the set of records that has been retrieved by the execution of a business component. Data-set caching applies only to those business components for which the Cache Data property has been set in Oracle's Siebel Tools. Caching data sets for frequently visited business components can improve response time and CPU usage. If memory usage is not a concern, then you might consider increasing the value of this parameter. |
MaxConnections |
Number of connections that can be made to the data source database server. |
MaxCursorSize |
Sets the total number of rows that can be returned in a result set. MaxCursorSize is intended for use only with IBM DB2 for OS/390 and z/OS, and must be set as described in Implementing Siebel Business Applications on DB2 for z/OS. If you are using another database, then do not set this parameter to any value other than the default value (-1), or database behavior is adversely affected. MaxCursorSize and PrefetchSize are used together, and they must be set to the same value. See also the description for the PrefetchSize parameter. |
NonSQL |
True or False. Setting that indicates that the data source does not use an SQL DBMS to retrieve its data. Use this parameter only in conjunction with a specialized business component that your company builds internally. Never use this parameter arbitrarily. |
PrefetchSize |
Sets the number of rows that the Siebel application reads initially as part of a query execution. PrefetchSize is intended for use only with IBM DB2 for OS/390 and z/OS, and must be set as described in Implementing Siebel Business Applications on DB2 for z/OS. If you are using another database, then do not set this parameter to any value other than the default value (-1), or database behavior is adversely affected. MaxCursorSize and PrefetchSize are used together, and they must be set to the same value. See also the description for the MaxCursorSize parameter. |
PrimaryEnterprise |
The name of the Enterprise Server that you want to administer from the client computer. Set this parameter to view or change information in the server administration views. |
ReverseFillThreshold |
When the current query contains many rows, it might be very inefficient for the user to click End try to display and read them all sequentially. For this reason, the customer might configure a threshold value to invert the current sort, re-execute the query, and fill the data buffers from the end. These internal operations are hidden from the user. |
SqlStyle |
Indicates what kind of SQL to send to the database that you are using. When generating SQL to send to a DBMS, the application constructs the SQL statement to suit the particular DBMS. The value of this parameter is automatically set by the Siebel client installer or by initial server configuration, according to database information that you specified. The local database or Sample Database, based on Oracle Database XE, uses OracleCBO (the same as Oracle Database Enterprise). IBM DB2 and Microsoft SQL Server use the style applicable to the particular DBMS. |
TableOwner |
In a database, tables are identified by both their owner and their name. When queries that reference tables are issued, the table owner must be included in those references (for example, SIEBEL.S_EVT_ACT, where SIEBEL is the table owner). Siebel Server infrastructure and system management components, such as SRBroker and SRProc, read the value of this parameter. For Application Object Manager server components, you specify the table owner by setting a value for the Datasource Table Owner (alias DSTableOwner) named subsystem parameter. |
UpperCaseLogin |
The default is False. If it is set to True, then the user ID, when a user logs in, is converted to uppercase before it is sent to the database for authentication. This value is applicable only if the database is used for authentication. The value of the parameter is ignored when SecurityAdapter is set to a nonempty value. Use this parameter if you want to enforce a policy of having all of the database accounts in uppercase on a case-sensitive database, but you do not want users to worry about case when they type in their user names. Note: The value of UpperCaseLogin does not affect the password. |
UseDictionaryinTransaction Logging |
To avoid the diccache.dat creation while using the Developer Web Client connected to the database server, add this parameter to the [ServerDataSrc] section in the configuration file.
Note: This parameter is not supported if you plan to use Siebel Remote and synchronize between client and server. If you plan to perform only testing and administration tasks connected against the database server, then you will not be affected. For Siebel Remote testing, use the Siebel Web Client and the Siebel Mobile Web Client. |