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 Handheld Component Groups for Siebel Mobile Disconnected Applications"

• "Setting Up the Disconnected Mobile Synchronization Component Group"

• "Assigning Responsibilities to Siebel Mobile Disconnected Application Users"

• "Setting Up Selective Retrieval for Siebel Mobile Disconnected Application Views"

• "Configuring Object Definitions for Siebel Mobile Disconnected Applications"

• "Configuring Siebel Mobile Disconnected Application Settings"

• "Configuring the Mobile Node for Siebel Mobile Disconnected Application Users"

• "Running Database Extract for Siebel Mobile Disconnected Application Users"

• "Configuring the Web Server MIME Type for Siebel Mobile Disconnected Applications"

• "Configuring a Hybrid Server Setup for Siebel Mobile"

• "Guidelines for Developing Data Filters for Siebel Mobile Disconnected Applications"

Enabling the Handheld 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 handheld components for Siebel Mobile must be enabled on the supported Siebel Server. You can enable the handheld 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 handheld component groups for Siebel Mobile disconnected applications 

1. Log in to the Siebel Web application, and then do the following:

   1. Navigate to the Administration - Server Configuration screen, then the Component Groups view.

   2. Query for the HandheldSync* component group.

      The following handheld 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 Step 1c.

      
      

      NOTE: The LifeSciences component group must only be enabled if using the Siebel Pharma application.

      
      

2. 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 the Disconnected Mobile Synchronization component group (MobileSync) for Siebel Mobile disconnected applications. The purpose of this task is to support synchronization in disconnected mode.

The Disconnected Mobile Synchronization component group (MobileSync), the Data Extraction component (MobileDbXtract), and batch synchronization are all configured for the Siebel Mobile application for Siebel Pharma by default so it is not necessary to configure them again for the application.

You must use MobileDbXtract as a template and configure it accordingly to create the Data Extraction component for other mobile applications (such as, the Siebel Mobile application for Siebel Sales or Siebel Service), as shown in the following procedure.

To set up the Disconnected Mobile Synchronization component group for 

1. 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.

