Using the Latest JDK 7.

0 Update with Oracle E-Business Suite Release

12.2

Verifying Online Patching Activities and Prepare for Patching:

Before you upgrade the Java version, it is essential to check that there is no open online patching
cycle by running one of the following commands:

UNIX:
$ adop -status

Prepare for Patching:

The JDK 7.0 configuration changes will be applied to the patch file system first. Use the
following command to prepare the patch file system for patching:

UNIX:
$ adop phase=prepare

Run the Environment Script for the Patch File System:

Since the prerequisite patches and the JDK 7.0 configuration changes are applied to the patch file
system first, use the following commands to source the Oracle E-Business Suite environment with the
patch file system:

UNIX:
$ cd /d02/R122 /* <EBS_BASE_HOME> where fs1, fs2 and others are installed. */
$ . ./EBSapps.env /*Type "P" to select the PATCH file system environment when prompted. */
$ echo $FILE_EDITION /* This returns "patch" to indicate that it uses the patch file
system environment. */

Note: Unless the run file system is mentioned explicitly, references to all files (such as the Oracle E-
Business Suite context files and environment setup scripts), refer to the copies under the patch file
system. This includes the directories mentioned in this document.
Upgrading to Latest Java 7.0 on Application Tier Nodes:

Click on the below link to download the Java for Linux x86-64 from the site that corresponds to the
operating system being used on the application tier node. Download the JDK, not the Java Runtime
Environment (JRE).

Java SE Downloads on My Oracle Support Knowledge Document 1439822.1

Oracle E-Business Suite Release 12.2 Prerequisite Patches

(Conditional):

Download and apply the following Oracle E-Business Suite updates to your Oracle E-Business
Suite Release 12.2.2 instance:

Release Patch Number

12.2.2 R12.TXK.C.DELTA.3 Patch 17021789
Note: already applied, we are on Delta 11.

Oracle Fusion Middleware 11g Prerequisite Patches (Conditional):

If the Oracle E-Business Suite environment was created using a startCD prior to startCD 46, the
following Oracle Fusion Middleware 11g (version 11.1.1.6.0) patches are required before the
JDK 7.0 upgrade for the Oracle E-Business Suite application tier:

 Oracle Fusion Middleware 11g patch using Smart Update Utility.

 Oracle Fusion Middleware 11g Patch 16199894 — This needs to be applied to all Oracle
E-Business Suite platforms. Apply this patch using OPatch. Be sure to apply the patch
twice — against [FMW_HOME]/oracle_common as well as EBS WebTier [OAH] Oracle
Homes.

Note: Oracle EBS is on Fusion Middleware 11.1.1.9.0

Identify Java Home Used with Oracle E-Business Suite Release 12.2:
Each Oracle E-Business Suite application tier uses the Java from a fixed installation location depending
on the use of 32-bit or 64-bit Java. The following tables show the Java usage and the existing and the
(new) targeted upgrading installation locations.

Oracle E-Business Suite Running on 64-bit hardware architectures:

Operating Application 32-bit and 64-bit Java 6 Targeted Java 7 Installation

System Tier Node Installation Locations Location
Linux x86- Application [FMW_HOME]/jrockit64 [COMMON_TOP]/util/jdk64
64 middle tier node
CP tier node [FMW_HOME]/jrockit32 [COMMON_TOP]/util/jdk32
*
AD/AutoConfig [FMW_HOME]/jrockit32 [COMMON_TOP]/util/jdk32
Cloning Tools [FMW_HOME]/Oracle_EBS- [COMMON_TOP]/util/jdk64
app1/jdk (by symbolic link)

Additional Notes:

 For the Oracle E-Business Suite running on 64-bit hardware architectures, the 64-bit Java
is used for the application tier node and for the cloning tools. For the CP tier node and
AD/AutoConfig, the 32-bit Java is still used. * In 12.2.6 or higher, the 64-bit Java is used
for the CP tier by default.

 If Oracle E-Business Suite environment is installed using startCD 47 or above, the JDK 7
installations are already in place in the targeted locations listed above.

 After the JDK upgrade, any additional certificates added to the cacerts file directory
(usually located in [COMMON_TOP]/util/<java>/jre/lib/security directory) will be lost.
Keep a copy of the original cacerts file which can be used to restore back. Or make a note
that the cacerts file will need to be added back in the final targeted JDK 7 installation
directory. Refer to My Oracle Support Knowledge Document 1591073.1, Enhanced Jar
Signing for Oracle E-Business Suite.

