EPM 220.127.116.11 Architecture: Reporting and Analysis
By Marc Schumacher on Nov 16, 2012
Reporting and Analysis is the basis for all Oracle EPM reporting components. Through the Java based Reporting and Analysis web application deployed on WebLogic, it enables users to browse through reports for all kind of Oracle EPM reporting components.
Typical users access the web application by browser through Oracle HTTP Server (OHS). Reporting and Analysis Web application talks to the Reporting and Analysis Agent using CORBA protocol on various ports. All communication to the repository databases (EPM System Registry and Reporting and Analysis database) from web and application layer is done using JDBC. As an additional data store, the Reporting and Analysis Agent uses the file system to lay down individual reports. While the reporting artifacts are stored on the file system, the folder structure and report based security information is stored in the relational database. The file system can be either local or remote (e.g. network share, network file system). If an external user directory is used, Reporting and Analysis services also communicate to this directory.
WebAnalysis is the ad hoc reporting utility that is part of Oracle EPM System. Users access WebAnalysis either by browser using the web based client or by WebAnalysis Studio, the Java based client.
The Java based web application is deployed on WebLogic. As WebAnalysis is part of Reporting and Analysis, communication to the Reporting and Analysis Agent is done using CORBA. To access the Reporting and Analysis repository as well as the EPM System Registry, WebAnalysis uses JDBC connections.
Typically WebAnalysis is used on top of Essbase or Financial Management, but it also has the ability to connect to relational databases. To access Essbase, WebAnalysis uses the Essbase JAPI. Financial Management is accessed using the ADM driver. WebAnalysis always connects to the Financial Management application server to retrieve data; it does not connect to the Financial Management database directly.
Financial Management will be covered in a later post in more detail. To access its repository, the Financial Management application server uses native database clients through OLE DB connections.
Users of Financial Reporting access the application using a browser through Oracle HTTP Server. Report designers need to use the Financial Reporting Studio, a Windows application, which talks to the Financial Reporting Server through HTTP and RMI protocol. RMI ports are dynamic by default, to make Financial Reporting Studio work through firewalls, these ports can be configured using FRconfig.cmd on Windows or FRconfig.sh on Unix.
Financial Reporting is deployed on WebLogic and includes all components (e.g. Report Server, Print Server, Scheduler, Web application) that were distributed in prior releases to several processes. Communication to the Reporting and Analysis Agent is done via CORBA protocol. EPM System Registry and the Reporting and Analysis Repository are accessed using JDBC.
The data sources for Financial Reporting in context of Oracle EPM are Essbase and Financial Management. To access Essbase, the Java API is used. Consolidation data is pulled from Financial Management application server using the ADM driver on top of Microsoft DCOM protocol. In case Planning Supporting Details are needed within a report, Planning can be a data source as well.
Interactive Reporting is the relational reporting tool as part of Oracle EPM System. There are two browser based clients, the HTML and the Web Client. While the HTML client can be used with a compatible browser right away, the Interactive Reporting Web Client is a Plug-in that needs to be installed first. As a third client, Interactive Reporting Studio, a Windows client, is available as well. The Interactive Reporting Studio is mainly used by report and dashboard designers.
Users accessing Interactive Reporting using the HTML or Web Client, go through Oracle HTTP Server and talk to Reporting and Analysis Web deployed on WebLogic. The Reporting and Analysis Web application communicates with the Reporting and Analysis Agent as well as the Interactive Reporting Services on various ports using CORBA protocol. The Interactive Reporting Services consist of Data Access Service and BI Service, which are used to query data and render reports on top of relational and multidimensional data sources. Data is typically accessed using native database clients or via ODBC connections.