Document Display Page 1 of 11

Using JDK 7.0 Latest Update with Oracle E-Business Suite Release 12.0 and 12.1 (Doc ID 1467892.1)

Modified: Sep 23, 2013 Type: WHITE PAPER

In this Document
bhavani
History
Details
In This Document
Section 1: Overview
Section 2: Upgrading to Latest JDK 7.0 on Application Tier Nodes
Step 2.1: Prerequisite Patches
Step 2.3: Stop All Application Tier Services
Step 2.4: Replace JDK Home Used With Oracle E-Business Suite Release 12
Step 2.5: Rename Existing JRE Directories
Step 2.6: Install Albany (Display) Font
Section 3: Upgrading to Latest JDK 7.0 in OracleAS 10.1.2 Oracle_Home
Step 3.1: Download and Apply Patch 12848228
Step 3.2: Download and Apply OUI 10.1.0.6 Patch (For Windows Only)
Step 3.3: Download Latest JDK 7.0 Update
Download JDK from the applicable link mentioned in the following table
Step 3.4: Replace JDK Home Used With Oracle E-Business Suite Release 12
Step 3.5: Rename The Following Directories
Step 3.6: Download and Apply Patches (Linux x86, Linux x86-64, and AIX)
For Linux x86, Linux x86-64, AIX Only:
Step 3.7: Rebuild Forms and Reports Executables (For Unix/Linux Only)
Step 3.8: Re-generate Oracle E-Business Suite Forms and Reports
Step 3.9: Restart All Application Tier Services
Section 4: Upgrading to Latest JRE 7.0 on Database Tier Node
Step 4.1: Download Latest JRE 7.0 Update
Step 4.2: Replace JRE Home Used With Oracle E-Business Suite Release 12
Section 5: Verify Application Tier Node Configurations
Step 5.1: Verify Installations On All Web Server Nodes
Step 5.1.1: Navigate to OA_HTML directory
Step 5.1.2: Create JDKtest.jsp file
Step 5.1.3: Compile JDKtest.jsp script
Step 5.1.4: Run JDKtest.jsp script from browser
Step 5.2: Verify Configurations On All Application Tier Nodes
Step 5.2.1: Check JDK version and CLASSPATH
Step 5.2.2: Verify Oracle E-Business Suite concurrent programs
Section 6: Verify JRE Installation on Database Tier Node
Section 7: Known Issues
Requirement for SSO/OID customers
adopmnctl.sh script reporting time out error messages
Change Log
References

APPLIES TO:

Oracle Applications Technology Stack - Version 12.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.

ABSTRACT

A procedure on how to upgrade the JDK 7.0 with use of Oracle E-Business Suite Release 12.0 and 12.1

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 2 of 11

HISTORY

28-May-2013, Heiming Hui, initial

DETAILS

Using JDK 7.0 Latest Update with Oracle E-Business Suite Release 12

In This Document

z Section 1: Overview
z Section 2: Upgrading to Latest JDK 7.0 on Application Tier Nodes
z Section 3: Upgrading to Latest JDK 7.0 in OracleAS 10.1.2 ORACLE_HOME
z Section 4: Upgrading to Latest JRE 7.0 on Database Tier Node
z Section 5: Verify Application Tier Node Configurations
z Section 6: Verify JRE Installation on Database Tier Node
z Section 7: Known Issues

The most current version of this document can be obtained in My Oracle Support Knowledge Document 1467892.1.

There is a change log at the end of this document.

Section 1: Overview
Oracle E-Business Suite Release 12 Rapid Install delivers the following Java SE Development Kit (JDK) Versions for use by Oracle E-Business Suite:

Oracle E-Business Suite Release 12.0.x:

z Java SE Development Kit (JDK) Version 5.0 on the application tier

z Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
z Java SE Runtime Environment (JRE) Version 5.0 on the database tier

Oracle E-Business Suite Release 12.1.x:

z Java SE Development Kit (JDK) Version 6.0 on the application tier

z Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
z Java SE Runtime Environment (JRE) Version 6.0 on the database tier

