Roadmap for Configuring Incremental Synchronization for Siebel Mobile Disconnected Applications

To configure incremental synchronization for Siebel Mobile disconnected applications, perform the following tasks:

1. "Enabling Incremental Synchronization for Siebel Mobile Disconnected Applications"

2. "Configuring the Object Mappings for a New Business Component"

3. "Enabling Modification Tracking for Siebel Mobile Disconnected Application Clients"

Configuring the Object Mappings for a New Business Component

The following procedure shows you how to configure the object mappings for a new or customized business component.

To configure the object mappings for a new business component 

1. Log in to Siebel Tools and do the following:

   1. Locate the new business component that you want and its corresponding base table name, and make a note of the object mappings in the table.

   2. If the new business component is a child that has a many-to-many relationship with its parent business component, then locate the corresponding parent business object and make a note of the intersection table name.

   3. If the new business component contains a picklist business component, which does not exist in the object mapping table, then locate the corresponding picklist business object and make a note of the table name.

2. Log in to your Siebel business application, and configure the object mappings as follows:

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

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

   3. Add all the required business component-to-table object mappings as follows:

      • Click New to add each new entry.

      • Set Table to the table name.

      • Set Business Component to the business component name.

      For example, to map Account to the S_PARTY table, set Business Component to Account and set Table to S_PARTY, and so on.

   4. If required, configure the intersection table mappings as shown in Step c.

      For all intersection table mappings, note that the business component name and the table name must be the same. So if the name of the intersection table is S_CON_ADDR, then click New to add a new entry, and set Table to S_CON_ADDR and set Business Component to S_CON_ADDR.

   5. If required, configure the picklist table mappings as shown in Step c.

3. Click the Settings tab, and set the Purge Interval to 30 if not already done so.

Enabling Modification Tracking for Siebel Mobile Disconnected Application Clients

Use the following procedure to enable modification tracking for Siebel Mobile disconnected application clients.

To enable modification tracking for Siebel Mobile disconnected application clients 

1. Log in to the Siebel application as a user with administrator privileges.

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

3. Locate and select the mobile client that you want from the Mobile Clients list, then complete the following field:

   Mobile Application Name. Select the appropriate mobile application for this node.

   For information about how to configure a new client, see "Configuring the Mobile Node for Siebel Mobile Disconnected Application Users".

4. Run database extract (dbxtract) for this mobile client, and then restart txnproc and txnroute.

   After dbxtract is run, a full data and metadata download is enforced on the mobile client by Siebel Mobile when the mobile client next sends a synchronization request to the Siebel Server.

   For information about how to run database extract, see "Running Database Extract for Siebel Mobile Disconnected Application Users".

   
   

   Note: If you remove a mobile application from the Mobile Application Name field in the Mobile Clients view and then add either the same or a new mobile application, then Siebel Mobile enforces a full data and metadata download on all corresponding mobile clients (or mobile application users) who are configured to use the mobile application, when the mobile clients next send a synchronization request to the Siebel Server. Removing a mobile application from the Mobile Clients view terminates the relationship between the mobile application and the mobile clients, and renders the application repository objects invalid. Adding a mobile application, regardless of whether the application was previously added or whether the application is new, creates a new relationship between the mobile application and the mobile clients. Hence a full data and metadata download is required.