Siebel Reports Guide > Siebel Reports Architecture > About the Siebel Reports Architecture >

How Siebel CRM Runs Reports in Connected Clients

Figure 5 illustrates the architecture that Siebel CRM uses to run a report if the user is using a Siebel client that is connected to a Siebel Server.

Figure 5. How Siebel CRM Runs Reports in Connected Clients

Explanation of Callouts

Siebel CRM does the following work when it runs a report in connected clients:

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 the Oracle BI Publisher Server.

9. The PublicReportService business service makes a Web service call to the Oracle BI Publisher Server. For more information, see How Siebel CRM Uses the PublicReportServiceService Web Service.
10. The Oracle BI Publisher Server runs the report, and then makes a Web service call to the PublicReportServiceService business service to return the report binary data.

    The Oracle BI 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 BI Publisher repository. It then sends the report to the Siebel application. For more information, see How Siebel CRM Uses the Oracle BI 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.

How Siebel CRM Uses the PublicReportServiceService Web Service

The PublicReportServiceService Web service is a Web service that Oracle BI Publisher uses to upload and send a report to the Siebel application. It does the following work:

• Validates privileges
• Gets information about reports, the Oracle BI Publisher repository, and the Oracle BI Publisher ServerSharedFolder/SIEBELCRMREPORTS
• Runs reports
• Creates and manages reports

How Siebel CRM Uses the Oracle BI Publisher Repository

The Oracle BI Publisher repository is a repository that contains predefined reports and new reports that you create. It resides on the Oracle BI Publisher Server. You install it when you install the Oracle BI Publisher Server. The following folder in the Oracle BI Publisher repository stores all reports:

SharedFolder/SIEBELCRMREPORTS

Siebel CRM stores the report template files that it requires to run a report in a separate folder in the SIEBELCRMREPORTS folder. For more information, see Directory Structure That Siebel Reports Uses.