The following guide shows how to install OAM 11.1.1.5 Bundle Patch 2 (Patch Number: 13115859). This patch addresses a login error relating to OAM and JavaScript failures, Oracle Bug 13254371 and Oracle Support article “1447194.1” explains how to resolve the error as well.

The primary issue was where a customer was when OAM tries to authenticate the user in any non-IE browser like Firefox, Chrome, and Safari, the customer gets the following message in the browser:

  • <body onLoad=”document.myForm.submit()”><noscript><p>JavaScript is required. Enable JavaScript to use OAM Server.</p></noscript>

JavaScript is enabled on the browsers, however the message keeps appearing. Installing Bundle Patch 2 for OAM 11.1.1.5, resolves the issue.

PATCH INSTALLATION

1.  Download OAM Patch

If you do not yet have BP02 Patch for OAM 11.1.1.5 (“p13115859_111150_Generic.zip”), please follow the instructions below to download the patch. Otherwise continue onto the next step.

1.  Go to http://support.oracle.com and login with your valid Oracle Support login credentials

2.  Open the “Patches & Updates” tab.

3.  Fill in “13115859” into the “Patch Number” field, then click the “Search” button.

4.  Click on patch “13115859” and click the “Download” button to download the file.

2.  Load and Unzip the OAM Patch onto Server’s File System

1.  Put the patch’s zip file in a short directory path like D:\OraclePatches…

2.  Unzip the patch so you have a file structure similar to D:\OraclePatches\13115859

3. Shutdown all OAM Fusion Middleware Servers

1.  Shutdown managed OAM Server

2.  Shutdown OAM WebGate (If necessary)

3.  Shutdown OAM Domain’s AdminServer

4. Backup RREG.tar.gz to a backup location

%OAM_ORACLE_HOME% = OAM Oracle Home.  The path can be something similar to: D:\Oracle\Middleware\Oracle_OAM

1.  Copy the file: “%ORACLE_HOME%/oam/server/rreg/client/RREG.tar.gz

2.  Create the following directory tree to store RREG.tar.gz: “%ORACLE_HOME%/backup/oam/server/rreg/client/RREG.tar.gz

5. Backup %OAM_DOMAIN_HOME% files

%OAM_DOMAIN_HOME% is the OAM WebLogic Domain Home. It should be something like “D:\Oracle\Middleware\user_projects\domains\oamdomain”.

1.  Navigate %OAM_Domain_Home%/config/fmwconfig/mbeans/oam

2.  Make a copy of the “config.jar” file with the filename “config.jar.13115859”

3.  Make a copy of the file “mapstore-coherence.jar” with the filename “mapstore-coherence.jar.13115859”

6. Backup %OAM_ORACLE_HOME% and %OAM_DOMAIN_HOME%

Take a complete file structure backup OAM’s ORACLE_HOME and DOMAIN_HOME.

%OAM_ORACLE HOME% can be “D:\Oracle\Middleware\Oracle_OAM”.

%OAM_DOMAIN_HOME% can be “D:\Oracle\Middleware\user_projects\domains\oamdomain”

7. Open Command Prompt

Open a command prompt window on the server.

8. Set environment variables within Command Prompt

1.  Set “ORACLE_HOME” to the absolute directory path of OAM’s %ORACLE_HOME%.
For example: set ORACLE_HOME=D:\Oracle\Middleware\Oracle_OAM

2.  Set “DOMAIN_HOME” to the absolute directory path of OAM’s %DOMAIN_HOME%.
For example: set DOMAIN_HOME= D:\Oracle\Middleware\user_projects\domains\oamdomain

9. Apply Patch via OPatch

1.  In command prompt, cd to the Patch Home, like the example below:
D:\OraclePatches\13115859

2.  Run the following command like in the example below:
D:\Oracle\Middleware\Oracle_OAM\OPatch\opatch apply -jdk D:\Java\jdk1.6.0_29

Allow a few minutes for the patch to install.

3.  You will see a warning at the end of the patch installation. This is no error. It is simply a warning stating BP01 patch has been patched over with BP02 patch.

4.  Leave the command prompt window open.

10.  Run the Script: domainAutomation

1.  Locate “domainAutomation” batch script in the BP02 Patch Folder. It is located in the following directory path: %PATCH_HOME%/13115859/files/oam/server/scripts/opatch

2.  Run the “domainAutomation.bat” script in the command prompt window.

3.  Leave the command prompt window open.

11.  Backup the oam-config

1.  Navigate to “%Domain_Home%/config/fmwconfig”

2.  Copy “oam-config.xml” to a file name “oam-config.xml.13115859”

12.  Startup OAM Domain’s AdminServer

Only startup OAM Domain’s Admin WebLogic Server

13.  Startup WLST from command prompt

1.  Cd to: %ORACLE_HOME%/common/bin.
For example: “D:\Oracle\Middleware\Oracle_OAM\common\bin”

2.  Run the script wlst

3.  Run the connect command: connect(‘%username%’,’%password’,’%host%:%AdminServer_port%’)
For example: connect(‘weblogic’,’Welcome1’,’localhost:7001’)

4.  After you connect, run the following command: patchUpgrade(path=”%OAM_ORACLE_HOME%”)
For example: patchUpgrade(path=” D:\Oracle\Middleware\Oracle_OAM”)
Allow a few seconds for the patch to install.

14.  Restart the OAM AdminServer

15.  Startup all remaining OAM servers

OAM Managed Server, OAM WebGate, etc…

After completing the steps above, please test your application.