Upgrading Java Home Used with Oracle E-Business Suite Release 12.2:

When upgrading to JDK 7.0, the final targeted JDK 7 installation must be located in
[COMMON_TOP]/util/<java>, where <java> could be "jdk", "jdk32", and "jdk64" depending on
the bitness of the JDK. Depending on the type of Java installed or the Oracle E-Business Suite
environment setup, there are two scenarios of the JDK 7.0 upgrade process as follows:
 1. Final targeted JDK 7 installation location different from the existing JRockit or JDK 6
installation location, which includes:
o First-time Java 6 upgrading to JDK 7 on Linux or Solaris operating system
2. Final targeted JDK 7 installation location same as for the existing JDK installation (but
the existing JDK version is different from the latest JDK 7 Update), which includes:
o First-time JDK 6 upgrading to JDK 7 on HP-UX or IBM AIX operating system
o Already upgraded JDK 7 environment with the lower revision upgrading to the
latest revision of JDK 7.0 Update on any operating system

Select the appropriate one above and proceed the next step.

Targeted JDK 7 Installation Location Same as for the Existing One:

The procedure applies to the JDK 7.0 upgrade under two circumstances as follows:

 First-time JDK 6 upgrading to JDK 7 on HP-UX or IBM AIX.

 Existing JDK 7 environment with the lower revision upgrading to the latest JDK 7.0
Update on any operating system.

Prior the upgrade, there is an existing old JDK installed into the fixed location under
[COMMON_TOP]/util/<java>, where <java> is "jdk", "jdk32", and "jdk64". To upgrade to the
latest JDK 7.0 Update, it becomes easy by replacing the contents of the existing old JDK with
the ones of latest JDK 7.0 Update. There are no configuration changes required. Perform the
following steps.

Install New JDK 7.0 and Replace the Existing JDK Home Contents:
For each unique JDK location listed, replace it with a corresponding JDK7 installation with the same
bitness either by copying the installation from the newly downloaded location, or by replacing the entire
JDK location with a new installation.

Note: If 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 when copying. On most UNIX
platforms, this can be accomplished with the cp -RH command. Consult the UNIX man page for the cp
command to check the parameters available on your 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 the tar command. Consult the UNIX man page for
the tar command to check the parameters available on your platform.
64-bit Linux x86-64 operating system (for JDK 7.0 previously migrated environment):

