Predefined Administrative Reports
The following table describes the predefined administrative status reports. The View column describes the view you can use to start the report. For more information, see About Siebel Replication Manager.
Name of Report | View | Description |
---|---|---|
Active Mobile Users Usage Graph |
Synchronization Sessions |
Displays information for server nodes that contain users. This report takes the start date as a parameter from the user and then creates the following details for each day that occurs between the start date and the current date, in the form of a graph:
|
Active Mobile Users Usage Table |
Synchronization Sessions |
Displays information for server nodes that contain users. This report takes the start date as a parameter from the user and then creates the following details for each day that occurs between the start date and the current date in the form of a table:
|
Mobile User Summary Report |
Client Status |
This report displays the following information for server nodes that contain users:
This report also indicates if the user is active. If the user is not active, then displays the last accessed date and the name of the Routing Model that is associated with the user. |
Regional Node Status Report |
Client Status |
Displays information for server nodes that contain subordinate regional nodes, including the following information about the regional node:
The report also indicates if the regional node is currently active or end dated and the routing group of the regional node. |
Synchronization Frequency Report |
Synchronization Sessions |
Displays how frequently Siebel Remote synchronizes each user for a period of time. Each line of the report includes the following information:
|
Synchronization Session Report |
Synchronization Sessions |
Displays information about synchronizations for every user for a period of time. The report provides user information and details of these synchronizations. |
Transaction Backlog Status Report |
Transaction Log |
Displays information about transactions that are pending in the queue from active users and regional nodes. It starts with the most recent transaction that Siebel Remote created on the headquarters node at the time you run the report. Fields in this report include the name of the remote client and the number of pending transactions. For more information about headquarters nodes, see Overview of Siebel Replication Manager. |
Transaction Processor Status Report |
Processor Status |
Displays the status of active and inactive Transaction Processor entries that exist in the current Siebel Server. This report includes the following information:
|
Transaction Router Backlog Report |
Transaction Log |
Displays the following information:
Latency is the time difference between the time when Siebel Remote routed the last transaction to the user or regional node and the time when you run the report. |