OAM 11gR2 PS3 Installation.

Today we are going to install OAM 11.1.2.3.0. The high level steps include:

 - Installing and Setting up DB
 - Running RCU
 - Installing Weblogic
 - Installing OAM

Before proceeding with the installation you must go through the certification matrix and acquire the compatible binaries from e-delivery. Also check the JDK version and use the certified jdk based on the OS you are using. I am going to focus on OAM installation and will not discuss DB installation.

DB post installation

OAM 11gR2 PS3 is only supported with Oracle DB. You will find many blogs and videos which explains step by step DB installation process. Post installation you need to alter below DB processes:

Login to sqlplus with a user having sysdba privileges and run below command

alter system set processes=500 scope=spfile;

alter system set open_cursors=1500 scope=spfile;

alter system set session_cached_cursors=500 scope=spfile;

alter system set session_max_open_files=50 scope=spfile;

alter system set aq_tm_processes=1 scope=spfile;

alter system set job_queue_processes=10 scope=spfile;

shut immediate;

startup;

These are the minimum configuration recommended by oracle. Later, when your environment is ready, you need to do a performance testing and fine tune your DB for maximum results.


Running RCU

For 11gR2 PS3 you need use the 11g Release 1 (11.1.1.9.0) version of the Oracle Fusion Middleware
Repository Creation Utility.

Unzip the binary and run 'rcu' located in rcuHome/bin

Fill in the connection details of DB instance.

 Give the preferred prefix and select 'Oracle Access Manager' and 'Oracle Mobile Security Manager'

You also need to select 'Oracle Mobile Security Manager' schema even if you just need Oracle Access Management. By default, Oracle Mobile Security Suite is installed with Oracle Access Management. 

By selecting Oracle Mobile Security Manager, the following schemas are also selected, by default:

– AS Common Schemas - Oracle Platform Security Services

– AS Common Schemas - Metadata Services

– AS Common Schemas - Audit Services

– Identity Management - Oracle Access Manager

If you manually select the Oracle Access Manager schema, then Oracle Mobile Security Manager schema will not be selected by default. In this case, you need to manually select the Oracle Mobile Security Manager schema because when you install and configure Oracle Access Management in a WebLogic domain, the Oracle Mobile Security Manager server is installed and configured in the domain by default.

Also note that if you are creating schemas for Oracle Identity Manager, Oracle Access Manager, and Oracle Adaptive Access Manager on the same database, then it is recommended to provide different schema prefixes to make sure that Oracle Platform Security Services and Metadata Services schemas are not shared. Else you will face issues at later stages.

 Set a password for these schemas and remember it, as it will be required at later stage. 

The schema has been created in the Database now we can proceed with weblogic installation.


Installing Weblogic

As of now only Oracle Weblogic Server 11gR1 (10.3.6) is supported for deploying OAM 11gR2 PS3. There are some document which says that weblogic 12c is certified with OAM but it simply means that you can protect any application deployed on 12c weblogic server but for OAM deployment you need weblogic 10.3.6. I am using generic weblogic 10.3.6 installer.

Fill the preferred path to Middleware home

Although you can install multiple products on the same Middleware home but it is recommended to use separate Middleware home for different products because when you will be installing second product some of the common file will be overwritten and this may lead to conflict when configuring the domain or upgrading your environment. As this is a test machine, I am going to use the same Middleware home for IDAM products suite but for production it is never recommended.

Select the certified jdk. I have seen some issues due to outdated jdk versions/libraries.

With this the weblogic installation is complete.

Installing OAM

Unzip the binaries and run 'runInstaller' located in Disk1 folder.

Check why prerequisites failed. In my case, I already have higher version of libraries.

Click Continue to proceed.

Specify the middleware home path created while installing weblogic.

With this we are done with OAM installation. Let us check the directory structure created till now.

In the next blog we are going to configure the OAM domain.

Thank you for reading.