1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

Upgrade JDK OC4J for Oracle Application Server 10.1.3

Discussion in 'General' started by mzainal, Aug 24, 2009.

  1. mzainal

    mzainal Forum Advisor

    Likes Received:
    Trophy Points:

    Now my OC4J running with jdk 1.5 update 11. I want to upgrade to update 19. My OC4J version Any doc that i can refer?

  2. apps_expert

    apps_expert Forum Expert

    Likes Received:
    Trophy Points:
    Chennai, India
    Yes please refer to Metalink Note no 396096.1.

    If you don't have metalink access, I have copied the note below:

    The JDK can be changed two ways:

    This approach replaces the $ORACLE_HOME/jdk location that is used by all Application Server components (including opmn, dmstool, all OC4J instances etc.)

    Per OC4J Instance
    In this scenario, the default JSDK is left untouched and a new JSDK location is created that can be used selectively with custom OC4J instances created after the initial Application Server install. This approach modifies the configuration of the Oracle Process Manager so that it uses a specific "java" executable when it starts a specified OC4J instance.

    The JSDK that is shipped within Application Server undergoes comprehensive testing during the product development and release cycles and this version is then "certified" as a version not found to present any known issues of significant impact or risk to customers adopting it. Wherever possible it is recommended to minimize against the possibility of introducing unknown risks by making as little change to the "certified" product as possible and for this reason changing the JSDK for specific OC4J instances should be preferred over the global approach.

    Before updating the JSDK it is also recommended that customers check the certification matrix for the Application Server in question and select a more recently certified JSDK possible, if possible. For a more detailed illustration of how to check under Metalink to see which JSDK versions have been certified, please see:

    Note 258833.1 - Determining which different JAVA versions are supported with Application Server Releases


    1. Changing the JSDK globally

    * First stop all running Application Server processes and rename the $ORACLE_HOME/jdk directory:
    $ cd ${ORACLE_HOME}
    $ mv jdk jdk.orig
    * Install the newer JSDK as per the installation instructions provided with it.

    For some vendor JSDK platforms and download types you may be able to select to install the desired JDK directly to $ORACLE_HOME/jdk. In other cases, it may be neccessary to first install it to a different location, such as /usr/jdk1.5.0_08, and later copy it to the $ORACLE_HOME/jdk location.

    Unlike with 9.0.4.x and 10.1.2.x, after the installation there are no additional files to copy from the original $ORACLE_HOMEjdk to the newly installed/copied $ORACLE_HOME/jdk.

    However, users running on AIX 5L platforms will need to apply additional known patches to any newly installed vendor JDK:

    1.5 5261515 AS10.1.3.X: PATCH OVER AIX5L JDK15
    1.4.2 5261519 AS10.1.3.X: ORACLE PATCH OVER JDK142

    On AIX you will have to clean up memory images of used classes before replacing the JDK. In order to do so execute the command "slibclean" as user "root".

    After downgrading the JDK to 1.4.2, customers on the AIX 5L platform will need to perform the following additional step after applying one of the above patches:

    % cd ${ORACLE_HOME}/j2ee/home/lib
    % cp crimson_1_1_3.jar ${JAVA14}/jre/lib/ext


    ${JAVA14} - represents the path to the newly installed JDK 1.4 directory

    2. Selectively changing the JSDK per OC4J instance

    o Backup the Oracle Process Manager configuration file ($ORACLE_HOME/opmn/conf/opmn.xml):
    $ cd $ORACLE_HOME/opmn/conf
    $ cp opmn.xml opmn.xml.safe
    o Using an appropriate text editor (e.g, vi, emacs, Notepad etc.), modify the "start-parameters" section for the desired OC4J instance and add a "java-bin" parameter that points to the the desired "java" executable.

    <ias-component id="OC4J">
    <process-type id="myOc4j" module-id="OC4J" status="enabled">

    <category id="start-parameters">
    <category id="start-parameters">
    <data id="java-bin" value="/usr/jdk1.5.0_08/bin/java"/>

    o After saving the changes to opmn.xml:
    + reload opmn, so that it re-reads it's configuration file:
    $ opmnctl reload
    + stop/start the desired OC4J instance so that it will be started using the modified "java" location:
    $ opmnctl stopproc-process-type=myOc4j
    $ opmnctl startproc-process-type=myOc4j

    For a more detailed example, please refer to the following product documentation:

    Oracle® Process Manager and Notification Server Administrator’s Guide 10g Release 3 (10.1.3)
    January 2006

    Chapter 8: Configuring OC4J
    "8.3 OC4J Complete Configuration", pages 8-1 through 8-3.