Monitoring Synchronization Sessions and Data Download

The Session Administration view contains detailed information about user synchronization sessions by gathering together all data related to each synchronization session that a user performs. Use this view to monitor and investigate user synchronization activities in Siebel Mobile disconnected applications. In the Session Administration view, the Sync Status list appears before the following two child lists: Sync Sessions and Extraction Info.

  • Sync Status. Enables you to monitor each user synchronization session, and includes information on synchronization status, date, type of synchronization, and so on.

  • Sync Sessions. Enables 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. Enables you to review a detailed description of all data extracted during the synchronization session, including business component information and the number of records extracted.

The following procedures show you how to monitor synchronization sessions and how to monitor data download.

To monitor synchronization sessions

  • Navigate to the Administration - Siebel Mobile screen, then the Session Administration view.

    The Sync Status list appears with the two child lists: Sync Sessions and Extraction Info.

To monitor data download

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

    The Sync Status list appears with the two child lists: Sync Sessions and Extraction Info.

  2. Scroll down to the Extraction Info list.

    There is one extraction record for each unique extraction context. Review the data-extraction information. The 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 the 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.

Information in the Extraction Record

The extraction record lists the following information:

  • The filters used to control the extraction

  • The context of the extraction

  • How many records exist in that context for those filters

  • How long it took to extract that set of records.

By analyzing these records and looking at all extraction changes resulting from the filter changes, or changes to the search specifications or both (defined in Siebel Tools), you can answer the following questions:

  • Why did I download a particular record?

  • Why is an expected server record not downloaded?

  • 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?

Note: Because storage space on a mobile device is typically limited and the available networking bandwidth for synchronization might not always be optimal, you must configure the filters carefully, and keep the size of your local database small. It is recommended that users have a local database size of about 3 megabytes (MB), which can be expanded up to 50 MB.