Oracle Access Management 12.2.1.4.210816 BP includes the following new features and enhancements:

• Two-way SSL for OAP over REST Communication.

  You can enable mutual authentication for OAP over REST between WebGate and OAM Server, therefore ensuring that the Server communicates with authentic clients.

  For details, see Enabling two-way SSL for OAP over REST.

Describes Bundle Patches and explains differences between Bundle Patches, patch set exceptions (also known as one-offs), and patch sets.

A bundle patch is an official Oracle patch for Oracle Access Management components on baseline platforms. In a bundle patch release string, the fifth digit indicated the bundle patch number. Effective November 2015, the version numbering format has changed. The new format replaces the numeric fifth digit of the bundle version with a release date in the form "YYMMDD" where:

• YY is the last 2 digits of the year

• MM is the numeric month (2 digits)

• DD is the numeric day of the month (2 digits)

Each bundle patch includes the libraries and files that have been rebuilt to implement one or more fixes. All of the fixes in the bundle patch have been tested and are certified to work with one another.

Each bundle patch is cumulative: the latest bundle patch includes all fixes in earlier bundle patches for the same release and platform. Fixes delivered in bundle patches are rolled into the next release.

Bundle patches are released on a regular basis and are available on My Oracle Support (formerly Oracle MetaLink).

Oracle recommends that you apply the WebGate bundle patch to all installed WebGates for which a bundle patch is provided.

1. Ensure that your system configuration is at the appropriate level:

   • Access Manager 12.2.1.4.0

   • Supported Operating System

   • Supported Web server release and type

2. Confirm that any currently installed bundle patch level is lower than the one you intend to install.
3. There is no need to remove an earlier bundle patch before installing a later one.
4. Windows 64-bit OS: See Preparing 64-Bit Oracle HTTP Server 12c WebGates on Windows 64-Bit Platforms

   Note:

   If your system configuration does not meet support requirements, or if you are not certain that your system configuration meets these requirements, Oracle recommends that you log an Service Request to get assistance with this bundle patch. Oracle Support will make a determination about whether you should apply this bundle patch or not.
5. Following pre-requisites are needed for Oracle HTTP Server(OHS) and Oracle Traffic Director(OTD) WebGates:
   1. Download DB Client Installer patch: 34761383 and install DB Client by following the instruction in the readme.txt of 34761383.
   2. Apply OSS Bundle Patch:37096063.
   3. Apply OHS Bundle Patch:37033394 or OTD Bundle Patch:34380114 according to middleware home.
   4. If you apply OHS Bundle Patch:37033394 for the HPUX operating system, you will also be required to apply the one-off patch 37204850.
   5. Apply DB Client patch 36615359 for all operating systems. If the operating system is AIX,then apply DB client one-off patch 34976606 also.
6. Minimum OS version required for WebGate is OEL 7.

This section contains the following topics to guide you, as you prepare and install the WebGate files (or as you remove a WebGate, should you need to revert to your original installation):

This section introduces the Oracle patch mechanism (Opatch) and requirements that must be met before applying the bundle patch. Opatch is a Java-based utility that runs on all supported operating systems and requires installation of the Oracle Universal Installer.

1. Download the latest Opatch version.

   • Log in to My Oracle Support: https://support.oracle.com/

   Note:

   Use opatch -version to check if your Opatch version is the latest. If it is an earlier version of Opatch, download the latest version.
2. Confirm and add required executables to your system PATH:

   • Check your $ORACLE_HOME to confirm that it is pointing to the right Webgate$ORACLE_HOME.

   • Confirm the required executables are in your system PATH, and add these if needed:

     which opatch

     which unzip

   To add the required executables to your system path, you need to add the path of Opatch in PATH variable using the following: 

   export PATH=$ORACLE_HOME/OPatch:$PATH
3. Verify the OUI Inventory using one of the following commands:
   opatch lsinventory

   or

   opatch lsinventory -jdk [Path to jdk8]

   If an error occurs, contact Oracle Support and work to validate and verify the inventory setup before proceeding.

4. On the machine that will host the bundle patch files, create a directory to store the unzipped patch (referenced later as PATCH_TOP). For example:

   Linux: /home/12.2.1.4.0/tmp

   Windows: C:\12.2.1.4.0\tmp

5. Retrieve the Bundle Patch:

   • From My Oracle Support, click the Patches & Updates link.

   • Enter the Patch ID or Number, then click Search to display a Patch Search Results table.

   • Using the Release and Platform columns, find the desired patch, then click the associated Patch ID.

   • Download: In the page that appears, click the Download button to retrieve the packages.

6. Unzip the patch zip file into the PATCH_TOP directory you created earlier. For example:
   unzip -d PATCH_TOP p37078094_122140_platform.zip
7. Proceed as needed for your environment:

   Preparing 64-Bit Oracle HTTP Server 12c WebGates on Windows 64-Bit Platforms

   Installing a WebGate Bundle Patch on Any Platform

If you are using Windows 64-bit operating systems, you must install updated Microsoft Visual C++ 2012 libraries on the machine hosting the Oracle HTTP Server 12c WebGate for Oracle Access Manager.

To install Microsoft Visual C++ 2012 Redistributable Package (x64)

Install the Microsoft Visual C++ 2012 Redistributable Package (x64) for x64 systems, which can be downloaded from the following web site:

https://www.microsoft.com/en-us/download/details.aspx?id=30679

Proceed to Installing a WebGate Bundle Patch on Any Platform

This section describes how to install WebGate bundle patches on any platform using Oracle patch (Opatch). While individual command syntax might differ depending on your platform, the overall procedure is the same for all platforms.

1. Before applying the bundle patch stop the node manager and OHS component.
2. Complete all activities in Preparing All Environments and Downloading the Bundle Patch
3. Finish preparing your deployment using one of the following topics, as needed:

   Preparing 64-Bit Oracle HTTP Server 12c WebGates on Windows 64-Bit Platforms

4. Log in as the same user who installed the base WebGate and:

   • Turn off the Web server associated with the protected application.

   • Back up your ORACLE_HOME.

   • Move the backup directory to another location and record this so you can locate it later, if needed.

5. Set your current directory to the directory where the patch is located. For example:
   cd PATCH_TOP/37078094
6. Use one of the following Opatch commands to apply the patch to your ORACLE_HOME:
   opatch apply

   or

   opatch apply -jdk [Path to jdk8]

7. Restart the Web server.

If there is a failure during your WebGate installation, your original WebGate installation is restored automatically.

1. Perform all steps in Preparing All Environments and Downloading the Bundle Patch to verify the inventory, set any environment variables, shut down any services running from the ORACLE_HOME or host machine.
2. Stop the WebGate Web server, and change to the directory where the patch was unzipped. For example:
   cd PATCH_TOP/37078094
3. Back up the ORACLE_HOME directory that includes the bundle patch and move the backup to another location so you can locate it later, if needed.
4. Run Opatch to roll back the patch. For example:
   opatch rollback -id 37078094

   or

   opatch rollback -id 37078094 -jdk PathtoJDK8
5. Start the WebGate Web server.

This Bundle Patch provides the fixes described in the below section:

This section describes the documentation that is available to support the latest bundle patch and the original release. This section provides the following topics:

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology.