| Siebel CRM Siebel Mobile Guide: Disconnected Siebel Innovation Pack 2015, Rev. D E52427-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM Siebel Mobile Guide: Disconnected Siebel Innovation Pack 2015, Rev. D E52427-01 |
|
Previous |
Next |
View PDF |
This task is a step in "Roadmap for Setting Up Siebel Mobile Disconnected Applications".
You can monitor synchronization sessions and synchronization conflicts for Siebel Mobile disconnected applications from a number of views within the Administration - Siebel Mobile screen. Every time a user synchronizes with the Siebel Server, a record is made. The following procedures relate to monitoring synchronization:
"Obtaining Business Component Information from Synchronization Conflicts"
"Responding to Synchronization Errors in Siebel Mobile Disconnected Applications"
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 above 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 procedure shows how to monitor synchronization sessions.
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.
The following procedure shows how to monitor data download.
To monitor data download
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.
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 |
The Conflict Administration view enables you to access selected transaction errors, and to obtain information about synchronization errors that occur during individual synchronization sessions. The following tabs are available from the Conflict Administration view:
Error Details. Use this tab to obtain detailed information about specific data conflicts. You can also take a particular action on any given conflict.
For more information, see the following procedure.
Business Components. Use this tab to see the business component information associated with a particular data conflict.
For more information, see "Obtaining Business Component Information from Synchronization Conflicts".
Audit Trail. Use this tab to obtain information about the action that is taken on a particular data conflict. The Audit Trail must first be enabled for the conflict data.
For more information, see "Obtaining an Audit Trail for Synchronization Sessions".
To obtain error details from the synchronization sessions
Navigate to the Administration - Siebel Mobile screen, then the Conflict Administration view.
In the Transactions list, select the appropriate record, and then click the Error Details tab.
In the Error Details list, select or query for the record that you want.
The Transactions view on the Conflict Administration screen enables you to obtain business component information related to synchronization errors that occur during individual synchronization sessions.
To obtain business component error details
Navigate to the Administration - Siebel Mobile screen, then the Conflict Administration view.
The Transactions list appears.
In the Transactions list, select the appropriate record, and then click the Business Components tab.
The Transactions view on the Conflict Administration screen enables you to obtain audit-trail information for an action that was taken for a particular transaction. You must enable Audit Trail separately. For information about enabling Audit Trail, see Siebel Applications Administration Guide.
To obtain audit trail information for synchronization errors
Navigate to the Administration - Siebel Mobile screen, then the Conflict Administration view.
The Transactions list appears.
In the Transactions list, select the appropriate record, and then click the Audit Trail tab.
When reviewing a synchronization error, you can respond to it in one of the following ways: you can ignore it, export it, or reapply it.
To respond to synchronization transaction errors
Navigate to the Administration - Siebel Mobile screen, then the Conflict Administration view.
The Transactions list appears. The transaction buttons are described in the following table.
| Action | Result |
|---|---|
| Reapply | Reapplies the selected transaction with the values listed in the view or Field Value view. These values override the results provided by the Siebel Server. |
| Export | Exports the content of the transaction in the same format used by the synchronization engine. For help with interpreting the content, create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. |
| Ignore | Accepts the current status and does not act upon the error. The record becomes read-only. There is no impact, except that the error will no longer appear in queries for unresolved conflicts. |
Click Reapply, Export, or Ignore, depending on your needs.
|
Note: This step works only when the Siebel Application Object Manager is running on a Windows-based server. |
