Configuring EPM 11.2.2 components
Now that I have covered Foundation configuration in this blog, let's proceed with the subsequent components.






















































Before that, I would like to show you the way in which you need to start OHS (12c) in this version.
Oracle HTTP Server is managed and monitored with Node Manager. To start OHS, follow the below process:
- Start the Node Manager service from the Windows Service panel: Oracle Weblogic ohs NodeManager (D_Oracle_Middleware_ohs_wlserver)
- Start Oracle HTTP Server from the command line from EPM_ORACLE_INSTANCE\httpConfig\ohs\bin. For my installation this is the path - D:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\bin. Enter - 'startComponent ohs_component'. When prompted, enter the WebLogic Admin Server password.
Lets continue with configuring the rest of the components.
Calculation Manager
Launch EPM Configurator:
Choose Calculation Manager components in the below screen:
Provide the schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
Summary screen:
And it's configured.
At this point of time if you want to validate Calculation Manager in Workspace, you will need to configure the Web Server once more.
Planning
Choose the Planning components:
Provide the schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
Specify the RMI port.
What is RMI: Oracle Hyperion Planning uses the Hyperion RMI Registry. RMI (JAVA RMI protocol, running on default port 11333) is being used by ODI (11.1.2.3 onwards) to communicate with Planning. Also RMI is being used in communication between Planning and Business Rules.
Summary Screen:
And it's configured.
Financial Reporting
Choose the Financial Reporting components:
Provide the schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
Configure RMI ports:
Summary screen:
And it's configured.
At this point of time, you will see the below services created:
Rest of the components, I will be configuring in a different server. In this server as well, I have run the RCU but with a different prefix.
Essbase
Since it's a different application server, we need to point the configurator to our previously configured Shared Services database:
Choose the Essbase components:
I didn't select Esbase Studio.
Provide the EAS schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
Configure Essbase server:
Essbase Cluster Name: Specify a cluster name to create a cluster to provide active-passive Essbase failover support with write-back capabilities. You can include only two Essbase instances in a cluster. When you configure the first instance of Essbase on the first machine, you define the cluster. When you configure the second instance of Essbase on the second machine, select Assign to Existing Cluster, select the cluster, and then click OK to add this Essbase Server to the cluster you created on the first machine. The Essbase cluster name must be unique in a deployment environment. It cannot contain special characters or spaces.
Agent Port Number: Accept the default port number on which the Essbase listens for client requests. If you change the default value, enter a port number that is not used by other programs. Select Active to enable the agent to listen on this port.
Start Port: Accept the default number or enter the first port number on which the Essbase Server listens for client requests. The port value is stored in essbase.cfg (in ARBORPATH/bin).
End Port: Enter the greatest port number that Essbase Server can use to connect.Essbase uses at least two ports for each application. For a large number of applications, you need a larger port range.
Full path to application location (ARBORPATH): The location for applications.
Binding Host Name: Specify a Binding Host Name to have Essbase bind only to the IP address for the specified Binding Host Name. Otherwise, at startup, Essbase binds on all available IP addresses.
Summary Screen:
And it's configured.
FDMEE
Choose the FDMEE components:
Provide the schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
Summary screen:
And it's configured.
Financial Management
Install .NET Framework in the server before configuring HFM. Download here.
Choose the Financial Management components:
Provide the schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
Financial Management — Configure Server:
Port: Review or change the default port number on which Oracle Hyperion Financial Management listens for client requests. If you change the default value, enter a port number that is not used by other programs. Select Active to enable the server to listen on this port.
SSL Port: Review or change the SSL port on which Financial Management listens for client requests. If you change the default value, enter a port number that is not used by other programs. Select Active to enable the server to listen on this port.
Max App Server Delay: Accept the default value or enter the time interval in seconds between when a change is made to an application and when the change is visible to users accessing the application through another application server.
Max Data Sync Delay: Accept the default value or enter the time interval in seconds between when a change is made to data and when the change is visible to users accessing the data through another application server.
Database Connection Pool Size: Specify the number of maximum pooled relational database connections for the application. Financial Management requires approximately 25 relational database connections per application.
Start Port: Accept the default number or enter the first port number in the range for the datasource connection.
End Port: Accept the default number or enter the last port number in the range for the datasource connection.
Financial Management — Configure Cluster:
Add a cluster:
When you add a cluster, specify the cluster name, and select Use Sticky Server if you want to direct all requests for a specific session to the same server.
Summary screen:
And it's configured.
Financial Close Management
Choose the Financial Close Management components:
Provide the schema/database host details in the below screen:
Deploy to an existing domain:
I will not be deploying the Java web applications to a single managed server:
URL: Enter the URL of the system hosting the Document Management system. See the Certification Matrix for information about supported document management systems.
Summary screen:
And it's configured.
That's all the components that I've configured.
Essbase patching to latest version
EPM version 11.2 utilizes Essbase version 11.1.2.4.033, Oracle Hyperion Provider Services Release 11.1.2.4.033, as well as Oracle Hyperion Essbase Administration Services 11.1.2.4.031. This allows users to expect the same features and functionalities that are used in Essbase 11.1.2.4.033 when using Essbase EPM version 11.2.
So, I decided to patch Essbase to the latest version.
Below are the patching commands for your reference:
Essbase Server 11.1.2.4.040
opatch.bat apply D:\Oracle\Middleware\EPMSystem11R1\OPatch\31206864 -oh D:\Oracle\Middleware\EPMSystem11R1 -jre D:\Oracle\Middleware\jdk1.8.0_181
Essbase RTC 11.1.2.4.040
opatch.bat apply D:\Oracle\Middleware\EPMSystem11R1\OPatch\31206851 -oh D:\Oracle\Middleware\EPMSystem11R1 -jre D:\Oracle\Middleware\jdk1.8.0_181
APS 11.1.2.4.040
opatch.bat apply D:\Oracle\Middleware\EPMSystem11R1\OPatch\31206874 -oh D:\Oracle\Middleware\EPMSystem11R1 -jre D:\Oracle\Middleware\jdk1.8.0_181
EAS 11.1.2.4.037
opatch.bat apply D:\Oracle\Middleware\EPMSystem11R1\OPatch\30717472 -oh D:\Oracle\Middleware\EPMSystem11R1 -jre D:\Oracle\Middleware\jdk1.8.0_181
That's all for now!
Comments
Post a Comment