Configuring Application Settings for Siebel Mobile Disconnected Applications

The Administration - Siebel Mobile, Application Administration view lists all the mobile applications that are available within your enterprise. From the Application Administration view, you c an create new application settings, change default settings, and administer settings that have already been created. Some of the settings are described in Table 4-1.

The following tabs, which are available from the Application Administration view, are used by the synchronization engine to extract application definition and user data:

• Business Component Filters. Use this tab to define the synchronization filter settings for business components. For more information, see "Adding Business Component Filters for Siebel Mobile Disconnected Application Users."

• Business Object Filters. Use this tab to define the business object level filters, which restrict data that is downloaded to the mobile client application upon synchronization. For more information, see "Adding Business Object Filters for Siebel Mobile Disconnected Application Users."

• Settings. Use this tab to define parameter settings for your application. For more information, see the following:

  • "Configuring a New Application Setting"

  • "Configuring a DefaultBusObj Setting Value with More Than 2000 Characters"

  • "Extracting Non-UI Fields During Synchronization"

  • "Configuring the Application Directory Setting"

  • "Application Settings for Siebel Mobile Disconnected Applications"

Note: You use the User Administration view and its tabs in a similar way to how you use the Application Administration view and its tabs, except that you are configuring business components, business objects, and user settings at the user level rather than at the application level. The mobile application is populated with the user administration data when the user performs a synchronization. The user administration settings override the Siebel Server component-level and application-level settings.

Configuring a New Application Setting

The following procedure shows how to configure a new application setting. This task is a step in "Roadmap for Setting Up Siebel Mobile Disconnected Applications".

To configure a new application setting 

1. Navigate to the Administration - Siebel Mobile screen, then the Application Administration view.

2. Select the appropriate mobile application from the top applet.

3. Click the Settings tab, and then click New.

4. Click the name field, and select the setting you require.

5. Click the Value field, and enter the text of the setting.

Configuring a DefaultBusObj Setting Value with More Than 2000 Characters

The Siebel Mobile disconnected application setting value field has a limit of 2000 characters. The following procedure shows how to create a default business object (DefaultBusObj) setting value with more than 2000 characters.

To configure a default business object setting value with more than 2000 characters 

1. Break the value into multiple lines of DefaultBusObj settings.

2. Enter these settings using the same DefaultBusObj value format:

   BusObj|Visibility|Query|BusComp_1|query specifications_1[|BusComp_n|query specifications_n]
   

   When defining multiple lines of DefaultBusObj settings for a single business object, all view modes and filters must match. If a business component is found in multiple DefaultBusObj settings for a single business object, then the business component's query specifications are concatenated with a space and appended to the previous business component's query specifications. You must be aware of this effect in order to decide if both query specifications must be combined with an OR operator or AND operator.

   The DefaultBCuserProps and DefaultFields settings for a single business component can also be broken into multiple lines of settings if their values exceed 2000 characters. These settings must all be entered using the same value format as well:

   BusComp|BCUserProp_1[|BCUserProp_n] or BusComp|Field_1[|Field_n]
   

Extracting Non-UI Fields During Synchronization

Fields displayed in the UI and fields that are part of the calculated field are extracted to the Siebel Mobile disconnected application during the synchronization process. However, not all fields in the business component are extracted. Often, you might have to refer to other fields in the user property that are either not exposed in the UI or they are calculated fields. For example, a user enters a value in the Amount field through the UI. This action updates a value in the Status field, but the Status field is not displayed in the UI and therefore is not automatically extracted to the Siebel Mobile disconnected application. Such fields must be sent to the Siebel Mobile disconnected application during synchronization.

Note: Calculated fields are downloaded from the Siebel Server and appear in the Siebel Mobile disconnected application. In offline mode, the calculated values for the new records created are set based on the fields available offline.

To extract specific non-UI fields during synchronization 

1. Navigate to the Administration - Siebel Mobile screen, then the Application Administration view.

