Siebel Mobile Application Settings

The following table describes the application settings that you can configure for Siebel Mobile disconnected applications.

Product Group	Server Components
Application Directory	Single-line setting. Specifies the working directory (UNC path) for the Siebel Mobile disconnected application synchronization component where user data is stored. A valid value for Application Directory is as follows: \\server name\directory name For more information, see Configuring the Application Directory Setting Configuring the Application Directory Setting for Multiple Servers.
DBExtractThreadLoad	Single-line setting. This parameter enables thread-throttling functionality for database-extraction threads. DBExtractThreadLoad is the load (or weight) that is assigned to each individual, database-extraction thread. For each running database-extraction thread, this load value is used to determine the total system load, which is then compared with the MaxTotalThreadLoads value. A new thread is started only if the total system load does not exceed the MaxTotalThreadLoads value. A value of zero disables throttling of the database-extraction threads. The default value is 2. A valid value for DBExtractThreadLoad is any integer greater than or equal to zero (0).
DefaultBusObj	Multi-line setting. This parameter is used to force the extraction of a business object and its designated business components. DefaultBusObj is typically used when a business component is not extracted because it is not specified by using the DefaultView setting and is required for the application to function correctly. This setting is also used to designate business components that function as reverse business objects (RBOs). For more information about QBE (query by example) structure, see Constructing Business Component Filters for Siebel Mobile. Valid values for DefaultBusObj are as follows: Business Object Name|Visibility Level||Business Component Name|QBE query construct For more information, see Configuring the DefaultBusObj Setting Value.
DefaultFields	Multi-line setting. This parameter is used to force the extraction of fields for a particular business component, which is typically the case where the business component is extracted through the DefaultView setting. However, because the field is not visible on the applet, it is not extracted. Also when a hidden business component is extracted through the DefaultBusObj setting, it is necessary to specify all of the fields that must be extracted for the business component. If no fields are specified using this setting, then the business component is not extracted in this case. Valid values for DefaultFields are as follows: Business Component Name|Field1|Field2|… For more information, see Extracting Non-UI Fields During Synchronization.
DefaultHandheldInsertMode	Single-line setting. This parameter enables the processing of insert operation failures for synchronization. If DefaultHandheldInsertMode is enabled, then synchronization stops when it encounters a data conflict during an insert operation. Users or administrators must resolve the data conflict before synchronization can resume. This feature is disabled by default. Valid values for DefaultHandheldInsertMode include one of the following: NoFail FailOnError
EnableBatchExtraction	Single-line setting. This parameter enables or disables the batch synchronization functionality. Disable batch synchronization is the default. For more information about batch synchronization, see Configuring Batch Synchronization for Siebel Mobile.
EnableThrottleDebugMode	Single-line setting. This parameter enables or disables thread-throttling functionality. Valid values for EnableThrottleDebugMode are TRUE or FALSE.
MaxThrottleWaitTime	Single-line setting. This parameter is used for thread-throttling functionality. MaxThrottleWaitTime is the upper limit on the amount of time (in minutes) that any individual throttling request is allowed to wait. The default value is 5. A valid value for MaxThrottleWaitTime is any integer greater than or equal to zero (0).
MaxTotalThreadLoads	Single-line setting. This parameter is used for thread-throttling functionality. It defines the maximum number of total thread loads (determined by DBExtractThreadLoad and TranProcThreadLoad for each type of thread) that will be allowed to run for the scope defined by ThreadThrottleScope. If a throttling request is made that causes this maximum to be exceeded, then the requesting thread is delayed. The default value is zero, which disables the throttling mechanism. A valid value for MaxTotalThreadLoads is any integer greater than or equal to zero (0).
ThreadThrottleScope	Single-line setting. This parameter is used with thread-throttling functionality. It defines the scope of the thread-throttling mechanism by using one of two different modes: Process Thread. Where thread throttling occurs independently in each process. Application. Where thread throttling occurs in all processes running the same synchronization application on a single server. Only the first character of the ThreadThrottleScope parameter is used to determine the value. All other characters are ignored. Thus aardvark is interpreted as Application. Case is also ignored. The default value is Application. Valid values for ThreadThrottleScope include Application or Process Thread.
TranProcThreadLoad	Single-line setting. This parameter is used with thread-throttling functionality. It defines the load (or weight) that is assigned to each individual, transaction-processing thread. For each running transaction processing thread, this load value is used to determine the total system load, which is then compared with the MaxTotalThreadLoads value. A new thread is started only if the total-system load does not exceed the MaxTotalThreadLoads value. A value of zero disables thread throttling of the transaction-processing threads. The default value is 3. A valid value for TranProcThreadLoad is any integer greater than or equal to zero (0).
TranProcThreshold	Single-line setting. This parameter is used with thread-throttling functionality. It specifies the minimum time (in minutes) that the Transaction Processor continues processing transactions before performing a handshake with the client. After this value is exceeded, a handshake occurs instead of starting to process the next transaction. Doing so prevents the client from timing out the session when thread throttling is enabled. The default value is 5. A valid value for TranProcThreshold is any integer greater than or equal to zero (0).