This document describes how to upgrade to the newer Java 7.0 Update on all tier nodes. Please note that the JRE 7.0 upgrade on the database tier is
independent from the others. But if the application tier nodes are planned to be upgraded to Java 7.0, the same upgrade in the OracleAS 10.1.2
ORACLE HOME must be planned together.

Note: To find the latest version of Java certified with Oracle E-Business Suite Release 12, see My Oracle Support Knowledge Document 418664.1:
Overview of Using Java with Oracle E-Business Suite Release 12.

As with all technology upgrades, these instructions should be tried out on a test instance first, to verify that the implementation and customizations
work properly. If no problems are encountered, you may then upgrade your production instance.

Section 2: Upgrading to Latest JDK 7.0 on Application Tier Nodes

Oracle E-Business Suite Release 12 Rapid Install delivers Oracle Application Server 10.1.3.0 (for release 12.0.x) and Oracle Application Server 10.1.3.4
(for release 12.1.x). This section describes the steps to upgrade the JDK in the 10.1.3 Oracle Home from JDK 1.5/1.6 to JDK 7.0. Upgrading to JDK 7.0
requires Oracle Application Server 10.1.3.5 or higher for the web tier. To take advantage of the latest stability, performance, and security updates,
Oracle strongly recommends that you upgrade your Oracle Application Server 10.1.3 Oracle Home to the latest available release by following the
instructions in My Oracle Support Knowledge Document 454811.1: Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite
Release 12.

Note: If you are carrying out a Release 12.0.x or 12.1 Maintenance Pack upgrade, and have completed the Pre-Update Tasks of "Apply the AD
Minipack" and "Update AutoConfig technology stack templates", you must perform the JDK upgrade steps in this document before applying the
corresponding Maintenance Pack and related update tasks. Specifically, you should skip the following steps in this document:

z Section 2 - Step 4 Install Albany (Display) Font

z All the steps in Section 4: Verify the Application Tier Node Configurations

Step 2.1: Prerequisite Patches

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 3 of 11

Obtain and apply the following Oracle E-Business Suite patches using AutoPatch:

Platform Release Version Patch Prerequisite Patch

Solaris 12.0 Patch 14635756:R12.TXK.A Patch 16214968:R12.TXK.A
Solaris 12.1 Patch 14635756:R12.TXK.B N/A
IBM AIX 12.0 Patch 14635756:R12.TXK.A Patch 16214968:R12.TXK.A
IBM AIX 12.1 Patch 14635756:R12.TXK.B Patch 13579837:R12.TXK.B
All 12.0 Patch 16545472:R12.OAM.A N/A
All 12.1 Patch 16545472:R12.OAM.B N/A
All 12.1 Patch 17309237:R12.TXK.B Check patch readme
Oracle iProcurement 12.0 Patch 16496713:R12.POS.A N/A
Oracle iProcurement 12.1 Patch 16496713:R12.POS.B N/A

Step 2.2: Download Latest JDK 7.0 Update

For optimum stability, performance, scalability, and OS vendor support, it is advisable to use the latest available update of JDK for the Oracle E-Business
Suite application tier.

Note: JDK maintenance releases are denoted by a third digit in the version string, such as 1.7.0. Using Sun Java as an example, the latest updates
of JDK are usually denoted by a fourth set of numbers in the version string, such as 1.7.0_02, or 1.7.0.02, or simply have a name such as JDK 7u2.

Oracle E-Business Suite Release 12 is certified with the JDK maintenance releases listed in the table below. You should only install patch releases that
are listed here.

Click on the appropriate link to download the JDK from the site that corresponds to the operating system being used on the application tier node.
Download the 32-bit JDK, not the Java Runtime Environment (JRE). Do not choose the 64-bit version, which is not supported.

Operating
Certified Java Version JDK 7.0 Download Location
System
Oracle
Solaris JDK 7.0 Update 7 or higher http://www.oracle.com/technetwork/java/javase/downloads/index.html
(SPARC)
Linux JDK 7.0 Update 7 or higher http://www.oracle.com/technetwork/java/javase/downloads/index.html
Windows JDK 7.0 Update 7 or higher http://www.oracle.com/technetwork/java/javase/downloads/index.html
HP Itanium JDK 7.0.03 or higher http://www.hp.com/go/java
JDK patch IV38628 on top of 1.7.0 SR3,
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-ibmjavaisv
JDK patch IV38628 on top of 1.7.0 SR4
IBM AIX Note: Log in using IBM ID. The access key is MJ3D7TQGMK. Then, select and download
FP2, JDK patch IV46430+IV45517 on
j732redist.7.0.0.62.bin for SR3, j732redist.7.0.0.91.bin for SR4 FP2 or j732redist.bin for SR5
top of 1.7.0 SR5

