Setting Up Siebel Mobile Disconnected Applications

This chapter describes how to set up Siebel Mobile disconnected applications. It includes the following topics:

Note: The procedures in this guide assume that you do not use the Tree navigation control option to access screens and views. However, you can choose to use the Tree navigation control if required. For more information about setting navigation options, see Siebel Fundamentals Guide.

Roadmap for Setting Up Siebel Mobile Disconnected Applications

To set up Siebel Mobile disconnected applications, review and perform the following tasks:

Review Load Balancing Support for Synchronization before setting up Siebel Mobile disconnected applications.
Review Requirements for Setting Up Siebel Mobile Disconnected Applications
Adding Object Managers for Siebel Mobile Disconnected Applications
Siebel Application Object Manager Parameters for Siebel Mobile Disconnected Applications
Process of Configuring Siebel Server for Siebel Mobile Disconnected Applications
Setting Up Users for Siebel Mobile Disconnected Applications
Set up the business component data filters for Siebel Mobile.

For more information, review Guidelines for Developing Data Filters for Siebel Mobile Disconnected Applications and see Data Filtering for Siebel Mobile Disconnected Applications.
Set up the default fields for non-UI business component fields.

The Handheld Business Service only downloads fields that are exposed in the UI. To download the non-UI fields, you must configure the field details. For more information, see Configuring Application Settings for Siebel Mobile Disconnected Applications.
Set up the default Business Objects to extract the business objects and the business components which are not extracted as part of UI.

The Handheld Business Service only downloads business components that are exposed in the UI. To download any additional non-UI fields, you must configure the default business objects in the Administration - Siebel Mobile, Application Administration, Settings view. For more information, see Configuring Application Settings for Siebel Mobile Disconnected Applications.
Monitoring Synchronization Sessions for Siebel Mobile Disconnected Applications
Customizing Siebel Mobile Applications

Requirements for Setting Up Siebel Mobile Disconnected Applications

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

Before starting to set up Siebel Mobile, you must meet the following requirements.

