1. Reports Guide
  2. How Siebel Runs Reports in Connected Clients

How Siebel Runs Reports in Connected Clients

The following figure illustrates the architecture that Siebel CRM uses to run a report if the user is using a Siebel client that is connected to the Siebel Server.

How Siebel Runs Reports in Connected Clients. This image is described in surrounding text.

As shown in this figure, the typical steps involved when Siebel CRM runs a report for connected clients are:

Note: As if Siebel CRM 17.0, the Siebel Repository File (SRF) no longer applies and is replaced by the Siebel Runtime Repository in Siebel database.

  1. A user runs a report from the Run Report pane.

  2. The Application Object Manager (AOM) sends an event to the Siebel Database.

  3. The Server Request Broker (SRBroker) and the Server Request Processor (SRProc) monitor the request, and then sends it to the XMLP Report server component through the XMLP Driver Service.

  4. The XMLP Driver Service calls the XMLP Data Service.

  5. The XMLP Data Service gets data from the Siebel Database through the EAI Siebel Adapter, and then returns control back to the XMLP Data Service.

  6. The XMLP Data Service sends control to the XMLP Driver Service.

  7. The XMLP Driver Service calls the XMLP Adapter Service.

  8. The XMLP Adapter Service calls the proxy PublicReportServiceService business service.

    The PublicReportServiceService Web service is the interface between the Siebel application and Oracle Publisher Server.

  9. The PublicReportService business service makes a Web service call to Oracle Publisher Server. For more information, see How Siebel Uses the PublicReportServiceService Web Service.

  10. Oracle Publisher Server runs the report, and then makes a Web service call to the PublicReportServiceService business service to return the report binary data.

    Oracle Publisher Server uses XSLT and XPath files to get XML data from the Siebel Database, and then merges this data with the report template that it gets from the Oracle Publisher repository. It then sends the report to the Siebel application. For more information, see How Siebel Uses Oracle Publisher Repository.

  11. The PublicReportServiceService business service returns control to the XMLP Adapter Service.

  12. The XMLP Adapter Service downloads the report, and then creates the file in the Siebel File System. Siebel CRM displays the file in the Siebel application.