Siebel Remote and Replication Manager Administration Guide > Siebel Remote Reports >

Status Reports

There are ten standardized reports available, with the following types of information:

There are nine on-line reports available from the related views within the Siebel Remote Administration screen. To access these from the application-level menu, choose View > Reports.

The Outbox Analysis report is not an on-line report because it is generated by a workflow. Access for this report is covered later in this chapter.

Table 22 lists the nine on-line reports accessed from the appropriate view within the Remote Administration screen.

Table 22.  Standardized Status Reports - Remote and Replication Manager
Name of Report
Description
View
Mobile User Status Report
This report is available on all server nodes that contain mobile users. Below is a list of information available in the report:
  • Date and time of last extraction
  • DB Extract Size (MB)
  • DB Extract Rows
  • Local DB Size (MB)
  • Date and time of last initialization
  • Date and time of last synchronization
    • Number of transactions
    • Size of transactions in MB
    • Duration of session
    • Duration of last merge on client
  • DX files last routed from the Server
  • DX files last routed to the Server
  • DX files received and merged into the Server by this user
  • DX files received and merged on to the Local database of this user
This report also indicates whether the user is active. Otherwise, it displays last accessed date, and the name of the Routing Model associated with the mobile user.
Client Status
Transaction Processor Status Report
This report shows the status of all active and inactive transaction processor entries in the current Enterprise server. It also includes details such as:
  • Date and time of last run
  • Duration of last run
  • Number of transactions and operations copied
  • Last DX file created and removed from the docking\txnproc folder on the corresponding application server
Processor Status
Transaction Backlog Status Report
This report provides information concerning pending transactions in the queue from active mobile users and regional nodes with respect to the most recent transaction created on the HQ at the time the report was run. Fields in this report include the Mobile Web Client name and the number of pending transactions.
Transaction Log
Synchronization Frequency Report
This report displays the frequency of synchronization by every mobile user for a given period of time. Each line of the report includes Mobile User ID, App Server Name, and the number of times the user has synchronized in a given period.
Synchronization Sessions
Synchronization Session Report
This report provides information about synchronization sessions of every mobile user for a given period of time. The report provides mobile user information and details of their synchronization sessions.
Synchronization Sessions
Regional Node Status Report
This report is available on all server nodes that have subordinate regional nodes. This report should contains the following information about the regional node:
  • Date and time of last extraction
  • Date and time of last initialization
  • Date and time of last synchronization
  • DX files last routed to the node from the parent server
  • DX files last routed by the regional node to the parent server
  • DX files received and merged into the parent server
  • DX files received and merged into the regional database
The report should also indicate whether the regional node is currently active or end dated and its routing group.
Client Status
Active Mobile Users Usage Graph
This report is available on all server nodes that have mobile users. The report takes start date as a parameter from the user and it generates the following details for each day between the start date and the current date, in the form of a graph:
  • X-axis includes all the days in the specified range of dates
  • Bar graph displays the number of cumulative inits per day
  • Line graph displays the number of unique syncs per day. Number of unique syncs means number of mobile users that synchronized per day.
Synchronization Sessions
Active Mobile Users Usage Table
This report is available on all server nodes that have mobile users. The report takes start date as a parameter from the user and it generates the following details for each day between the start date and current date in the form of a table:
  • Date column displaying all the days in the specified range of dates
  • Daily inits column displaying the number of initializations per day
  • Cumulative initializations column displaying the number of cumulative inits per day
  • Daily unique syncs column displaying the number of mobile users that synchronized per day
Synchronization Sessions
Transaction Router Backlog Report
This report provides information about:
  • The number of transactions that could potentially be routed to the active mobile users or regional nodes. This is calculated with respect to the most recent transaction created on the HQ at the time the report was run.
  • The latency of the active mobile users and regional nodes with respect to the time the report was run. The report displays the total, average, maximum, and minimum backlog and latency.
Latency is the time difference between the last transaction routed to the mobile user or regional node and the time the report was run.
Transaction Log

The procedure that follows describes how to access these reports.

To access on-line Remote reports

  1. Navigate to the appropriate view within the Remote Administration Screen that has status reports available.

    For example, you may want reports from the Synchronization Sessions view.

  2. From the application-level menu, navigate to View > Reports.
  3. From the selection dialog box, choose the report and language options.
  4. Click OK and view the report.

These reports are accessible only to the Administrator except for the Client Status report. The Client Status report is available to Mobile Web Clients as long as their responsibilities include this view. For additional information about responsibilities, see Applications Administration Guide.


 Siebel Remote and Replication Manager Administration Guide 
 Published: 19 November 2003