The installed software for Siebel Mobile is Siebel CRM 17.x or any Siebel CRM 18.x release prior to Siebel CRM 18.9 Update.
Install Siebel CRM 18.9 Update for new installations or for existing installations. For more information about new installations and migration installations for existing installations, see Siebel Installation Guide for the operating system you are using.
For a migration installation for an existing installation, run the Siebel Incremental Repository Merge to update your database to the latest Siebel CRM.
For more information about using Siebel Incremental Repository Merge, see Siebel Database Upgrade Guide.
For new installations, running Siebel Incremental Repository Merge is not required. Install a new Siebel database for Siebel CRM.
All standard Siebel Server and Siebel Application Interface configurations have been carried out before you run any Siebel Mobile script on the Siebel Server and Siebel Application Interface.
- New installations. Complete the standard Siebel Server and Siebel Application Interface installation and configuration tasks to create the object managers for the language or languages that you choose to deploy.
- Migration installations. Run the script to add the object managers for new Siebel Mobile applications not present in any prior installation, for the existing installed and deployed languages. For Siebel Application Object Managers, run the object manager script for each language that you are deploying. After installation, run the Siebel Management Console and configure the Application Interface to add the new applications.
- Additional languages. After a migration installation, run the object manager script once for each installed language. If you are adding a new language to an existing installation, then run the object manager script for that language, but only after first completing all the standard tasks to install and deploy a new language as detailed in Siebel Installation Guide for the operating system you are using.
Note: The Siebel Bookshelf is available on Oracle Technology Network (http://www.oracle.com/technetwork/indexes/documentation/index.html) and Oracle Software Delivery Cloud. It might also be installed locally on your intranet or on a network location.

Adding Object Managers for Siebel Mobile Disconnected Applications

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications and is required under the following conditions:

For new installations. The Siebel Application Object Managers are created by default in the language or languages selected during Siebel CRM installation. For example, if ENU and ESP are the languages selected, then the Siebel Application Object Managers shown in the following table are automatically added for ENU and ESP so it is not necessary to add them again. If you want to run your Siebel Mobile application subsequently in a new language, then you must run the new_compdef_sia script for each language that must be supported, but only after first completing all the standard tasks to install and deploy a new language.
For migration installations. You must run the new_compdef_sia script to add the object managers for new Siebel Mobile applications not present in any prior installation, for each language that is installed and deployed on the Siebel Server.
For additional languages. You must run the new_compdef_sia script after adding a new language on the Siebel Server, but only after first completing all the standard tasks to install and deploy a new language.
For more information about new installations, migration installations, and additional language installations, including the standard tasks to install and deploy a new language, see Siebel Installation Guide for the operating system you are using.

Table Siebel Application Object Managers for Siebel Mobile

Application	Application Object Manager
Siebel Mobile application for Siebel Pharma	ePharmamObjMgr_enu ePharmamObjMgr_esp
Siebel Mobile application for Siebel Consumer Goods Note: Supported only in online mode.	CGmObjMgr_enu CGmObjMgr_esp
Siebel Mobile application for Siebel Sales	SalesmObjMgr_enu SalesmObjMgr_esp
Siebel Mobile application for Siebel Field Service	ServicemObjMgr_enu ServicemObjMgr_esp
Siebel Mobile application for Siebel Finance Note: Supported only in online mode.	FinsmObjMgr_enu FinsmObjMgr_esp

The following procedure shows you how to run the new_compdef_sia script to add new object managers for Siebel Mobile applications. Running the script adds the object managers for the applications that are in the HandheldSync and HandheldSyncSIS component groups. You perform the following procedure only for migration installations to add the object managers for new Siebel Mobile applications not present in any prior installation.

To add object managers for Siebel Mobile

Stop the Siebel Server.
Stop the Siebel Gateway and make a backup of the Siebel Gateway registry.
For instructions on how to do this type of backup, see Siebel System Administration Guide.
Restart the Siebel Gateway.
Set the SIEBEL_HOME environment variable to the SES_HOME/siebsrvr directory.
Navigate to the following folder from, for example, a command prompt:
```
SES_HOME/siebsrvr/bin/<LANG>
```

Execute one of the commands shown in the following table, as required:

Operating System	Command
Microsoft Windows	Execute the following command on Windows: new_compdef_sia.bat <GATEWAY>:<PORT> <ENTERPRISE> <USERNAME> <PASSWORD> <LANG>
Linux or UNIX	Execute the following command on Linux or UNIX: new_compdef_sia.ksh <GATEWAY>:<PORT> <ENTERPRISE> <USERNAME> <PASSWORD> <LANG>

Operating System

Command

Microsoft Windows

Execute the following command on Windows:

new_compdef_sia.bat <GATEWAY>:<PORT> <ENTERPRISE> <USERNAME> <PASSWORD> <LANG>

Linux or UNIX

Execute the following command on Linux or UNIX:

new_compdef_sia.ksh <GATEWAY>:<PORT> <ENTERPRISE> <USERNAME> <PASSWORD> <LANG>

When prompted, verify that the parameters passed are correct.
Start the Siebel Server.
Enable the component groups for Siebel Mobile.

For more information, see Enabling the Component Groups for Siebel Mobile Disconnected Applications.

Siebel Application Object Manager Parameters for Siebel Mobile Disconnected Applications

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

Siebel Application Object Manager parameters must be set on every Siebel Server that will support Siebel Mobile, and for each language that must support Siebel Mobile disconnected applications. For more information about Siebel Application Object Manager parameters and the Siebel Server Manager, see Siebel System Administration Guide. For more information about enabling Siebel Open UI for Siebel Application Object Managers, see Siebel Installation Guide for the operating system you are using.

The Siebel Application Object Manager parameters settings shown in the following table are set by default (except for EnableOfflineMode), and are required for all Siebel Mobile disconnected applications.

Table Siebel Application Object Manager Parameters for Siebel Mobile

Parameter Name	Parameter Setting
AppletSelectStyle	AppletSelectStyle="Applet Select"
EnableInlineForList	EnableInlineForList=Never
EnableOfflineMode	EnableOfflineMode=True
ShowWriteRecord	ShowWriteRecord=TRUE

For Siebel Mobile disconnected, you must set the EnableOfflineMode application object manager parameter to TRUE to enable offline mode for the following applications:

Siebel Mobile disconnected application for Siebel Pharma
Siebel Mobile disconnected application for Siebel Sales
Siebel Mobile disconnected application for Siebel Field Service

EnableOfflineMode is set to FALSE by default. Before you can work in offline mode, you must enable offline mode. The following procedure shows you how to set the EnableOfflineMode application object manager parameter.

To set application object manager parameter, EnableOfflineMode

Log in to the srvrmgr.
Type the following command at the srvrmgr command line for each mobile application in the appropriate language.
For U.S. English for example, type the command as follows:
```
change param EnableOfflineMode=True for comp XObjMgr_enu 
```
For each language that you want to set up for your mobile application, substitute the language in question for _enu and replace XObjmgr with the name of the application object manager (as shown in the previous table). For example, use _esp to enter the command for the Spanish language on ePharmamObjMgr as follows:
```
change param EnableOfflineMode=TRUE for comp ePharmamObjMgr_esp
```

Process of Configuring Siebel Server for Siebel Mobile Disconnected Applications

This process is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

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

Enabling the Component Groups for Siebel Mobile Disconnected Applications

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications and Guidelines for Developing Data Filters for Siebel Mobile Disconnected Applications.

The component groups for Siebel Mobile must be enabled on the supported Siebel Server. You can enable the component groups for the following Siebel Mobile disconnected applications on Microsoft Windows or on UNIX:

ePharma Mobile Object Manager (<Lang>)
Sales Mobile Object Manager (<Lang>)
Service Mobile Object Manager (<Lang>)

To enable the component groups for disconnected applications

Log in to the Siebel Web application, and then do the following:
1. Navigate to the Administration - Server Configuration screen, Enterprises, then the Component Groups view.
2. Query for the HandheldSync* component group.
  The following component groups are returned:
  - HandheldSync
  - HandheldSyncSIS
3. For each of these component groups, do the following:
  - Select the component group, and then click the Enable button.
  - In the Component Group Assignments applet, click the Enable button for the required Windows or UNIX Server.
4. If required, go to the LifeSciences component group, and enable it as described in the previous substep.
Note: The LifeSciences component group must only be enabled if using the Siebel Pharma application.
Stop, and then restart the Siebel Server.

Setting Up the Disconnected Mobile Synchronization Component Group

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

The following procedure shows you how to set up MobileSync, the disconnected mobile synchronization component group for Siebel Mobile disconnected applications. The purpose of this task is to support synchronization in disconnected mode.

Note that by default, all of the following are configured for the Siebel Mobile application for Siebel Pharma so it is not necessary to configure them again for the application:

MobileSync. The disconnected mobile synchronization component group.
MobileDbXtract. The data extraction component (in this case, the Siebel Mobile disconnected component) that is to extract data based on buscomp (the business component). The output is stored in the dmData.txt file, which will be synchronized with the Siebel Mobile client.
You must use MobileDbXtract as a template and configure it accordingly to create the data extraction component for other mobile applications (such as, Siebel Field Service Mobile), as shown in the following procedure.
BatchSync. Batch synchronization.

To set up the Disconnected Mobile Synchronization component group

Connect to the server manager on your server computer and run the following command to see if the MobileSync component group has been enabled or not:
```
list compgrps
```
If required, enable the MobileSync component group as follows:
1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.
2. Select the Component Groups tab, and then query for MobileSync in the Alias field.
3. Click the Enable button.
4. In the Component Groups Assignments applet, click the Enable button for the required Windows or UNIX server.

Create the data extraction component, using MobileDbXtract as a template, for the mobile application as follows:

Note: The data extraction component is the Siebel Mobile disconnected component that is to extract data based on buscomp (the business component). The output is stored in the dmData.txt file, which will be synchronized with the Siebel Mobile client.

Log in to the Siebel application as a user with administrator privileges.
Navigate to the Administration - Server Configuration screen, then the Enterprises view.
Click the Component Definitions tab, and then query for MobileDbXtract in the Alias field.
Using MobileDbXtract as a template, create a similar data extraction component for the mobile application you want to set up MobileSync for as follows:
- Click Menu, then Copy Record.
- In the Component field, type the name of the new data extraction component.
  For example, type in ServicemDbXtract_enu to create a data extraction component for the Siebel Mobile application for Siebel Field Service where _enu indicates the language (English) supported. Type in ServicemDbXtract_jpn for the japanese language, and so on.
- Select MobileSync from the Component Group drop-down list.
- In the Description field, type a description of the new component.

In the Component Parameters applet, configure the component parameters for the data extraction component (in this case, ServicemDbXtract) with the values shown in the following table:

Name	Value
Application Name	Siebel Field Service for Mobile Note: The application name must be exactly the same as the mobile application name. You can find the mobile application name using the srvrmgr command line as follows: `list param CFGApplicationName for comp ServicemObjMgr_enu.`.
Language Code	ENU

Click Activate to activate the data extraction component for the mobile application.
Click Synchronize to synchronize the data extraction component for the mobile application.

Note: This synchronization is a server administration task, which must be done for batch mode server components after certain types of operations, and is not related to the data synchronization that the components perform. For more information, see Siebel System Administration Guide.

Configure the settings for the mobile application as follows:
1. Navigate to the Administration - Siebel Mobile screen, then the Application Administration view.
2. Select the mobile application from the upper applet. For example, select Siebel Field Service for Mobile.
3. Click the Settings tab, and then do the following:
  - Click New, select Data Extraction Component in the Name field, and then select the actual data extraction component (in this case, ServicemDbXtract) in the Value field. The name of the data extraction component must be the same as the name defined in Step 2.
  - Click New, select Enable Batch Extraction in the Name field, and then select True in the Value field. For more information, see Configuring Batch Synchronization for Siebel Mobile Disconnected Applications.
  - Set any other mobile application settings. For example, set PurgeInterval, Default Busobj, and Application Directory. For more information, see Configuring Siebel Mobile Disconnected Application Settings.
4. Restart the Siebel Server for the changes to take effect.
5. Check the status of the MobileSync component group by doing one of the following:
  - From the command line, run the following command:
```
list comp for compgrp MobileSync
```
  - From the UI, navigate to the Administration - Server Management screen, then the Components view.
Create a mobile client (such as SPORTER) and perform the database extraction by doing one of the following:
- From the command line, run dbxtract using the following command:
```
start task for comp dbxtract with client="SPORTER-MOBILE"
```
- From the UI, navigate to the Administration - Server Management screen, then the Jobs view, and select the Dbxtract Component Job. Then in the Job Parameters applet, add the Client Name parameter and its value, for example, as follows:
```
ClientName=SPORTER-MOBILE
```
Note: Dbxtract is the Siebel Remote component used to extract data based on database tables. Running dbxtract generates full user data and also the visibility database that is used to route the incremental changes to the user. Dbxtract generates the visibility database only for Siebel Mobile users that are not legacy remote users. For more information, see Running Database Extract for Siebel Mobile Disconnected Application Users.
Start the mobile application (for example, servicem/enu) and log in with the appropriate user credentials.
Test that batch synchronization is working:
- Run the following in the server manager:
```
list task for comp MobileDbXtract
```
  From the UI, you can check the status of MobileDbXtract or the component of the respective application that was created (for example, ServiceDbXtract) by navigating to the Administration - Server Management screen, then the Tasks view.
- Verify that the dmData.txt file is generated in the hhsync/<mobile-application> directory.
  For example, hhsync/phm is the directory created for Siebel ePharma Mobile, hhsync/salesm is the directory created for Siebel Sales Mobile, and hhsync/servicem is the directory created for Siebel Field Service Mobile.
  The folder structure is determined by the Application Directory value specified in the Administration - Siebel Mobile screen, Application Administration view, Settings subview.
  The dmData.txt file contains all the application data (records and business components) to be synchronized with the client.

Assigning Responsibilities to Siebel Mobile Disconnected Application Users

This task is a step in Process of Configuring Siebel Server for Siebel Mobile Disconnected Applications.

A responsibility corresponds to a set of views. Responsibilities control the views to which users have access. The following procedure shows you how to assign views to a responsibility and then users to that responsibility. For more information about setting up view access and users for Siebel Mobile disconnected, see Setting Up Selective Retrieval for Siebel Mobile Disconnected Application Views and Setting Up Users for Siebel Mobile Disconnected Applications.

To assign responsibilities to Siebel Mobile users

Log in to the Siebel application as a user with administrator privileges.
Navigate to the Administration - Application screen, then the Responsibilities view.
Query for and select the appropriate responsibility or user role.
For example, query for the following: PH Pharma Sales Rep - US Sales.
Select the Responsibilities tab, and then do the following:
1. In the lower Users applet, add users to the responsibility as required.
2. In the lower Views applet, add the appropriate views to the responsibility as required.

The following table lists the application views that are added by default as part of the seed data for Siebel Mobile, so it is not necessary to manually add the views again.

Table Siebel Mobile Disconnected Application Views

Application	Default Views
Siebel Mobile application for Siebel Pharma	LS Home Page Call View - Mobile LS Pharma Call Validation Results View - Mobile LS Pharma Call Signature Capture View - Mobile LS Pharma Signature Audit Administration View_PUI SIS HH Pharma Account Call Attendee View - Mobile SIS HH Pharma Professional Promotional Items View - Mobile SIS HH Pharma Professional Samples Dropped View - Mobile SIS HH Pharma Professional Call Products Detailed View - Mobile eDetailer Message Plan Preview View - Mobile eDetailer Presentation View - Mobile Pharma Call Literature View - Mobile Pharma Account List View - Mobile Pharma Account Contact View - Mobile Pharma Account Calls View - Mobile Pharma Account Addresses View - Mobile Pharma Account Affiliations View - Mobile Pharma Account Relationships View - Mobile Pharma Account Attachments View - Mobile Pharma Contact List View - Mobile Pharma Contact Call View - Mobile Pharma Contact Address View - Mobile Pharma Contact Best Contact Times View - Mobile Pharma Contact State Licenses View - Mobile Pharma Contact Affiliations View - Mobile Pharma Contact Relationships View - Mobile Pharma Contact Attachments View - Mobile
Siebel Mobile application for Siebel Sales	SHCE Account List View - Mobile SHCE Account Contacts View - Mobile SHCE Account Opportunity View - Mobile SHCE Account Address View - Mobile SHCE Account Activities View - Mobile SHCE Account Team View - Mobile SHCE Sales Contact List View - Mobile SHCE Sales Contact Opportunities View - Mobile SHCE Contact Team View - Mobile SHCE Contact Address View - Mobile SHCE Sales Lead List View - Mobile SHCE Sales Lead Opportunities View - Mobile SHCE Opportunities List View - Mobile SHCE Sales Opportunities Contacts View - Mobile SHCE Sales Opportunities Products View - Mobile SHCE Sales Opportunities Quotes View - Mobile SHCE Sales Opportunities Activities View - Mobile SHCE Sales Opportunities Opportunity Team View - Mobile SHCE Quote List View - Mobile SHCE Quote QuoteItem View - Mobile SHCE Quote Order View - Mobile SHCE Quote Team View - Mobile SHCE Sales Orders List View - Mobile SHCE Sales Order line Item View - Mobile SHCE Activity List View - Mobile SHCE Sales Activity Contact Form View - Mobile SHCE Sales Activity Employee Form View - Mobile
Siebel Mobile application for Siebel Field Service	SHCE Service Account Assets View - Mobile SHCE Service Account Contacts View - Mobile SHCE Service Account Entitlements View - Mobile SHCE Service Account SRs View - Mobile SHCE Service Accounts View - Mobile SHCE Service Activity Assets List View - Mobile SHCE Service Activity Attachment View - Mobile SHCE Service Activity Contact Form View - Mobile SHCE Service Activity FS Expense View - Mobile SHCE Service Activity FS Instructions List view - Mobile SHCE Service Activity FS Steps View - Mobile SHCE Service Activity Home Page View - Mobile SHCE Service Activity Invoice Signature View - Mobile SHCE Service Activity SR List View - Mobile SHCE Service Activity Time View - Mobile SHCE Service Asset Entitlements View - Mobile SHCE Service Asset List View - Mobile SHCE Service Asset Measurement View - Mobile SHCE Service Asset Reading View - Mobile SHCE Service Asset Warranty View - Mobile SHCE Service FS Activity Part Movements View - Mobile SHCE Service FS Activity Recommended Parts Tools - Mobile SHCE Service FS Invoice - Auto Invoice View - Mobile SHCE Service Invoice Line Item Details View - Mobile SHCE Service Invoice List View - Mobile SHCE Service Invoice line Item View - Mobile
Siebel Mobile application for Siebel Field Service (continued)	SHCE Service My Part Browser View - Mobile SHCE Service Order line Item View - Mobile SHCE Service Orders List View - Mobile SHCE Service Part Browser Availability View - Mobile SHCE Service Part Browser Substitute View - Mobile SHCE Service SR Activity View - Mobile SHCE Service SR Invoices View - Mobile SHCE Service SR Orders View - Mobile SHCE Service Service Request Invoice Signature View - Mobile SHCE Service Service Request View - Mobile SHCE Technician Breaks View - Mobile SHCE Technician POU View - Mobile SHCE Technician Shifts View - Mobile

Setting Up Selective Retrieval for Siebel Mobile Disconnected Application Views

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

All Siebel Mobile disconnected application views are available to users in offline mode by default. Setting up selective retrieval for mobile application views is therefore a mandatory step if you want to restrict the number of views that will be downloaded to client devices and available to users in offline mode. For more information about setting up selective retrieval for mobile application views, see the following topics:

Configuring Object Definitions for Siebel Mobile Disconnected Applications

It is not necessary to configure object definition data for the following Siebel Mobile disconnected applications because the object definitions are configured by default:

Siebel Mobile disconnected application for Siebel Pharma
Siebel Mobile disconnected application for Siebel Sales
Siebel Mobile disconnected application for Siebel Field Service

However, for information about configuring object mappings for a new or customized business component, see Configuring the Object Mappings for a New Business Component.

Configuring Siebel Mobile Disconnected Application Settings

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

Siebel Mobile disconnected application settings are configured in the Settings view. The following application settings must be configured for all applications:

Purge Interval, which is set to 30 by default.
This field specifies the duration of the Purge Interval for cleaning up the S_SD_CHG_TXN and S_DM_CHG_TXNPAR tables. These tables carry incremental data, and the volume of data continues to grow in these tables if a user fails to download data for a long time. If a user fails to download data during the Purge Interval, then all incremental data is purged by default.

Note: When the purge interval expires, the transaction router (TxnRouter) will not track the incremental changes for that node any more and a forced full download will be triggered the next time that the user goes offline (switches to disconnected mode).
Default Busobj, which is used to download the business objects that are not based on any view in the Siebel Mobile disconnected application.
Application Directory, which is used to specify the directory where user metadata is saved. For example: hhsync\phm (on Windows) or hhsync/phm (on UNIX). Forward slash must be used for UNIX.
Data Extraction Component (MobileDbXtract), which is the component used for the mobile data extraction, must be created for Siebel Mobile disconnected applications. For more information, see Setting Up the Disconnected Mobile Synchronization Component Group.

Note: The data extraction component is configured by default for Siebel ePharma Mobile so it is not necessary to configure it again for the application.
Enable Batch Extraction, which is used to configure batch synchronization for Siebel Mobile disconnected applications.

Use the following procedure to configure Siebel Mobile disconnected application settings. This task is a step in Process of Configuring Siebel Server for Siebel Mobile Disconnected Applications and Guidelines for Developing Data Filters for Siebel Mobile Disconnected Applications.

To configure Siebel Mobile disconnected application settings

Navigate to the Administration - Siebel Mobile screen, Application Administration, and then the Settings view.
Verify that Purge Interval is set to 30.
Set Application Directory, Default Busobj, and other application settings as required.
For information about all the other application settings that can be configured for Siebel Mobile disconnected applications, see the following topics:

Configuring the Mobile Node for Siebel Mobile Disconnected Application Users

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

The following steps must be performed for each Siebel Mobile disconnected application user. Setting up the mobile node triggers transaction logging for the corresponding user on the Siebel Server.

To configure the mobile node for a disconnected application user

Log in to the Siebel application as a user with administrator privileges.
Navigate to the Administration - Siebel Mobile screen, then the Mobile Clients view.
In the Mobile Clients applet, click new to create a new record with the following values:
- User ID. Click the lookup icon, and then select a user ID from the drop–down list that opens.
- Mobile Application. Click the lookup icon, and then select the appropriate mobile application name from the drop-down list that opens.
- Mobile Client. After you complete the Mobile Application field, the Mobile Client field automatically shows the following: <username>-MOBILE.
- Routing Model. Click the lookup icon, and then select Mobile Client - Standard from the drop-down list that opens.
Connect to the server manager and run dbxtract (database extract) for each application user. For more information, see Running Database Extract for Siebel Mobile Disconnected Application Users.

For more information about setting up users in Siebel Mobile disconnected applications, see Setting Up Users for Siebel Mobile Disconnected Applications.

Running Database Extract for Siebel Mobile Disconnected Application Users

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

You must run dbxtract (database extract) for every Siebel Mobile disconnected application user. Running dbxtract for each user takes approximately 3-10 minutes.

Dbxtract is the Siebel Remote component used to extract data based on database tables. Running dbxtract generates full user data and also the visibility database that is used to route the incremental changes to the user. Dbxtract generates the visibility database only for Siebel Mobile users that are not legacy remote users.

Note: If the position changes for a Siebel Mobile disconnected application user (for example, the data visibility for the user increases or decreases), then you must run dbxtract again for that user. After dbxtract is run again, a full data and metadata download is enforced on the disconnected client by Siebel Mobile when the mobile client next sends a synchronization request to the Siebel Server.

To run dbxtract from srvrmgr command line

Start a task for dbxtract with the following parameters:
```
client="<client-name>" 
```
For example, for SPORTER-MOBILE, run dbxtract as follows:
```
start task for comp dbxtract with client="SPORTER-MOBILE"
```
Run the same command for each configured Siebel Mobile disconnected application user.
You can also run dbxtract against a list of users that are specified in a command list or in a file, for example, as follows:
```
start task for comp dbxtract with 
client="SPORTER-MOBILE,LHILL-MOBILE,BFRIEDEL-MOBILE" 
```
You can check the dbxtract log file to see the status (completed or failed) for each user specified in the command.
If the transaction processor component is not running, then run the following command:
```
start task for comp txnproc 
```
To change the interval for the component, run the following command:
```
change param sleeptime=<value> for comp txnproc 
```

For more information about setting up users for Siebel Mobile disconnected applications, see Setting Up Users for Siebel Mobile Disconnected Applications and Roadmap for Configuring Incremental Synchronization for Siebel Mobile Disconnected Applications.

Configuring a Hybrid Server Setup for Siebel Mobile

This task is step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

You can set up the MobileSync component group and also Siebel Mobile disconnected applications on Microsoft Windows or any UNIX platform. The MobileSync component group includes the MobileDbXtract component which is a new component, and the following legacy remote components, which were formerly part of the Siebel Remote component group: TxnRoute, TxnProc, and DbXtract.

Use the following procedure to configure a hybrid server setup for Siebel Mobile. Configuring a hybrid server setup is optional.

Note: The complete system requirements and supported platform certifications are available from the Certifications tab on My Oracle Support. For information about Certifications, see article 1492194.1 (Article ID) on My Oracle Support.

To configure a hybrid server setup for Siebel Mobile

Navigate to the Administration - Server Configuration screen, Enterprises, and then the Component Definition view.
Query for one of the following, as required:
- ePharma Mobile Object Manager (<Lang>)
- Sales Mobile Object Manager (<Lang>)
- Service Mobile Object Manager (<Lang>)
Click Component Parameters, and then click Advanced.
Search for Siebel File System, and then update the value to the respective windows path.

Guidelines for Developing Data Filters for Siebel Mobile Disconnected Applications

This task is a step in Roadmap for Setting Up Siebel Mobile Disconnected Applications.

Siebel Mobile disconnected applications use the existing Siebel application framework for data filtering. Because Siebel Mobile disconnected applications run on a browser on a mobile device and typically on a slower network, careful analysis is required to limit the amount of data that is downloaded to client devices. Before starting to design and develop filters for Siebel Mobile disconnected applications, it is recommended that you consider the following guidelines:

Examine all of your Siebel application configuration and make a note of all the business objects and business components.
For each business object and business component, determine if there is a search specification that can be specified for daily usage, which will cut down on user data size. There is a browser storage limit of 50 MB, data filter configuration is required to limit the number of records that are downloaded to mobile devices.
Because picklists tend to carry a lot of data, especially if there is no search specification defined for the picklist, review the buscomps used in picklists and design filters for those business components.
The Siebel Mobile administration screens include views for defining filters on business objects. Make sure that you define filters for any business object that has a large data set, and that you specify one default filter (for the business object) to avoid excessive data download.

Business component data filters must be configured to control the volume of data that is downloaded for offline operations. A number of generic data filters are set up by default for Siebel Mobile disconnected applications, but you can modify the default data filters to suit your own business needs. For more information about configuring data filters, see Data Filtering for Siebel Mobile Disconnected Applications.

Customizing Siebel Mobile Applications

You can use the Siebel Open UI framework, templates, and style sheets to configure the user interface and behavior of your mobile application to address your own particulabusiness needs. You can customize the look-and-feel of your mobile application by modifying the JavaScript files. You can also deploy your own presentation models and physical renderers that might or might not use one or more third-party JavaScript plug-ins of your choice.

The following customizations are recommended:

Set up the jQuery grid (jqGrid) renderer so that the mobile application data displays in grid (tabular) format.
Set up landscape and portrait layout for mobile applications so that the views are visible on tablets.
Set up infinite scroll for mobile applications, which is a feature that allows you to scroll through records in a list applet indefinitely.
Set up Location Services so that when you tap the Route (the pin icon) in mobile applications, a map window opens showing the location details.
Set up transitions, themes, styles, and colors as required.

For more information about the Siebel Open UI templates and style sheets, about how to customize the look-and-feel of your mobile application features, and about how to implement each of these recommendations, see Configuring Siebel Open UI.

Copying and Deleting Siebel Mobile Applications

You can copy and delete duplicate copies of mobile applications in Siebel CRM as shown in the following procedure. You should not delete any Siebel-provided applications. Note the following:

When you copy a mobile application, the application plus all the associated child business component records are copied.
When you delete a Siebel Mobile application, the application plus all the associated child business component records are deleted.
Before deleting a mobile application, it is recommended that you make a copy of it first.

Note: The Deep Copy and Deep Delete user properties are used to copy or delete records in Siebel Mobile. For more information about using Deep Copy and Deep Delete to copy and delete records in child business components, see Siebel Developer's Reference.

To copy and delete mobile applications in Siebel CRM

Log in to the Siebel Server using a user ID with a Siebel administrator responsibility.
Navigate to the Administration - Siebel Mobile screen, then the Application Administration view.
Create a copy of an existing mobile application as follows:
1. Select an application from the upper applet.
  For example: Siebel ePharma Mobile (ENU)
2. Select Copy Record in the menu.
  A duplicate record is created for the mobile application with the same Name and Language Code.
3. In the Language Code field, select a different language code.
4. Verify that the copy was successful by checking the records in the following child applets: Object Definition, Modification Tracking, Business Component Filters, Business Object Filters, and Settings.
Delete a duplicate or a copy of a mobile application as follows, but do not delete any Siebel-provided applications:
1. Select an application from the upper applet.
  For example: Siebel ePharma Mobile (ITA)
2. Select Delete Record in the menu, and then OK when prompted for confirmation to delete the selected mobile application record.
  The record is deleted from the list of mobile applications.

Troubleshooting Siebel Mobile Disconnected Applications

The following table shows some common errors that users might encounter when trying to access and use Siebel Mobile disconnected applications on their mobile device.

Table Troubleshooting Siebel Mobile Disconnected Applications: Common Errors

Error Number	Error Description
1	Problem:	The application user interface is not displaying correctly on the mobile device.
	Cause:	The mobile application is not rendering correctly.
	Solution:	Check the browser that is being used on your mobile device. For information about browser requirements, see Deploying Siebel Open UI.
2	Problem:	The Siebel Mobile environment is not loading and a blank screen appears.
	Cause:	Private browsing is enabled for the browser on your mobile device.
	Solution:	Make sure that private browsing is not enabled for the browser on your mobile device. For more information, see Disabling Private Browsing.
3	Problem:	If you get errors similar to the following: Tag: swe:nav-control is not valid in this context. . . . Error creating Parameter:MobileApplication for Comp:ePharmaMObjMgr_ENU @ in CompGroup:HandheldSyncSIS Strict Flag set to FALSE, continuing with the next Object...
	Cause:	The mobile application is not rendering properly.
	Solution:	Make sure that the Siebel Application Object Manager parameters are configured correctly for your Siebel Mobile disconnected application. To set the parameters again, run the srvrmgr command for your Siebel Application Object Manager. For more information, see Siebel Application Object Manager Parameters for Siebel Mobile Disconnected Applications.
4	Problem:	The Siebel Mobile disconnected application is not showing the latest information or most recent changes.
	Cause:	One or more files that your browser has cached have changed.
	Solution:	Clear your browser cache. For more information, see Clearing the Browser Cache.
5	Problem:	The Siebel Mobile disconnected application keeps failing or locking.
	Cause:	The cause of this problem can be one or both of the following: One or more files that your browser has cached has changed. You have reached, are nearing, or have exceeded your browser cache limit. You must have a minimum of 50 megabytes (MB) of available storage on your mobile device.
	Solution:	Check your browser cache size to make sure that you have not exceeded your cache limit, remove any Web site data if required, and then clear your browser cache. For more information, see the following: Clearing the Browser Cache Checking the Browser Cache Size
6	Problem:	An error message similar to the following appears after selecting a value from a drop-down list: The applet field with name " . . . " does not exist (SBL-UIF-00289)
	Cause:	The User Agent settings for the web browser are incorrect.
	Solution:	The steps to modify the User Agent settings for the web browser are: Log in to the Siebel Business Application. Navigate to the Administration - Web Browser screen, then the Browsers view. Create a new browser by entering the browser name and version. Add the capabilities for the new browser. For example: User-Agent = Mozilla/4.0 (compatible; <browsername&version> Parent = <browsenamer&version> Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, / JumpTab = True Note that although the User Agent value looks incomplete without a closing parenthesis, this is the correct value. After applying these Siebel client parameters, restart the Siebel Mobile disconnected application. No browser errors will be returned, no matter what parameters are set on the browser side.
7	Problem:	When using Siebel Mobile disconnected applications on Solaris, an authentication popup displays after every operation.
	Cause:	The Bitmap Category object settings in the repository are incorrect. Note that this issue is seen only on Solaris platforms.
	Solution:	Modify the Bitmap Category object in the repository by updating the file name for the following categories: Leads Applet - Mobile Bitmap Name: Lead Form Applet Icon File Name value: LeadsGrey_Large_Highlight.png Quote Applet - Mobile Bitmap Name: Quo Form Applet Icon File Name value: QuoteGrey_Large_Highlight.png Opportunities Applet - Mobile Bitmap Name: Oppty Form Applet Icon File Name value: OpportunityGrey_Large_Highlight.png

The following table shows some common logging errors that users might encounter, including how to debug the errors. You can use the Log button on the application banner to review the log messages and debug information for disconnected applications, provided that logging has been enabled for the application. For more information, see Siebel Mobile Disconnected Application Logging.

Table Troubleshooting Siebel Mobile Disconnected Applications: Logging Errors

Number	Description
1	Problem:	Data created in offline mode is not visible in online mode after triggering a data upload. The log event setting is set to UpSync (to debug issues with uploading data in offline mode). Messages similar to the following examples appear in the log console: SyncThreadHandler - OnCall, UpSync failed. AppMgr - Ping, Pinging Server.... AppMgr - CheckServerConnection, Checking server connection.... AppMgr - CheckServerConnection, Network/Server is unavailable. Continuing in offline mode. AppMgr - CheckServerConnection, Checking server connection.... Failed AppMgr - Ping, Pinging Server.... Failed SyncThreadHandler - OnCall, UpSync failed.
	Cause:	The cause of this problem can be one or more of the following: Failure to upload data. Conflicts after uploading data.
	Solution:	The steps to debug using the logs are: Tap Log (the bug icon) on the application banner to open the log console. Review the log messages to check whether there was a failure in uploading data or if there was a server connection failure. In the case of an UpSync or Upload data failure message, check the server logs for more detailed information. If the logs show an UpSync completed message, then check for conflicts.
2	Problem:	After tapping Go Offline on the application banner, data extraction and the transition to offline mode is taking too long to complete. The log event setting is set to Data Extraction. Messages similar to the following examples appear in the log console: ProactiveCacheBuilder - ParseData Table:PharmaProfessionalStateLicenses , Columns: 15, No. of records: 39 ProactiveCacheBuilder - ParseData, Creating table LSMessagingPlansBC ProactiveCacheBuilder - Unique Keys, OwnerId,Version,Name The syntax for these error messages is as follows: ProactiveCacheBuilder - ParseData Table:<BusComp Name without alpha chars> , Columns: <# of columns>, No. of records: <#of records>.
	Cause:	The cause of this problem can be one or more of the following: Too many records were downloaded for some of the business components (BusComps). There were SQL errors when caching the downloaded records into the Web database. There were network issues (the server, component, or VPN is down) or appcache issues.
	Solution:	The steps to debug using the logs are: After download, tap Log (the bug icon) on the application banner to open the log console. Verify the number of records downloaded for each business component (BusComp). For BusComps with large volumes of records, modify the filter specification accordingly so that fewer records will be downloaded in future. In the case of SQL errors, fix the issue as suggested by the error message in the log console.
3	Problem:	In offline mode when trying to save a newly created record, the following error message appears: "Field '<FieldName> ' not found in BusComp."
	Cause:	The field specified in the error message was not downloaded in offline mode.
	Solution:	The steps to debug are as follows: Provided that the browser’s debugging tool to view browser resources is available, then query the Web database to verify whether the field is available in the BusComp.
4	Problem:	In offline mode when saving a newly created record, some default fields are populated with incorrect values and some fields are given validation error messages. The log event setting is set to Client System. A message similar to the following example appears in the log console: BusComp - SetDefaultValues, where expression type is : PreDefault, BC name is: Action, field: Duration Minutes, value: 15, expression: "IIf ([IsiLog] = 'N', [Work Time Min],Expr: "LookupValue(""APPOINTMENT_DURATION"", ""15"")")" The syntax for this error message is as follows: BusComp - SetDefaultValues, where expression type is : <expression type i.e. either PreDefault or PostDefault>, BC name is <bcname>, field: <field name>, value: <evaluated value>, expression: <expression> A messages similar to the following example appears in the log console: SyntaxError: Parse error on line 1: ...s Stock Employee Id - Owned by Id] = 'Y' ----------------------^ Expecting 'TOKEN_IDENTIFIER', ']', 'TOKEN_SPL_CHAR', 'TOKEN_NUMBER', got 'TOKEN_MINUS' Expression: [Is Product Allocation Type] = 'Y' && [Owned By Id] = LoginId() && [Stop Sampling Flag] = LookupValue("BOOLEAN_VALUE","N") && (([Active Flag] = LookupValue ("BOOLEAN_VALUE","Y") && [Is Stock Employee Id - Owned by Id] = 'Y' && [Is Lot Product Type] = 'Y' && [Is Lot Stock] = 'Y' && [Inventory Audit Report Id] IS NULL ) \|\| (([Inventory Flag] = 'N' \|\| [Inventory Flag] IS NULL ) && ([Lot Flag] = 'N' \|\| [Lot Flag] IS NULL ))) The syntax for this error message is as follows: SyntaxError: Parse error on line #: <error message> Expression: <expression>
	Cause:	There are issues in the Siebel Repository with the expressions configured for the PreDefault, PostDefault or ValidationSpec property of the BusComp field.
	Solution:	The steps to debug using the logs are: Tap Log (the bug icon) on the application banner to open the log console, and then tap Clear to clear any existing logs. Navigate to the view where the error occurs, and then create a new record and save it. Close any error message that appears, and then return to the log console. In the log console, search for log messages that start with the following: "BusComp - SetDefaultValues..." These log statements provide information about the PreDefault and PostDefault expressions that are set for fields when creating new records and the evaluated value. Verify whether the value was evaluated correctly. If the log console shows messages similar to the following, then the expression configured for the field in the Siebel repository is incorrect and must be fixed as indicated by the error message: SyntaxError: Parse error on line #: If the browser’s debugging tool to view the browser resources is available, then verify all expressions in the application by running the SiebelApp.Metadata.VerifyExpressions() API in the log console, and then checking the logs for errors. To get a list of all the expressions used in the application, run the SiebelApp.Metadata.GetAllExpressions() API in the log console. That is, the expressions used in all of the following: BusComp Field PreDefault, PostDefault, and ValidationSpec property. BusComp search specifications. Applet Search specification. CanInvokeMethod applet user property. OnFieldUpdateSet BusComp user properties.
5	Problem:	In offline mode when trying to save a newly created record, the following error message appears: "<FieldName> is a required Field.Enter an appropriate value.(SBL-UIJ-00126)" The log event setting is set to Client System (to debug error messages displayed in offline mode). A message similar to the following example appears in the log console: BusComp - SetDefaultValues, where expression type is : PreDefault, BC name is: Action, field: Duration Minutes, value: 15, expression: "IIf ([IsiLog] = 'N', [Work Time Min],Expr: "LookupValue(""APPOINTMENT_DURATION"", ""15"")")" The syntax for this error message is as follows: BusComp - SetDefaultValues, where expression type is <expression type /PreDefault or PostDefault>, BC name is <bcname>, field is <field name>, value is <evaluated value>, and expression is <expression>. A message similar to the following example appears in the log console: SyntaxError: Parse error on line 1:...s Stock Employee Id - Owned by Id] = 'Y' ----------------------^ Expecting 'TOKEN_IDENTIFIER', ']', 'TOKEN_SPL_CHAR', 'TOKEN_NUMBER', got 'TOKEN_MINUS' Expression: [Is Product Allocation Type] = 'Y' && [Owned By Id] = LoginId() && [Stop Sampling Flag] = LookupValue("BOOLEAN_VALUE","N") && (([Active Flag] = LookupValue ("BOOLEAN_VALUE","Y") && [Is Stock Employee Id - Owned by Id] = 'Y' && [Is Lot Product Type] = 'Y' && [Is Lot Stock] = 'Y' && [Inventory Audit Report Id] IS NULL ) \|\| (([Inventory Flag] = 'N' \|\| [Inventory Flag] IS NULL ) && ([Lot Flag] = 'N' \|\| [Lot Flag] IS NULL ))) The syntax for this error message is as follows: SyntaxError: Parse error on line #: <error message> Expression: <expression>.
	Cause:	The suspected causes of this problem are: The required `<FieldName>` is exposed in the UI with an asterisk star (*) next to it, but the field contains no value. The required `<FieldName>` is not exposed in the UI and has a PreDefault or PostDefault expression to set its value when a new record is saved. The issue here could be one of the following: The expression failed to parse. The expression includes fields with no values (where no values are set), leading to an incorrect evaluation. The expression looks up a value in a particular LOV Type, but that LOV Type is not downloaded.
	Solution:	The steps to debug this error using the logs are: Tap Log (the bug icon) on the application banner to open the log console, and then tap Clear to clear any existing logs. Navigate to the view where the error occurs, and then create a new record and save it. Close any error message that appears and then return to the log console. In the log console, search for log messages that start with the following: BusComp - SetDefaultValues... These log statements provide information about the PreDefault and PostDefault expressions that are set for fields when creating a new record and the evaluated value. Verify whether the value was evaluated correctly. If the expression contains functions similar to the following, then the expression verifies whether the LOV Type and the required value is downloaded in the local database: LookupValue(<LOV Type>,<value to look up>) If the log console shows log messages similar to the following, then the expression configured for the field in the Siebel repository is incorrect and must be fixed as indicated by the error message: SyntaxError: Parse error on line #:
