EPM Architecture: Foundation

If applicable, the component will have its standard port next to its name in brackets.

EPM Architecture Foundation

EPM Foundation is Java based and consists of two web applications, Shared Services and Workspace. Both applications are accessed by browser through Oracle HTTP Server (OHS) or Internet Information Services (IIS). Communication to the backend database is done by JDBC. The file system to store Lifecycle Management (LCM) artifacts can be either local or remote (e.g. NFS, network share). For authentication purposes, the EPM Product Suite can connect to external directories or databases.

Interaction with other EPM Suite components like product specific Lifecycle Management connectors or Reporting and Analysis Web happens through HTTP protocol.

There are two kinds of clients available for the Enterprise Performance Management Architect (EPMA). The most commonly used is the browser based web interface. In addition to the web interface a Batch Client is available for atomization purposes. Both clients use the HTTP(S) protocol to communicate with the EPMA WebServer through Oracle HTTP Server.

The Java based EPMA WebServer deployed on WebLogic is the central point of contact that interacts with other components. Interaction to the EPMA DataSync Server, Planning, Profitability and Cost Management as well as to the EPMA Web Services running on IIS is done using the HTTP protocol. JDBC is used to communicate to the repository databases.

Various protocols are used by EPMA WebServer to communicate to the application layer. Communication to Financial Management is done through the Financial Management DME Listener based on TCP/IP protocol. Essbase Studio is accessed based on TCP/IP protocol as well. The Essbase JAPI is used to communicate to the Essbase server.

As described above, EPMA WebServer talks to EPMA Web Services using HTTP protocol. Communication from EPMA Web Services to the EPMA Dimension Server is based on NET.tcp. Keep in mind that both services, EPMA Web Services and EPMA Dimension Server need to be on the same server.

EPMA Dimension Server uses HTTP protocol to talk to the Data Relationship Management (DRM) Web Services. Communication to the database layer is done using native database protocols, therefore a database client needs to be installed on the EPMA Dimension Server.

Calculation Manager is accessed by a browser based client through the Oracle HTTP Server. The Java based application is deployed on WebLogic. Interaction between Calculation Manager and EPMA, Planning as well as Financial Management is done using the HTTP protocol. Essbase is accessed using the Essbase JAPI. All communication to repository databases is done using JDBC.



Excellent diagram and info on EPM.


Posted by Azmat Bhatti on November 13, 2012 at 01:31 PM PST #

It would be great if all the architecture diagrams were gathered together in one document.

Posted by guest on December 17, 2012 at 07:06 AM PST #

The diagrams shown above work well if you are installing a logical tier model. If you want to split between a Windows and LINUX environment and a physical tier model a more comprehensive diagrams would be better.

Haroon Yaqoob
Comprobase, Inc.

Posted by Haroon Yaqoob on January 12, 2013 at 02:08 PM PST #

First time I saw this and it is fantastic. Can you also advise if there is any similar things done with OBIEE with foundation and Essbase

Posted by Amir Ali on April 03, 2014 at 12:09 PM PDT #

First time I saw this and it is fantastic. Can you also advise if there is any similar things done with OBIEE with EPMA, foundation and Essbase

Posted by guest on April 03, 2014 at 12:13 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed