Saturday, January 24, 2009

Upgrade J2SE Version 5.0 in Oracle Applications

J2SE 1.4 is no longer supported in Oracle Apps.The minimum supported version is JDK 1.5. Please note that The Java 2 SDK, Standard Edition (J2SE) was previously referred to as the Java Development Kit (JDK)

Pre-req

Oracle E-Business Suite 11.5.10 CU1 or higher

134MB Disk space for Solaris 9 OS 32 bit sparc

Downloading J2SE 1.5

Download Java SE Development Kit 5.0u17 for Solaris SPARC, Multi-language from the sun site
http://java.sun.com/j2se/1.5.0/download.jsp 

Java Development Kit 5.0 Update 17-->jdk-1_5_0_17-solaris-sparcv.tar.Z

Installing J2SE 1.5

Extract in a directory on the server (say /usr/patches). Execute the following steps using "root" user

-->zcat jdk-1_5_017-solaris-sparc.tar.Z | tar -xf -

Just make sure you do have any earlier 5.0 package installation of JDK.If it is there use pkgrm to remove the packages first.

Now we will install the packages->

-->pkgadd -d . SUNWj5rt SUNWj5dev SUNWj5cfg SUNWj5man SUNWj5dmo

It will give the following prompt-->

Processing package instance <SUNWj5rt> from </usr/patches>

JDK 5.0 Runtime Env. (1.5.0_17)
(sparc) 1.5.0,REV=2004.12.07.00.07
Copyright 2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Using </usr> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user permission during the process of installing this package.

-->Do you want to continue with the installation of <SUNWj5rt> [y,n,?] y

Enter "y" above to continue

Verify the java version

By default jdk 1.5, referred as  $JDK50_TOP will be installed in "/usr/jdk/instances/jdk1.5.0"

cd $JDK50_TOP/bin

java -version

The following confirms that j2se 1.5 is installed correctly->
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Server VM (build 1.5.0_17-b04, mixed mode)

Make J2SE 5.0 to be default on Solaris 9

In Solaris 9-->make JDK 5.0 the default Java platform by modifying the /usr/java symbolic link to point to /usr/jdk/instances/jdk1.5.0 by

-->ln -s /usr/jdk/instances/jdk1.5.0 java

Steps for Oracle Apps

Now following the Oracle metalink note 304099.1- "Using J2SE Version 5.0 with Oracle E-Business Suite 11i"

-->Step 1: Stop all Application Tier Server Processes

-->Step 2: Obtain and Install JInitiator 1.3.1

-Ignored as we already upgraded to JRE1.6.0_06

-->Step 3: Obtain TXK AutoConfig Template Rollup Patch 6372396

-Ignored as it we are already on 11.5.10.CU2

-->Step 4: Obtain J2SE 5.0 Consolidated Patch 4372996 and other EBS Interoperability Patch(es) --Apply patch 4372996

If you are using Oracle Field Service, apply Field Service (CSF) interoperability patch, Patch 5372210-skipped

If you are using Scheduler, please apply the following patch(es);

· 11.5.10CU2 users should also apply Patch 5680223-skipped

· 11.5.10CU1 users should also apply Patch 5281664 as a pre-req to Patch 5680223-skipped

-->Step 1: Execute the J2SE 5.0 Upgrade Script to Update Configuration Files

cd $FND_TOP/bin

txkrun.pl -script=SetJDKCfg -contextfile=$CONTEXT_FILE -runautoconfig=Yes -appspass=<APPS_schema_passwd> -jdktop=[JDK50_TOP]

This will update the configuration files and run autoconfig

-->Step 2: Regenerate the appsborg2.zip File & Product JAR Files

This step must be repeated for each [APPL_TOP]

$APPL_TOP/APPS<CONTEXT_NAME>.env

Run AD Administration, and choose "Generate Product JAR Files" and then "Generate Applications Files" menu to update appsborg2.zip to include the new JDBC Drivers for the J2SE 5.0 library (jdbc14.zip) and to generate the product JAR files.

-->Step 3: Restart all Application Tier Server Processes

cd $COMMON_TOP/admin/scripts/<CONTEXT_NAME>

adstrtal.sh <APPS username/APPS password>

Testing Applications

-->Section 4: Verify the Application Tier Node Configurations

-->Step 1: Verify Installations on all Web Server Nodes

Follow these steps to verify that J2SE 5.0 has been successfully installed on all the Web Server node(s):

Run the AOL/J test page from a web browser, using the URL:

http://[web server]:[port]/OA_HTML/jsp/fnd/aoljtest.jsp

Now, To create a simple J2SE test page (without logging in to the Oracle E-Business Suite database), proceed with the follows:

  1. Change to the OA_HTML directory on the Web server.
  2. Using a text editor, create a file called J2SEtest.jsp with the following lines:

The J2SE version is:<%= System.getProperty("java.version") %>
<p> </p>
The class path is:<%= System.getProperty("java.class.path") %>

  1. Access this JSP from a web browser, using the URL:

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

The version should display "1.5.0_17". Also verify whether the necessary J2SE 5.0 libraries (i.e.[JDK50_TOP]/lib/dt.jar, [JDK50_TOP]/lib/tools.jar, [JDK50_TOP]/jre/lib/rt.jar, and [JDK50_TOP]/jre/lib/charsets.jar) are included in the CLASSPATH

-->Step 2: Verify Configurations on all Application Tier Nodes

Follow these steps to determine that J2SE 5.0 is running on all the application tier nodes:

1. 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 J2SE 5.0 executable. The CLASSPATH and AF_CLASSPATH environment variables must contain the necessary J2SE 5.0 libraries.

Note: If the AD utilities have not been upgraded to use J2SE 5.0, do not run $ADJVAPRG -version and echo $CLASSPATH

2. $ADJVAPRG -version

$AFJVAPRG -version

The above will display->
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Server VM (build 1.5.0_17-b04, mixed mode)

echo $CLASSPATH
echo $AF_CLASSPATH

3. Log in to the Oracle Applications and select the "System Administrator" responsibility. Check the Concurrent/Manager/Administer form and make sure all managers have the corresponding numbers for their actual and target.Run the "Active Users" concurrent request.