6	Problem:	In offline mode, the applet shows an incorrect set of records or no records at all. The log event setting is set to Client System (to debug error messages displayed in offline mode). Messages similar to the following example appear in the log console: BusComp - SearchSpec, Name: Pharma Professional Call - Mobile, SearchSpec: (( ("Category" = "Contact Call") OR ("Category" = "Attendee Call")) OR ("Category" = "Account Call")) The syntax for this error message is as follows: BusComp - SearchSpec, Name: <BusComp Name>, SearchSpec: <BusComp Search Spec>
	Cause:	The cause of this problem can be one or more of the following: The downloaded records do not satisfy the business component search specification. The visibility of the downloaded record does not match the visibility of the view in which the record is expected to be displayed. The filter specification that is applied to download the data is incorrect.
	Solution:	The steps to debug using the logs are: Tap Log (the bug icon) on the application banner to open the log console, and then tap Clear to clear any existing logs. Navigate to the view where the error occurs. Check the logs to verify the business component search specification that was applied when the view was populated with records. Verify whether or not the missing records satisfied the search specification. If the browser's debugging tool to view the browser resources is available, then query the Web database to determine whether the required records are downloaded and the value in the PDAVisibilityTypes column for the records. Verify the visibility of records. Verify the filter specification applied to download the records.