$ cd $COMMON_TOP/util/
$ rm -rf jdk32 /* Remove previous JDK 7 maintenance release */
$ rm -rf jdk64 /* Remove previous JDK 7 maintenance release */
$ /* Install the latest JDK 7.0 Update here*/
$ mv jdk1.7.0_[latest_32-bit_update#] jdk32
$ mv jdk1.7.0_[latest_64-bit_update#] jdk64
cd /backup/JDK170191/32
mv jdk1.7.0_191 jdk32
cp -RH jdk32/ $COMMON_TOP/util

cd /backup/JDK170191/64
mv jdk1.7.0_191 jdk64
cp -RH jdk64/ $COMMON_TOP/util

Note: For all platforms, after replacing the old Java install home with the new certified JDK 7.0 Update,
do not rename the [COMMON_TOP]/util/jdk, [COMMON_TOP]/util/jdk32, or
[COMMON_TOP]/util/jdk64 directories. If you do, the Oracle E-Business Suite application tier will not
function correctly.

Run Oracle E-Business Suite AutoConfig utility:

cd $ADMIN_SCRIPTS_HOME

./adautocfg.sh appspass={APPSPASSWORD}

Upgrading to Latest Java 7.0 in Oracle Fusion Middleware 11g Web

Tier:
This section describes the steps to upgrade the JDK with the latest Java 7.0 Update in the web tier of
Oracle Fusion Middleware 11g Home on the patch file system.

Replace JDK Home Used in the Web Tier of Oracle Fusion Middleware 11g Home:

The JDK home within the web tier of Oracle Fusion Middleware 11g Home can be replaced by
entering the applicable commands below.

UNIX:

$ cd $FMW_HOME/webtier
$ mv jdk jdk_03DEC2021
/* Now install the downloaded latest JDK 7.0 Update. In this example, the version is 1.7.0_9.
Then perform the following steps. */

$ cd /backup/JDK170191/64
$ cp -RH jdk64/ $FMW_HOME/webtier

cd $FMW_HOME/webtier
$ mv jdk64/ jdk

The JDK 7.0 upgrade for the Oracle Fusion Middleware 11g web tier is now complete.

Upgrading to Latest Java 7.0 in OracleAS 10.1.2 Oracle_Home:

This section describes the steps to upgrade the JDK with the latest Java 7.0 Update in the 10.1.2 Oracle
Home on the patch file system.

Replace JDK Home Used with Oracle E-Business Suite Release 12.2:

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

UNIX:

$ cd /d02/R122/fs1/EBSapps/10.1.2/
$ mv jdk jdk_03Dec2021
/* Now install the downloaded latest JDK 7.0 Update here. In this example the
version is 1.7.0_9. Then perform the following step. */

$ cd /backup/JDK170191/32
$ cp -RH jdk32 /d02/R122/fs1/EBSapps/10.1.2/
$ cd /d02/R122/fs1/EBSapps/10.1.2/
$ mv jdk32 jdk

OracleAS 10.1.2 Prerequisite Patches (For Linux Only)

The following OracleAS 10.1.2 patches are required before the JDK 7.0 upgrade on the
OracleAS 10.1.2 Oracle_Home on the Linux platform only:

 OracleAS 10.1.2 Patch 16271876

 OracleAS 10.1.2 Patch 17907988
 OracleAS 10.1.2 Forms Patch 17653437
 OracleAS 10.1.2 Patch 16241466
 OracleAS 10.1.2 Patch 17645157

Obtain them and apply using OPatch. Be sure to apply the OracleAS 10.1.2 Patch 16271876
first.
Note: When applying any above patches, ignore the conflicts with any existing installed patches if there
are. The above patches already have the fixes from the conflicting patches. Also, the Patch 17907988
should be applied before the Forms Patch 17653437 application.

The above Patches already applied.

Rebuild Forms and Reports Executables (For UNIX/Linux Only):

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

Source the environment to point to the 10.1.2 Oracle Home before relinking forms and reports
executables.

$ cd $ORACLE_HOME/forms/lib32
/* If this directory does not exist, do the following: */
$ cd $ORACLE_HOME/forms/lib
$ make -f ins_forms.mk sharedlib install
$
$ cd $ORACLE_HOME/reports/lib32
/* If this directory does not exist, do the following: */
$ cd $ORACLE_HOME/reports/lib
$ make -f ins_reports.mk install

The JDK 7.0 upgrade for the Oracle Home 10.1.2 is now complete.

Cut Over to Newly Installed JDK 7.0 Patch File System:

Enter the applicable command to cut over to the newly installed JDK 7.0 patch file system:

UNIX:

$ adop phase=cutover

Verify Application Tier Node Configurations:

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

Verify Installations on All Web Server Nodes:

Follow these steps to verify that Java 7.0 has been successfully installed on all the Web server
node(s):
cd /d02/R122/
. ./EBSapps.env run

E-Business Suite Environment Information

----------------------------------------
RUN File System : /d02/R122/fs1/EBSapps/appl
PATCH File System : /d02/R122/fs2/EBSapps/appl
Non-Editioned File System : /d02/R122/fs_ne

DB Host: erptest1.crescent.com.pk Service/SID: PROD

E-Business Suite Environment Setting

------------------------------------
- Enter [R/r] for sourcing Run File System Environment file, or
- Enter [P/p] for sourcing Patch File System Environment file, or
- Enter anything else to exit

Please choose the environment file you wish to source [R/P]:R

Sourcing the RUN File System ...

[oracle@erptest1 R122]$

Navigate to OA_HTML directory:

Go to the OA_HTML directory on the Web server.

cd $OA_HTML

/d02/R122/fs1/FMW_Home/Oracle_EBS-app1/applications/oacore/html

Create JDKtest.jsp file

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

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

Compile JDKtest.jsp script

Use the following command to compile the .jsp file:

UNIX:

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

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_9

Verify Configurations on All Application Tier Nodes:

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

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:

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

[oraapps@financials admin]$ $ADJVAPRG -version

java version "1.7.0_281"
Java(TM) SE Runtime Environment (build 1.7.0_281-b32)
Java HotSpot(TM) Server VM (build 24.281-b32, mixed mode)
[oraapps@financials admin]$ echo $CLASSPATH
/oracle/apps/R12_2/fs2/EBSapps/comn/util/jdk32/lib/dt.jar:/oracle/apps/R12_2/
fs2/EBSapps/comn/util/jdk32/lib/tools.jar:/oracle/apps/R12_2/fs2/EBSapps/
comn/util/jdk32/jre/lib/rt.jar:/oracle/apps/R12_2/fs2/EBSapps/comn/shared-
libs/ebs-3rdparty/WEB-INF/lib/ebs3rdpartyManifest.jar:/oracle/apps/R12_2/fs2/
FMW_Home/Oracle_EBS-app1/shared-libs/ebs-fmw/WEB-INF/lib/ebsFMWManifest.jar:/
oracle/apps/R12_2/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/oracle/apps/R12_2/fs2/FMW_Home/
oracle_common/modules/oracle.uix_11.1.1/uix2.jar:/oracle/apps/R12_2/fs2/
EBSapps/comn/java/classes:/oracle/apps/R12_2/fs2/EBSapps/10.1.2/forms/java:/
oracle/apps/R12_2/fs2/EBSapps/10.1.2/forms/java/frmall.jar:/oracle/apps/
R12_2/fs2/EBSapps/10.1.2/jlib/ewt3.jar:/oracle/apps/R12_2/fs2/EBSapps/10.1.2/
j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/WEB-INF/lib/frmsrv.jar
[oraapps@financials admin]$ $AFJVAPRG -version
java version "1.7.0_281"
Java(TM) SE Runtime Environment (build 1.7.0_281-b32)
Java HotSpot(TM) 64-Bit Server VM (build 24.281-b32, mixed mode)
[oraapps@financials admin]$ echo $AF_CLASSPATH
/oracle/apps/R12_2/fs2/EBSapps/comn/util/jdk64/lib/dt.jar:/oracle/apps/R12_2/
fs2/EBSapps/comn/util/jdk64/lib/tools.jar:/oracle/apps/R12_2/fs2/EBSapps/
comn/util/jdk64/jre/lib/rt.jar:/oracle/apps/R12_2/fs2/EBSapps/comn/shared-
libs/ebs-3rdparty/WEB-INF/lib/ebs3rdpartyManifest.jar:/oracle/apps/R12_2/fs2/
FMW_Home/Oracle_EBS-app1/shared-libs/ebs-fmw/WEB-INF/lib/ebsFMWManifest.jar:/
oracle/apps/R12_2/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/oracle/apps/R12_2/fs2/FMW_Home/
oracle_common/modules/oracle.uix_11.1.1/uix2.jar:/oracle/apps/R12_2/fs2/
FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/oracle/apps/R12_2/
fs2/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrf-client.jar:/oracle/
apps/R12_2/fs2/EBSapps/comn/java/lib/cplex.jar:/oracle/apps/R12_2/fs2/
EBSapps/comn/java/classes

The CLASSPATH and AF_CLASSPATH environment variable must contain the necessary Java
7.0 libraries, which should include:

 [COMMON_TOP]/util/<Java7>/lib/dt.jar
 [COMMON_TOP]/util/<Java7>/lib/tools.jar
 [COMMON_TOP]/util/<Java7>/jre/lib/rt.jar

where <Java7> is the installation directory for the latest JDK 7.0 Update.

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.

Synchronize the Run File System and the Patch File System:
After the completion of the verification, both file systems need to be synchronized for the
changes of the newly installed Java 7.0 Uptake. Perform the following command:

UNIX:

$ adop phase=fs_clone

Upgrading to Latest JRE 7.0 on Database Tier Node:

Download Latest JRE 7.0 Update

Replace JRE Home Used with Oracle E-Business Suite Release 12.2:
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.

UNIX:

$ cd /backup/JRE170191
$ unzip p28740726_170191_Linux-x86-64.zip
$ tar -xvf jre-7u191-linux-x64.tar.gz
$ mv jre1.7.0_191/ jre
$ cd $ORACLE_HOME/appsutil
$ mv jre jre_02Nov2021
$ cd /backup/JRE170191
$ cp -RH jre $ORACLE_HOME/appsutil

Note:

 Do not use this procedure to upgrade the [ORACLE_HOME]/jdk/jre, which is used by

the Oracle database.
 If the database tier is just upgraded with the new certified version of Oracle database,
simply create a new directory under [ORACLE_HOME]/appsutil/jre.
 After replacing the old JRE install home with the new certified JRE Update, 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 JRE 7.0 Update on the
database tier.

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 (except Solaris 64-bit):

[oracle@erptest1 bin]$ ./java -version

java version "1.7.0_191"

Java(TM) SE Runtime Environment (build 1.7.0_191-b32)

Java HotSpot(TM) 64-Bit Server VM (build 24.191-b32, mixed mode)

[oracle@erptest1 bin]$