2. Create the Data Extraction component for the mobile application as follows:

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

   2. Navigate to the Administration - Server Configuration screen, then the Enterprises view.

   3. Click the Component Definitions tab, and then query for MobileDbXtract in the Alias field.

   4. Using MobileDbXtract as a template, create a similar Data Extraction component for the mobile application you want to set up the Disconnected Mobile Synchronization component group (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 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.

   5. In the Component Parameters applet, configure the component parameters for the Data Extraction component (ServicemDbXtract) with the values shown in the following table:

      Name	Value
      Application Name	Siebel Service for Mobile Note that 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 CFGApplication Name for comp ServicemObjMgr_enu.
      Language Code	ENU
      Application Repository File	siebel_sia.srf

      
      

   6. Click the Activate button to activate the Data Extraction component (created in Step 2d) for the mobile application.

   7. Click the Synchronize button to synchronize the Data Extraction component (created in Step 2d) 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.

      
      

3. 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 top applet. For example: Siebel 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 (for example: 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.

4. Create a mobile client (for example: SPORTER) and perform the database extraction by doing one of the following:

   • From the command line, run the Database Extract component (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 Database Extract component (DbXtract). In the Job Parameters applet, add a Client Name parameter and its value, for example, as follows:

     ClientName=SPORTER-MOBILE
     

5. Start the mobile application (for example, servicem_enu) and log in with the appropriate user credentials.

6. 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 hhsync/<mobile-application> directory. For example:

     hhsync/phm is the directory created for the Siebel Mobile application for Siebel Pharma. hhsync/salesm is the directory created for the Siebel Mobile application for Siebel Service. hhsync/servicem is the directory created for the Siebel Mobile application for Siebel Service.

     The folder structure is determined by the Application Directory value specified in the Administration - Siebel Mobile screen, Application Administration, Settings view.

Assigning Responsibilities to Siebel Mobile Disconnected Application Users

This task is a step in "Roadmap for Setting Up 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, 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 disconnected application users  

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

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

3. Query for and select the appropriate responsibility or user role.

   For example, query for the following: PH Pharma Sales Rep - US Sales.

4. 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.

Table 3-3 lists the Siebel Mobile disconnected 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 3-3 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 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 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 Access to Views for Siebel Mobile Disconnected Applications"

• "Limiting Access to Views by Modifying Responsibilities"

• "Limiting Access to Views for All Responsibilities Globally"

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 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, which must be created for Siebel Mobile disconnected applications.

  
  

  Note: The Data Extraction Component (MobileDbXtract) is configured by default for the Siebel Mobile application for Siebel Pharma 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  

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

2. Verify that Purge Interval is set to 30.

3. 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 Application Settings for Siebel Mobile Disconnected Applications"

   • "Application Settings for Siebel Mobile Disconnected Applications"

   • "Configuring the Application Directory Setting"

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 Siebel Mobile disconnected application user  

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. 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 picklist that opens.

   • Mobile Application. Click the lookup icon, and then select the appropriate mobile application name from the picklist 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 picklist that opens.

4. Connect to the server manager and run Database Extract (dbxtract) 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 the Database Extract component (dbxtract) for every Siebel Mobile disconnected application user. Running dbxtract for each user takes approximately 3-10 minutes.

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 the Database Extract component 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 for Siebel Mobile disconnected application users from srvrmgr command line 

1. Start a task for the Database Extract component 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"
   

2. 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.

3. If the transaction processor component is not running, then run the following command:

   start task for comp txnproc
   

4. 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, and see "Setting Up Users for Siebel Mobile Disconnected Applications" and "Roadmap for Configuring Incremental Synchronization for Siebel Mobile Disconnected Applications".

Configuring the Web Server MIME Type for Siebel Mobile Disconnected Applications

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

The following procedures show you how to set MIME Type on different Web servers for Siebel Mobile disconnected applications. The procedure is similar across all Web servers. For more information, see the supporting Web server documentation.

For example, see "Configuring MIME Type on Microsoft Windows" to configure MIME Type on Microsoft Windows with IIS. To configure MIME type on operating systems other than Microsoft Windows, see the following:

• "Configuring MIME Type for Linux"

• "Configuring MIME Type for AIX and HPUX"

• "Configuring MIME Type for Solaris"

  
  

  Note: For a complete list of supported Web servers for each operating system, go to the Certifications tab on My Oracle Support and see Siebel Installation Guide for the operating system you are using.

  
  
  
  

  Note: For information about the Web Open Font Format (MIME Type: application/x-font-woff, file extension: .woff) used in web pages, refer to: http://en.wikipedia.org/wiki/Web_Open_Font_Format.

  
  

Configuring MIME Type on Microsoft Windows

Use the following procedure to configure MIME Type for Microsoft Windows with Internet Information Services (IIS).

To configure MIME Type on Microsoft Windows  

1. Start IIS.

   On Microsoft Windows for example, click Start, Control Panel, Administrative Tools, and then Internet Information Services.

2. Right click your local computer in the left pane, and then Properties.

3. Click the MIME Types button, and then New.

4. Configure MIME Type as follows:

   1. In the Extension field, enter the file name extension, as follows:

      .manifest
      

   2. In the MIME Type field, enter a description that exactly matches the file type defined on the computer, as follows:

      text/cache-manifest
      

5. Click OK.

Configuring MIME Type for Linux

Use the following procedure to configure MIME type for Oracle Enterprise Linux (Linux) with Oracle HTTP Server (for example, 11g Web Server).

To configure MIME type for Linux  

1. Login into the Linux computer.

2. Navigate to Web server installation directory where the mime.types file is located. For example:

   cd <WEB_SERVER_INST_DIR>/ config/OHS/ohs1
   

3. Run the following command:

   echo "text/cache-manifest manifest appcache" >> mime.types
   

4. Restart the Web server.

Configuring MIME Type for AIX and HPUX

Use the following procedure to configure MIME type for AIX and HPUX with HTTP Server and Apache Web Server. The types of HTTP Servers are as follows:

• IBM HTTP Server (on AIX)

• Oracle HTTP Server (on Linux)

To configure MIME type for AIX and HPUX  

1. Login into the AIX or HPUX computer.

2. Navigate to the Web server installation directory where the mime.types file is located. For example:

   cd <WEB_SERVER_ROOT>/conf
   

3. Run the following command:

   echo "text/cache-manifest manifest appcache" >> mime.types
   

4. Restart the Web server.

Configuring MIME Type for Solaris

Use the following procedure to configure MIME Type for Solaris with Oracle iPlanet Web Server.

To configure MIME Type for Solaris  

1. Login into the Solaris computer.

2. Navigate to Web server installation directory where the mime.types file is located. For example:

   cd <WEB_SERVER_ROOT>/https-localhost/config
   

3. Run the following command:

   echo "type=text/cache-manifest exts=appcache,manifest" >> mime.types
   

4. Restart the Web server.

Configuring a Hybrid Server Setup for Siebel Mobile

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

For Siebel Innovation Pack 2014 and later, 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  

1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Component Definition view.

2. Query for one of the following, as required:

   ePharma Mobile Object Manager (<Lang>)

   Sales Mobile Object Manager (<Lang>)

   Service Mobile Object Manager (<Lang>)

3. Click Component Parameters, and then click Advanced.

4. Search for Siebel File System, and then update the value to the respective windows path.