Enabling JavaScript for Safari

To use Siebel Mobile on Safari, JavaScript must be enabled for Safari.

To enable JavaScript for Safari

Start your Safari browser.
Select Preferences from the Safari menu.
Click Security.
Select the Enable JavaScript option.
Close the Preferences window.
Close and restart Safari.

Disabling Private Browsing

If after logging into Siebel Mobile, the application environment will not load and a blank screen appears, then make sure that private browsing is not enabled for the browser on your mobile device. Private browsing mode will block any browser cache from registering, and prevent Siebel Mobile, which depends on caching, from running. The following procedure shows you how to disable private browsing in, for example, Safari on iPad.

To disable private browsing (for example, on iPad)

Tap Safari on the home screen of your iPad to start the browser.
Do one of the following as required:
1. If using Apple iOS 7, then disable private browsing as follows:
  - Tap Show Pages in the lower corner of the screen.
  - Tap Private in the lower corner of the screen
  - If prompted to close or keep all current tabs open, select an option.
  - Tap Done in the lower corner of the screen.
  Private browsing is now disabled for the mobile device, and the background color of the Safari browser changes (that is, the color gets brighter by changing to white or light gray). To enable private browsing for the mobile device, repeat this step again. When private browsing is enabled, the background color of the Safari browser is dark (that is, black or dark gray).
