Siebel Service Handheld Guide > Siebel Handheld Application Administration > About Monitoring Synchronization Sessions for Siebel Handheld Applications >

Monitoring Synchronization Sessions for Siebel Handheld Applications


The Session Administration view allows you to gather all data related to each synchronization session a user performs. In the Session Administration view, the Sync Status list appears above two child lists—Sync Sessions and Extraction Info.

  • Sync Status—Allows you to monitor each user synchronization session, and includes information on synchronization status, date, type of synchronization, and so on.
  • Sync Sessions—Allows you to gather further information on the status of each synchronization session, including information on any conflicts that occurred during the synchronization, the size of the data extracted, and so on.
  • Extraction Info—Allows you to review a detailed description of all data extracted during the synchronization session, including business component information and the number of records extracted.

To monitor synchronization sessions

  • Navigate to the Administration - Mobile screen > Session Administration view.

    The Sync Status list appears with the two child lists, Sync Sessions and Extraction Info, below it.

To monitor data download

  1. Navigate to the Administration - Mobile screen > Session Administration view.

    The Sync Status list appears with the two child lists, Sync Sessions and Extraction Info, below it.

  2. Scroll down to the Extraction Info list.

    There is one extraction record for each unique extraction context. Review the data extraction information recorded. Information recorded for review is described in the following table.

    Field
    Comments

    Business Component

    The business component on which the synchronization is based.

    Context

    The context of the extraction.

    # Records Extracted

    The number of records that exist in the context of applied filters.

    Extract Time

    The length of time it took to extract the set of records.

    Business Object Filter

    The business object filter (if any) applied to the extraction.

    Business Component Filter

    The business component filter (if any) applied to the extraction.

    You should use this information to help answer the following questions:

    • Why did I download a particular record to the device?
    • Why is an expected server record not downloaded to the device?
    • Why is the total number of records showing up in some views so big?
    • Why is the total number of records showing up in some views so small?
    • Why does the extraction take so long?

      The extraction record lists the filters used to control the extraction, the context of the extraction, how many records exist in that context for those filters, and how long it took to extract that set of records. By analyzing these records, and looking at all extraction changes resulting from filter changes, and, or changes to search specifications (defined in Siebel Tools), you can answer all of the above questions.

      NOTE:  Because storage space on a handheld device is typically limited, and available networking bandwidth for synchronization might not always be optimal, it is critical to carefully configure the filters and keep the size of your local database small. It is recommended that users should have a local database size of around three megabytes (MB), and this should never exceed 10 MB.

Siebel Service Handheld Guide Copyright © 2007, Oracle. All rights reserved.