Note: For IBM AIX, select and download the redistribution .BIN images. If the JDK 7.0 is installed using the default installp/smit format installer,
there will be a few symbolic links presented within the newly installed JDK 7.0 home, which point to absolute paths of the system's default installed
location (i.e., /usr/java7). This could be a problem for the Rapid Clone utility. To avoid this problem, obtain and install the latest JDK 7.0 SR version
(see above "Certified Java Version") using the redistribution .BIN image installer. If you're using JDK patch IV38628 on top of 1.7.0 SR3 or JDK
patch IV38628 on top of 1.7.0 SR4 FP2, run the installer in the text mode by not setting the environment variable of DISPLAY and do not run the
installer in the GUI mode because the installer GUI may crash intermittently. This issue has been fixed in JDK patch IV46430+IV45517 on top of
1.7.0 SR5 or higher.

Always review in detail the installation instructions and release notes for the vendor's JDK to ensure that the operating system version is supported with
JDK 7.0. Before installing the latest update of JDK 7.0, it may be necessary to upgrade to a later, certified version of the operating system, or to apply
operating system patches.

Step 2.3: Stop All Application Tier Services

Stop all application tier services before installing the latest update of JDK 7.0 into the [IAS_ORACLE_HOME]/appsutil/jdk location. Enter the applicable
commands below.

UNIX:

$ cd $INST_TOP/admin/scripts/
$ adstpall.sh [APPS username/APPS password]

Windows:

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 4 of 11

C:\>cd %INST_TOP%\admin\scripts
C:\>adstpall.cmd [APPS username/APPS password]

An alternative on Windows is to stop the processes using the Services applet, located in the Control Panel under Administrative Tools.

Step 2.4: Replace JDK Home Used With Oracle E-Business Suite Release 12

Oracle E-Business Suite application tier uses the JDK from a fixed installation location, [IAS_ORACLE_HOME]/appsutil/jdk. This can be replaced either by
copying the installation from a separate default location or working directory, or by replacing the old JDK installation with the new one on each
application tier node. Perform this action by entering the applicable commands below.

Note: If the latest update of JDK 7.0 is installed by copying the installation from an existing JDK 7.0 directory, UNIX/Linux users should ensure that
the symbolic links (soft links) are preserved during the copying operation. On most UNIX platforms, this can be accomplished with the "cp -RH"
command. Consult the UNIX man page for the cp command and check the parameters available on the specific platform.

Alternatively, the tar command can be used to compress the directories into a temporary staging area. UNIX/Linux users should ensure that the
symbolic links (soft links) are preserved when compressing. On most UNIX platforms, this is the default behavior of tar command. Consult the UNIX
man page for the tar command and check the parameters available on the specific platform.

$ cd [IAS_ORACLE_HOME]/appsutil
$ mv jdk jdk_old
/** Install the latest JDK 7.0 Update here. In the example, the directory name is jdk1.7.0_5 .**/
$ mv jdk1.7.0_5 jdk

The final line installs the latest update of JDK 7.0 into the [IAS_ORACLE_HOME]/appsutil directory. In this example, the version is 7.0_5.

Windows:

C:\>cd [IAS_ORACLE_HOME]/appsutil
C:\>rename jdk jdk_old
C:\>mkdir jdk
C:\>cd jdk

