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

Overview of How Siebel CRM Runs Reports in Clients

Figure 5 illustrates an overview of how Siebel CRM runs reports in connected and disconnected clients.

Figure 5. Overview of How Siebel CRM Runs Reports in Connected and Disconnected Clients

Explanation of Callouts

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

1. The user requests to run a report in the Siebel client, and then Siebel CRM sends this request to one of the following items:
   • Oracle BI Publisher Server if the user is using a connected client
   • Oracle BI Publisher XDO Engine if the user is using a disconnected client
2. The RTF Processor converts the report template files to the XSL format so that Siebel CRM can use it as input to the BI Publisher-FO Processor.
3. The BI Publisher-FO Processor merges the XSL and the XML data files, and then creates one or more of the following output formats, depending on the output type that the user chooses:
   • Converts XML and XSL formats to HTML.
   • Converts XML, XSL-FO, and XLIFF formats to PDF, HTML, RTF, EXCEL, PPT, and MHTML.

     For more information about the file types that the user can choose, see Output File Types That Siebel Reports Supports.

Oracle renamed XML Publisher and XMLP to Oracle BI Publisher. Some items still use XML Publisher or XMLP.