2. Click the Settings tab.

   You use the Settings tab to define the parameter settings for your application.

3. Select, for example, Siebel ePharma Mobile Application Name.

4. Click Query, enter Account, and click Execute Query.

5. Select the DefaultFields Directive for the Account business component, and add the following to the end of the Value column:

   |Start Time|End Time
   

Configuring the Application Directory Setting

Application Directory is an application-level parameter that is defined in the Administration - Siebel Mobile, Application Administration, Settings view. The default value for this parameter in the standard product is hhsync\app_name, where app_name is the name of the application, such as salesm or servicem, and so on. You can set this parameter using the following procedure. This task is a step in "Roadmap for Setting Up Siebel Mobile Disconnected Applications".

To configure the Application Directory setting 

1. Log in to the Siebel Server using a user ID with a Siebel administrator responsibility.

2. Navigate to the Administration - Siebel Mobile screen, then the Application Administration view.

3. Select the appropriate application (for example, Siebel ePharma Mobile) from the top applet.

4. Click the Settings tab, and set the value of the Application Directory parameter to be the shared network location using a UNC format, for example, as follows:

   \\shareddsk\hhsync\phm
   

5. Save the change.

6. Restart the Siebel Application Object Manager server component for the Siebel Mobile disconnected application.

   
   

   Note: The location for the Application Directory must be a networked, high performance, highly available drive. SAN (Storage Area Network) or NAS (Network Access Server) with a high RAID (Redundant Array of Independent Disks) rating is a good option for this purpose.

   
   

Configuring the Application Directory Setting for Multiple Servers

The following procedure shows you how to set the Application Directory parameter for Siebel Mobile disconnected applications in a multiple server or hybrid environment (for example, Microsoft Windows and UNIX).

To configure the Application Directory setting for multiple servers 

1. Set up a shared CIFS (or Samba) FileSystem folder between Windows and UNIX servers.

   On Windows for example, a folder called mobile is created on the c:\ drive (c:\mobile) and Siebel Servers are installed under C:\23044\ses\siebsrvr.

   On Linux for example, a folder called mobile is mounted as /somepath/mobile (which points to the Windows folder) and Siebel Servers are installed under /export/home/siebelqa1/23044/ses/siebsrvr.

2. Create the hhsync subfolder c:\mobile\hhsync as follows:

   mkdir c:\mobile\hhsync

3. On Windows, use mklink to link siebsrvr\hhsync to the shared folder c:\23044\ses\siebsrvr as follows:

   C:\23044\ses\siebsrvr> mklink /D C:\23044\ses\siebsrvr\hhsync
   c:\mobile\hhsync
   

4. On UNIX, link siebsrvr/hhsync to the shared folder as follows:

   ln -s /somepath/mobile/hhsync
   /export/home/siebelqa1/23044/ses/siebsrvr/hhsync
   

5. Log into the Siebel Server using a user ID with a Siebel administrator responsibility, and then do the following:

   1. Navigate to the Administration - Siebel Mobile screen, then the Application Administration view.

   2. Select the appropriate application (for example, Siebel ePharma Mobile) from the top applet.

   3. Click the Settings tab, and set the value of the Application Directory parameter to hhsync/phm.

      On Microsoft Windows, this points to: .\siebsrvr\hhsync\phm.

      On Linux, this points to: ./siebsrvr/hhsync/phm.

   4. Save the change and restart the Siebel Application Object Manager server component for the Siebel Mobile disconnected application.

Application Settings for Siebel Mobile Disconnected Applications

Table 4-1 describes the application settings that you can configure for Siebel Mobile disconnected applications.

Table 4-1 Application Settings 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 Disconnected Applications". Valid values for DefaultBusObj are as follows: Business Object Name|Visibility Level||Business Component Name|QBE query construct For more information, see "Configuring a DefaultBusObj Setting Value with More Than 2000 Characters".
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 Disconnected Applications".
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).