Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
109 views4 pages

How To Manually Configure An Existing EPM 11.1.2.4 To Use Java 1.7

This document provides instructions for manually configuring an existing Oracle Enterprise Performance Management (EPM) 11.1.2.4 environment to use Java 1.7. The process involves downloading and installing Java 1.7, updating configuration files and scripts to reference the new Java home, modifying the Windows registry, and testing the new configuration. Only EPM 11.1.2.4 has been certified to work with Java 1.7.

Uploaded by

Kumar Shawn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
109 views4 pages

How To Manually Configure An Existing EPM 11.1.2.4 To Use Java 1.7

This document provides instructions for manually configuring an existing Oracle Enterprise Performance Management (EPM) 11.1.2.4 environment to use Java 1.7. The process involves downloading and installing Java 1.7, updating configuration files and scripts to reference the new Java home, modifying the Windows registry, and testing the new configuration. Only EPM 11.1.2.4 has been certified to work with Java 1.7.

Uploaded by

Kumar Shawn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

How To Manually Configure an Existing EPM 11.1.2.4 to use Java 1.

This document is written for both Unix and Windows and assumes that you already have a working EPM
11.1.2.4 environment. Reconfiguring EPM to use Java7 is a manual process. Java7 will replace both
jdk1.6 and jrocket1.6.

Note that 11.1.2.4 is the only EPM version currently certified for Java7.

The paths shown are for Windows. Just change them accordingly for if you are on Unix.
1. Download Java7 (Patch 26916855) for your OS and install to F:\Oracle\Middleware

2. Change Directory to F:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0 and


backup the setJavaRuntime.(bat/sh) script. Then change all occurrences of jdk160_35 to
jdk1.7.0_161
3. Change Directory to F:\Oracle\Middleware\user_projects\domains\EPMSystem\bin and backup
the WebLogic setDomainEnv.(cmd/sh) script. Then change all occurrences of jrockit_160_37 to
jdk1.7.0_161
4. Windows Only - Backup the Hyperion Solutions Branch of the Windows Registry

5. Windows Only - Update the Windows Registry via the regedit.


For ALL EPM Services Change the JavaDLL to
F:\Oracle\Middleware\jdk1.7.0_161\jre\bin\server\jvm.dll

6. Unix Only – Change directory to


/Oracle/Middleware/user_projects/epmsystem1/bin/deploymentScripts and backup all scripts.
Modify each of the setCustomParamsProduct.sh and remove the
“-XX:-FlightRecorder” option in each one. This option is not valid in Java7.
7. For Essbase - Change directory to
F:\Oracle\Middleware\user_projects\epmsystem1\config\OPMN\opmn and backup the
opmn.xml file. Open the opmn.xml file change the one occurrence of jdk160_35 to jdk1.7.0_161
8. For Essbase – (This step may not be required in your environment). By default Essbase gets the
location of Java from OPMN, but if you have modified your essbase.cfg and hardcoded the Java
location, then you must make a change to the essbase.cfg. Change Directory to
F:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin. If the
JvmModuleLocation is not proceeded by a semi colon then you must modify the java location
changing jdk160_35 to java1.7.0_161

9. Client Changes

EssbaseAdministration Console
Change Directory to
F:\Oracle\Middleware\EPMSystem11R1\products\Essbase\eas\console\bin\admincon.bat
Modify the admincon.bat and change jdk160_35 to jdk170_161
Financial Reporting Client
Change Directory to F:\Oracle\Middleware\EPMSystem11R1\products\financialreporting\bin
Modify the setJavaRuntime.cmd script changing jdk160_35 to jdk170_161
10. Start all services and Test

You might also like