7/28/2019 Load Balanced Setup Config

1/5

1Architecture

In This Chapter

What is Oracles recommended Production Deployment Model for EPM System Release 11.1.2.x?

... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

What is the typical architecture for EPM System components for Release 11.1.2.1? .. .. .. .. .. .. .. . 9

Where can I get a list of infrastructure new features and enhancements for EPM System Release

11.1.2.1?.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What is an example of internal HTTP-based, Server-to-Server communication in EPM System

11.1.2.x, and what is the exact communication path for it? ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 9

What is Oracles recommended Production Deployment

Model for EPM System Release 11.1.2.x?EPM System follows Oracles standard enterprise deployment model for a highly available

distributed setup as described in the following diagram.

What is Oracles recommended Production Deployment Model for EPM System Release 11.1.2.x? 7

7/28/2019 Load Balanced Setup Config

2/5

There are two VIPs used in this model:

epm.mycompany.com is used for all client access to server resources.

epminternal.mycompany.com is used for all server-to-server communications for EPM

System services. epminternal.mycompany.com is referred to in the EPM System

configuration process as the Logical Web App.

The internal communications between servers and external access to the system are directed to

two VIPs for the following two reasons:

Having two URLs provides flexibility in configuring security. In the recommended model,

all external access to the system is based on HTTPS (which is then converted to HTTP by

the load balancer/SSL offloader), and all internal communication is based on HTTP because

inside communications may not be configured for SSL.

8 Architecture

7/28/2019 Load Balanced Setup Config

3/5

Improved security. The firewall to the Web tier should be configured to not allow access to

internal communications between the services and therefore needs a separate VIP.

What is the typical architecture for EPM System

components for Release 11.1.2.1?Diagrams showing the component architecture for each EPM System component are now

included in the Installation Start Here (EPM System Architecture chapter) and are also

provided in Powerpoint format on the EPM/BI Whitepaper Library(Component Architecture

for 11.1.2 EPM System Components).

Where can I get a list of infrastructure new features

and enhancements for EPM System Release 11.1.2.1?

See the EPM System Installation and Configuration Readme and the Shared Services Readme,in the New Features sections.

What is an example of internal HTTP-based, Server-to-

Server communication in EPM System 11.1.2.x, and

what is the exact communication path for it?There are a number of internal HTTP-based, server-to-server communications in EPM System

for Release 11.1.2.x. These communications are routed through the logical Web application

address (host and port) configured by users. In a high availability environment, the logical Webapplication should be configured as a pool on the load balancer that routes the calls to the Web

servers. For example, in the diagram below, the server and port for this internal pool is named

epminternal.mycompany.com.

What is the typical architecture for EPM System components for Release 11.1.2.1? 9

7/28/2019 Load Balanced Setup Config

4/5

An example of an internal server-to-server HTTP call is when a user lists artifacts in Shared

Services Console. The actual list of artifacts is produced by the Planning Web application via an

HTTP-based call, but it is displayed by Shared Services Console.

The communication path for expanding the artifact list in a Planning application in Shared

Services Console is as follows:

1. A user starts the call from a browser.

2. The browser makes an HTTPS call to the load balancer to load the page.

3. The load balancer converts the call to HTTP and passes it to an OHS server.

4. OHS uses the WebLogic Plug-in and routes the call to a WebLogic Server that is running a

Shared Services Web application.

5. The Shared Services Web application looks up the Planning LWA address in the Shared

Services Registry and makes an HTTP call to retrieve the list of artifacts. This address should

10 Architecture

7/28/2019 Load Balanced Setup Config

5/5

be a pool on the load balancer as depicted above. Note that even though deployment is in

SSL-offloading mode, the server-to-server communications are not in SSL, and therefore

the load balancer pool for internal communication is configured to be in non-SSL mode.

6. The load balancer routes the call via HTTP to one of the OHS servers in the deployment.

7. OHS routes the call via the WebLogic Plug-in to one of the Planning Web applications.

8. The Planning Web application retrieves the list of Planning artifacts from the database and

returns the call back to Shared Services. All of the calls are retuned back to the browser, and

the user sees the list of artifacts in the Planning application.

Important points:

LWA is the server and port to which all HTTP-based communications are routed.

The communication is in non-SSL mode even if the system is configured for SSL off loading.

LWA should be configured as a pool on the load balancer that routes the call to all OHS

servers.

What is an example of internal HTTP-based, Server-to-Server communication in EPM System 11.1.2.x, and what is the exact communication path for

it? 11