2. If using Apple iOS 7.1 or later, then disable private browsing as follows:
  - Tap the URL field on-screen.
  - When the keyboard opens, tap Private (over the keyboard).
  - If prompted to close or keep all current tabs open, select an option.
  Private browsing is now disabled for the mobile device, and the background color of the Safari browser changes (that is, the color gets brighter by changing to white or light gray). To enable private browsing for the mobile device, repeat this step again. When private browsing is enabled, the background color of the Safari browser is dark (that is, black or dark gray).

Clearing the Browser Cache

The process of clearing the browser cache differs from browser to browser, but typically involves selecting an option to delete the cache or temporary files in your browser’s administrative settings. After clearing your browser cache, refresh the page that you are viewing so that your browser can obtain the fresh files. The following procedure shows you how to clear the browser cache.

To clear the browser cache

On an iOS device (such as iPad):
1. Tap Settings, Safari, and then tap Clear Cookies and Data.
2. Tap Clear when prompted for confirmation to clear all cookies and data.
  This step clears all the cached data that was used to speed up browsing.
3. Refresh the page that you are viewing to obtain the latest files.
On an Android device (such as Samsung Galaxy tablet):
1. Open the Web browser on your mobile device.
2. Tap Menu, select Settings, tap Privacy and Security, and then to one or both of the following as required:
  - Tap Clear browser cache to delete locally cached content and databases.
  - Tap Clear all cookie data to clear all browser cookies.
3. Refresh the page that you are viewing to obtain the latest files.

Checking the Browser Cache Size

To successfully use Siebel Mobile in offline mode, you must have a minimum of 50 megabytes (MB) of available storage on your mobile device. The following procedure shows you how to check the browser cache size in Safari on iPad so that you are within the cache limit and how to delete the Web site data if required. The procedure is similar on Android devices.

To check the browser cache size (for example, on iPad)

Tap Settings, Safari, Advanced, and then tap Website Data.
Review the amount of data stored for each Web site and the total amount of Web site data stored on your iPad.
Remove the data for any Web site whose data has been updated recently or is no longer required as follows:
- Tap Edit.
- Select the Web site whose data you want to remove, and then tap Delete.

3Setting Up Siebel Mobile Disconnected Applications