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

How Siebel CRM Runs Reports in Disconnected Clients

Figure 6 illustrates the architecture that Siebel CRM uses to run a report if the user is using a disconnected client. The Siebel Mobile Web Client and Siebel Developer Web Client allow you to run reports if disconnected from the Siebel Server.

Figure 6. How Siebel CRM Runs Reports in Disconnected Clients

Explanation of Callouts

Siebel CRM does the following work when it runs a report in a disconnected client:

1. A user runs a report from the Run Report pane.
2. Siebel CRM uses the EAI Siebel Adapter to get data from the Siebel Database, and then stores this data as XML code in the following folder:

   SIEBEL_CLIENT_ROOT\CLASSES\XMLP\DATA

3. Siebel CRM calls the XMLP Report Java Business Service.
4. The XMLP Report Business Service calls the EAI Java Business Service, and then loads the JAR files in the Java Virtual Machine.

   The XMLP Report Business Service provides XML files to the Oracle BI Publisher XDO Engine to merge the report templates with XML data. One of the required inputs for the XDO Engine is an XML file. Siebel CRM uses the EAI Java Business Service to connect a Siebel application to the XDO Engine, and then uses the EAI Siebel Adapter to create the XML files. Oracle BI Publisher uses the EAI Java Business Service to send the XML file to the Oracle BI Publisher XDO Engine. This XML file contains the data that Siebel CRM uses to populate the report. Siebel CRM gets this data when it queries various data sources.

   Siebel CRM merges the XML data file with the report template, and then the Oracle BI Publisher displays the report in the client after storing the file in the Siebel File System.

   The XMLP Report Business Service and the Oracle BI Publisher libraries (XDO JAR files) are available as part of a Siebel mobile client installation. These libraries reside in the SIEBEL_CLIENT_ROOT\CLASSES folder. For information about installing a client, see Siebel Installation Guide for the operating system you are using.

   The EAI Java Business Service is the JVM (Java Virtual Machine) interface that resides between the XDO Engine and the Siebel application. For more information about the EAI Java Business Service and Java Virtual Machine, see Transports and Interfaces: Siebel Enterprise Application Integration.

5. The Oracle BI Publisher XDO Engine loads the XDO classes from the JAR files. Siebel CRM then sends the XML, XLIFF, and XSL templates to the XDO classes to run the report. Siebel CRM temporarily stores the report in the following folder, and then sends it to the Siebel File System:

   SIEBEL_CLIENT_ROOT\CLASSES\XMLP\REPORTS

   Oracle BI Publisher uses the XSLT and XPath files to get data from the XML data, and then incorporates this data into a report template file. The XSL data includes the XSLT, XPath, and XSL-FO standards that Siebel CRM uses to manipulate XML data. The XMLP Report server component uses the XDO Engine to convert the report template files into the XSL format. It then uses the BI Publisher-FO Processor to convert these files to the report that it publishes.

6. Siebel CRM sends control to the Siebel client, and then this client displays the report.