Download the latest JDK at [jdk1.7.0._latest_update#] location and then move all the files and sub directories under [jdk1.7.0._latest_update#] to
[IAS_ORACLE_HOME]\appsutil\jdk directory.

Note:

When installing JDK 7.0 for windows, by default the following options are selected:

z Development Tools
z Demos and Samples code
z Source Code
z Public JRE
z Java DB

Please de-select the Source Code, Public JRE and Java DB options by clicking on each one and selecting 'Don't install this feature now'. This will
prevent issues occurring due to the JRE being installed in the same directory as the JDK.

Note: After replacing the old JDK install home with the new certified update of JDK, do not rename the [IAS_ORACLE_HOME]/appsutil/jdk
directory, or the Oracle E-Business Suite application tier will not function correctly.

Step 2.5: Rename Existing JRE Directories

The existing JRE directory is no longer needed. Perform this action by entering the applicable commands below.

UNIX:

$ mv [IAS_ORACLE_HOME]/jre/1.4.2 [IAS_ORACLE_HOME]/jre/1.4.2_old

Windows:

C:\>rename [IAS_ORACLE_HOME]\jre\1.4.2 [IAS_ORACLE_HOME]\jre\1.4.2_old

Step 2.6: Install Albany (Display) Font

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 5 of 11

Installation of the font files listed below is required to support Oracle XML Publisher and enable the Oracle UIX Dynamic Image technology to
successfully generate images. These font files must be available on each application tier node. They are located under $FND_TOP/resource.

The font files are:

z ALBANYWT.ttf - Single-byte characters only

z ALBANWTJ.ttf - Unicode font with Japanese Han Ideographs
z ALBANWTK.ttf - Unicode font with Korean Han Ideographs
z ALBANWTS.ttf - Unicode font with Simplified Chinese Han Ideographs
z ALBANWTT.ttf - Unicode font with Traditional Chinese Han Ideographs

On each application tier node, use the applicable commands to copy the font files from $FND_TOP/resource to the JDK installation location, i.e. the
[IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/fonts directory.

UNIX:

$ cp $FND_TOP/resource/font_file_name.ttf [IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/fonts

Windows:

C:\>copy %FND_TOP%\resource\font_file_name.ttf [IAS_ORACLE_HOME]\appsutil\jdk\jre\lib\fonts

For more details, refer to My Oracle Support Knowledge Document 240862.1: Install Oracle Unicode Fonts for Dynamic Image Generation in Oracle
Applications.

Section 3: Upgrading to Latest JDK 7.0 in OracleAS 10.1.2 Oracle_Home

Oracle Application Server (OracleAS) 10g Forms and Reports comes with JDK 1.4. This section describes the steps to upgrade the JDK in the 10.1.2
Oracle Home to JDK 7.0. We recommend that you apply the latest forms and reports patch in My Oracle Support Knowledge Document 437878.1 :
Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12, before upgrading to JDK 7.0.

Note: If you have upgraded the JDK used in OracleAS 10.1.2 JDK 1.6 previously, you can skip Step 3.1 and Step 3.2 in this section which you've
already performed during the previous 10.1.2 JDK 1.6 upgrade..

Note (for AIX only) :

There is a known issue in relinking any binaries or libraries under <10.1.2 Oracle_Home>/sysman after upgrading to JDK 7.0 in the 10.1.2 Oracle
Home. If any OracleAS 10.1.2 one-off patch you apply or rollback fails due to such an error, please ignore it and proceed with the Opatch session to
complete the OracleAS patch application.

Step 3.1: Download and Apply Patch 12848228

Apply Patch 12848228 to your 10.1.2.3 Oracle Home using Opatch.

Step 3.2: Download and Apply OUI 10.1.0.6 Patch (For Windows Only)

If you have not yet upgrade your OUI to 10.1.0.6 you are required to do so now. Please download and apply Patch 6640838 . Select all the OUI
components for installation except for JDK 1.4.2. The installer will prompt for an existing JDK to use. Point the installer to the [10.1.2_ORACLE_HOME]
JDK location.

Step 3.3: Download Latest JDK 7.0 Update

Click on the appropriate link below to download the JDK from the site that corresponds to the operating system being used on the application tier node.
Download the 32-bit JDK, not the Java Runtime Environment (JRE). Do not choose the 64-bit version, which is not supported.

Download JDK from the applicable link mentioned in the following table

Operating
Certified Java Version JDK 7.0 Download Location
System
Oracle Solaris
JDK 7.0 Update 7 or higher http://java.sun.com/javase/downloads/index.jsp
(SPARC)
Linux JDK 7.0 Update 7 or higher http://java.sun.com/javase/downloads/index.jsp
Windows JDK 7.0 Update 7 or higher http://java.sun.com/javase/downloads/index.jsp

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 6 of 11

HP Itanium JDK 7.0.03 or higher http://www.hp.com/go/java

JDK patch IV38628 on top of 1.7.0 SR3,
JDK patch IV38628 on top of 1.7.0 SR4
IBM AIX
FP2, JDK patch IV46430+IV45517 on top
of 1.7.0 SR5
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-ibmjavaisv
Note: Log in using IBM ID. The access key is MJ3D7TQGMK. Then, select and download
j732redist.7.0.0.62.bin for SR3, j732redist.7.0.0.91.bin for SR4 FP2 or K732redist.bin for
SR5

Note: For IBM AIX, select and download the redistribution .BIN images. If the JDK 7.0 is installed using the default installp/smit format installer,
there will be a few symbolic links presented within the newly installed JDK 7.0 home, which point to absolute paths of the system's default installed
location (i.e., /usr/java7). This could be a problem for the Rapid Clone utility. To avoid this problem, obtain and install the latest JDK 7.0 SR version
(see above "Certified Java Version"), using the redistribution .BIN image installer. If you're using JDK patch IV38628 on top of 1.7.0 SR3 or JDK
patch IV38628 on top of 1.7.0 SR4 FP2, run the installer in the text mode by not setting the environment variable of DISPLAY and do not run the
installer in the GUI mode because the installer GUI may crash intermittently. This issue has been fixed in JDK patch IV46430+IV45517 on top of
1.7.0 SR5 or higher.

Please always review in detail and follow the installation instructions and release notes for the vendor's JDK on specific platform. Ensure that the
operating system version is supported with JDK 7.0. Before installing the latest update of JDK 7.0, it may be necessary to upgrade to a later, certified
version of the operating system, or to apply operating system patches.

Step 3.4: Replace JDK Home Used With Oracle E-Business Suite Release 12

The JDK home within the OracleAS 10.1.2 Forms and Reports ORACLE_HOME can be replaced by entering the applicable commands below.

Note: If the latest update of JDK 7.0 is installed by copying the installation from an existing JDK 7.0 directory, UNIX/Linux users should ensure that
the symbolic links (soft links) are preserved during the copying operation. On most UNIX platforms, this can be accomplished with the "cp -RH"
command. Consult the UNIX man page for the cp command and check the parameters available on the specific platform.

Alternatively, the tar command can be used to compress the directories into a temporary staging area. UNIX/Linux users should ensure that the
symbolic links (soft links) are preserved when compressing. On most UNIX platforms, this is the default behavior of tar command. Consult the UNIX
man page for the tar command and check the parameters available on the specific platform.

UNIX:

$ cd [10.1.2_ORACLE_HOME]
$ mv jdk jdk_old
/* Now install the downloaded latest update of JDK 7.0 here. In this example the version is 7.0_2. Then */
$ mv jdk1.7.0_2 jdk

Windows:

C:\>cd [10.1.2_ORACLE_HOME]
C:\>rename jdk jdk_old
/* Now install the downloaded latest update of JDK 7.0 here. In this example the version is 7.0_2. Then */
C:\>rename jdk1.7.0_2 jdk

Step 3.5: Rename The Following Directories

Note: The JDK 1.7 that you installed in the step above contains the directories which replace what you are renaming below. No action required
to create any new directories manually.

UNIX:

$mv [10.1.2_ORACLE_HOME]/jdk64 [10.1.2_ORACLE_HOME]/jdk64_old

$mv [10.1.2_ORACLE_HOME]/jre/1.4.2 [10.1.2_ORACLE_HOME]/jre/1.4.2_old
$mv [10.1.3_ORACLE_HOME]/jre/1.4.2 [10.1.3_ORACLE_HOME]/jre/1.4.2_old

Windows:

$rename [10.1.2_ORACLE_HOME]\jdk64 [10.1.2_ORACLE_HOME]\jdk64_old

$rename [10.1.2_ORACLE_HOME]\jre\1.4.2 [10.1.2_ORACLE_HOME]\jre\1.4.2_old
$rename [10.1.3_ORACLE_HOME]\jre\1.4.2 [10.1.3_ORACLE_HOME]\jre\1.4.2_old

Step 3.6: Download and Apply Patches (Linux x86, Linux x86-64, and AIX)

For Linux x86, Linux x86-64, AIX Only:

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 7 of 11

Operating
Other Patch Forms Patch Reports Patch ProC Patch
System
Patch 16271876
Linux Patch 14703419 Patch 16207165 Patch 16241466
(Apply this patch first)
AIX Patch 13686664 Patch 14029977

Note: Please carefully review the patch README which contains important instructions for the patch application and the post patch steps. When
applying some of these patches, you might face an opatch error while it tries to rollback the previous patch. You can safely ignore the error as
indicated in the patch readme.

Step 3.7: Rebuild Forms and Reports Executables (For Unix/Linux Only)

Note: If you have relinked forms/reports when applying one-off patches in Step 3.6, you can skip this section.

Source the environment (under $INST_TOP/ora/10.1.2) to point to the 10.1.2 Oracle Home before relinking forms and reports executables.

cd $ORACLE_HOME/forms/lib32
/* Note: if this directory does not exist, use the following command: */
cd $ORACLE_HOME/forms/lib
$ make -f ins_forms.mk sharedlib install

cd $ORACLE_HOME/reports/lib32
/* Note: if this directory does not exist, use the following command: */
cd $ORACLE_HOME/reports/lib
$ make -f ins_reports.mk install

Step 3.8: Re-generate Oracle E-Business Suite Forms and Reports

Run ADAdmin and select the Forms and Reports regeneration.

Step 3.9: Restart All Application Tier Services

Restart the application tier services using the applicable commands below.

UNIX:

$ cd $INST_TOP/admin/scripts/
$ adstrtal.sh [APPS username/APPS password]

Windows:

C:\>cd %INST_TOP%\admin\scripts\
C:\>adstrtal.cmd [APPS username/APPS password]

An alternative on Windows is to start the services using the Services applet, located in the Control Panel under Administrative Tools.

The Oracle E-Business Suite system is now configured to use the latest update of JDK 7.0 on the application tier nodes. Section 4 describes how to
perform the equivalent JRE 7.0 upgrade steps on the database tier node.

Section 4: Upgrading to Latest JRE 7.0 on Database Tier Node

This section describes the steps to upgrade the JDK in the Oracle E-Business Suite database tier from JDK 1.5/1.6 to JDK 7.0 if your Oracle database
version is below 11gR2.

Note: If you have upgraded the Oracle database version to 11gR2 or higher on the database tier, do not perform this section since the
AutoConfig uses the JRE from <Oracle_Home>/jdk/jre.

Step 4.1: Download Latest JRE 7.0 Update

For optimum stability, performance, scalability, and OS vendor support, it is advisable to use the latest available update of JRE for the Oracle E-Business
Suite database tier.

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 8 of 11

Oracle E-Business Suite Release 12 is certified with the JRE maintenance releases listed in the table below. You should only install patch releases that
are listed here.

Click on the appropriate link to download the JRE from the site that corresponds to the operating system being used on the database tier node.

Note: Download the 32-bit JRE only, not the Java SE Development Kit (JDK).

Operating
Certified Java Version JRE 7.0 Download Location
System
Oracle Solaris
JRE 7.0 Update 7 or higher http://www.oracle.com/technetwork/java/javase/downloads/index.html
(SPARC)
Linux JRE 7.0 Update 7 or higher http://www.oracle.com/technetwork/java/javase/downloads/index.html
Windows JRE 7.0 Update 7 or higher http://www.oracle.com/technetwork/java/javase/downloads/index.html
HP Itanium JRE 7.0.03 or higher http://www.hp.com/go/java
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-ibmjavaisv
JRE patch IV46430+IV45517 on
IBM AIX Note: Log in using IBM ID. The access key is MJ3D7TQGMK. Then, select and download
top of 1.7.0 SR5"
jre732redist.bin for SR5.

Note: For IBM AIX, select to download the redistribution .BIN images. If the JRE 7.0 is installed using the default installp/smit format installer,
there will be a few symbolic links presented within the newly installed JRE 7.0 home, which point to absolute paths of the system's default installed
location (i.e., /usr/java7). This could be a problem for the Rapid Clone utility. To avoid this problem obtain and install the latest JDK 7.0 SR version
(see above "Certified Java Version") using the redistribution .BIN image installer.

Always review in detail the installation instructions and release notes for the vendor's JRE to ensure that the operating system version is supported with
JRE 7.0. Before installing the latest update of JRE 7.0, it may be necessary to upgrade to a later, certified version of the operating system, or to apply
operating system patches.

Step 4.2: Replace JRE Home Used With Oracle E-Business Suite Release 12

The Oracle E-Business Suite database tier uses the JRE 7.0 from a fixed installation location, [ORACLE_HOME]/appsutil/jre. This can be replaced by
copying the install from a separate default location or working directory, or by installing the new version following the procedure below, which replaces
the old JRE installation used by AutoConfig with a new one for each database tier node. Enter the applicable commands.

Note: If the latest update of JRE 7.0 is installed by copying the installation from an existing JRE 7.0 directory, UNIX/Linux users should ensure that
the symbolic links (soft links) are preserved during the copying operation. On most UNIX platforms, this can be accomplished with the "cp -RH"
command. Consult the UNIX man page for the cp command and check the parameters available on the specific platform.

Alternatively, the tar command can be used to compress the directories into a temporary staging area. UNIX/Linux users should ensure that the
symbolic links (soft links) are preserved when compressing. On most UNIX platforms, this is the default behavior of tar command. Consult the UNIX
man page for the tar command and check the parameters available on the specific platform.

UNIX:

$ cd [ORACLE_HOME]/appsutil
$ mv jre jre_old
/** Install the latest JRE 7.0 Update here. In the example, the directory name is jre1.7.0_5 .**/
$ mv jre1.7.0_5 jre

The final line installs the latest update of JRE 7.0 into the [ORACLE_HOME]/appsutil directory. In this example, the version is 7.0_5.

Windows:

C:\>cd [ORACLE_HOME]\appsutil
C:\>rename jre jre_old
C:\>mkdir jre
C:\>cd jre

Download the latest JRE at [jre1.7.0._latest_update#] location and then move all the files and sub directories under [jre1.7.0._latest_update#] to
[ORACLE_HOME]\appsutil\jre directory.

Note:

z Do not upgrade the [ORACLE_HOME]/jdk and [ORACLE_HOME]/jre which are used by the Oracle database.

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 9 of 11

z After replacing the old JRE install home with the new certified update of JRE, do not rename the [ORACLE_HOME]/appsutil/jre directory.
Otherwise, the Oracle E-Business Suite AutoConfig on the database tier will not function correctly.

The Oracle E-Business Suite system is now configured to use the latest update of JRE 7.0 on the database tier. Proceed to Section 5 to perform the
verification steps.

Section 5: Verify Application Tier Node Configurations

The steps in this section must be performed on each application tier node.

Step 5.1: Verify Installations On All Web Server Nodes

Follow these steps to verify that JDK 7.0 has been successfully installed on all the Web server node(s):

Step 5.1.1: Navigate to OA_HTML directory

Go to the OA_HTML directory on the Web server.

Step 5.1.2: Create JDKtest.jsp file

Using a text editor, create a file called JDKtest.jspunder [OA_HTML] containing the following line:

The JDK version is: <%= System.getProperty("java.version") %>

Step 5.1.3: Compile JDKtest.jsp script

Use the following command (same on UNIX and Windows) to compile the .jsp file:

$ perl -x $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s 'JDKtest.jsp'

Step 5.1.4: Run JDKtest.jsp script from browser

Access the JSP file from a browser, using the URL:

http://[web server]:[port]/OA_HTML/JDKtest.jsp

You should see something like:

The JDK version is: 1.7.0_5

Where the last portion (in this case, 5) is the number of the installed JDK 7.0 latest update.

The Web server node is now configured to use the latest update of JDK 7.0.

As the system configuration has changed, you should log in to Oracle E-Business Suite Release 12 and perform some routine tasks to ensure all
functionality is working as expected.

Step 5.2: Verify Configurations On All Application Tier Nodes

Follow these steps to confirm that JDK 7.0 is running on all application tier nodes.

Step 5.2.1: Check JDK version and CLASSPATH

Open the $APPL_TOP/admin/adovars.env file and ensure that the environment variables below are defined. Run the following commands to verify that
the environment variables ADJVAPRG and AFJVAPRG point to the JDK 7.0 executable. The CLASSPATH and AF_CLASSPATH environment variables must
contain the necessary JDK 7.0 libraries.

UNIX:

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 10 of 11

$ $ADJVAPRG -version
$ echo $CLASSPATH
$ $AFJVAPRG -version
$ echo $AF_CLASSPATH

Windows:

C:\>%ADJVAPRG% -version
C:\>echo %CLASSPATH%
C:\>%AFJVAPRG% -version
C:\>echo %AF_CLASSPATH%

The output of the version check should display JDK "1.7.0_x", where x is the number of the installed JDK 7.0 update. The CLASSPATH and
AF_CLASSPATH environment variable must contain the necessary JDK 7.0 libraries, which should include:

z [IAS_ORACLE_HOME]/appsutil/jdk/lib/dt.jar
z [IAS_ORACLE_HOME]/appsutil/jdk/lib/tools.jar
z [IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/rt.jar
z [IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/charsets.jar

Step 5.2.2: Verify Oracle E-Business Suite concurrent programs

1. Log in to Oracle E-Business Suite and select the "System Administrator" responsibility.
2. Check the Concurrent --> Manager --> Administer form and ensure that all managers have the appropriate numbers for their actual and target.
For more details on how to manage concurrent managers and concurrent programs, refer to Managing Concurrent Processing and Concurrent
Programs, Chapter 2 of Oracle Applications System Administrator's Guide - Maintenance.

Section 6: Verify JRE Installation on Database Tier Node

Follow the steps below to verify that JRE 7.0 has been successfully installed on the database node:

UNIX:

$ cd [ORACLE_HOME]/appsutil/jre/bin
$ java -version

The output of the version check should display "Java(TM) SE Runtime Environment (build 1.7.0_x", where x is the number of the installed JRE 7.0
update.

Windows:

C:\>cd [ORACLE_HOME]\appsutil\jre/bin
C:\>java -version

The output of the version check should display "Java(TM) SE Runtime Environment (build 1.7.0_x", where x is the number of the installed JRE 7.0
update.

The database tier node is now configured to use the latest update of JRE 7.0 for AutoConfig.

Section 7: Known Issues

IBM AIX

Requirement for SSO/OID customers

Refer to My Oracle Support Knowledge Document 376811.1 : Integrating Oracle E-Business Suite Release 12 with Oracle Internet Directory and Oracle
Single Sign-On 10gR3 for the specific instructions when utilizing the E-Business Suite with JDK 7.0 .

IBM AIX

adopmnctl.sh script reporting time out error messages

With JDK 7, the run of the adopmnctl.sh script reports the time out error messages when stopping oacore, oafm, and forms. The OPMN processes are
forcefully shut down, but the adopmnctl.sh script exits with the status 206. Please ignore this error message since it does not cause any issue. This
issue is being investigated by Oracle and IBM so that the OPMN processes will be gracefully shut down.

Windows

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013
Document Display Page 11 of 11

After the JDK upgrade, you will see a warning messgage in the concurrent request log file such as ' WARNING: "IOP02310202: (OBJ_ADAPTER) Error in
connecting servant to ORB'. You can safely ignore this message as it does not have any functional impact.

Change Log
Date Description
June 5, 2013 z Initial document created.
July 9, 2013 z Updates as per doc bugs 14294307, 16950497
July 29, 2013 z Updates as per doc bug 17195009
Aug 19, 2013 z Updates as per doc bugs 17319617, 17302595

My Oracle Support Knowledge Document 1467892.1 by Oracle E-Business Suite Development

Copyright © 2013, Oracle Corporation

https://support.oracle.com/epmos/faces/SearchDocDisplay... 10/18/2013