I'm making the assumption that you already have the database installed. If not, here's a quick link on HOW TO: Install Oracle Database 11.2.0.x on Linux 64bit.
Step 1: Download
If you're reading this and you want to install Oracle Identity and Access Management 11g Release 2 (11.1.2.2), specifically OAM 11gR2PS2, then you need to install Oracle Identity and Access Management Release 2 (11.1.2.1) THEN patch that version to get to OAM 11g R2 PS2. Sadly, Oracle does not provide OIM 11gR2PS2 as a single, distributed package from My Oracle Support (or from their cloud services). No idea why they've done this though in order to install OAM 11gR2 PS2, you need to install OAM 11gR2 then perform a 'patch update'. (WHY ORACLE, WHY!?!)
If you don't believe me, check it out here
So in order to install OAM 11gR2, you will need to following:
- For Oracle Identity and Access Management 11g (11.1.2.0.0), go to the Oracle Software Delivery Cloud and download V33644-01_1of2 and V33644-01_2of2
- For Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.9.0) go to V75907-01, which can be downloaded from the Oracle support cloud
Step 2: RCU
Go ahead and start the installation of the RCU by following the link, HOW TO: Install Oracle RCU 11.1.1.5. This step is pretty much the same process. The only difference is that you need install 11.1.1.9 to select Oracle Access Manager and not Oracle Identity Manager in step 2.
Step 3: Install Weblogic 10.3.6
There's the link on HOW TO: Install Weblogic 10.3.6.
Step 4: Install the Identity Management
The fusion middleware Identity and Access Management 11g package you download needs to be extracted into one folder then executed. The installation for OAM is pretty much the same process as the HOW TO: Install OIM (11gR2) 11.1.2.0 on Linux 64bit post that was made earlier
Step 5: Configure the Access Management
Sadly I decided to remove the screenshot though rest assure it's pretty much like installing OIM. Click here on how to configure your domain.
Step 6: OPSS Configuration
Once you've installed and configured OAM, you then perform WLS 10.3.6 - Configure Database Security Store
The full script in question is as follows:
/home/oracle/Oracle/OAM11gR2PS2/oracle_common/common/bin/wlst.sh /home/oracle/Oracle/OAM11gR2PS2/Oracle_IDM1/common/tools/configureSecurityStore.py -d /home/oracle/Oracle/OAM11gR2PS2/user_projects/domains/oam_domain/ -c IAM -p Password1 -m create
Once you've executed the script,
Credential with map Oracle-IAM-Security-Store-Diagnostics key Test-Cred stored successfully!
Credential for map Oracle-IAM-Security-Store-Diagnostics and key Test-Cred is: GenericCredential
Info: diagnostic credential created in the credential store.
Info: Create operation has completed successfully.
Further information on how to configure Weblogic for OAM can be located here: WLS 10.3.6 - Configure Database Security Store
Step 7: Upgrade from OAM 11gR1 to OAM11gR1PS2
As mentioned, you need to install OAM 11gR1 in order to install OAM11gR1PS2. A useful oracle document can be located here. The steps are fairly similar to the actual installation though the only difference is that you point to the existing middleware home for OAM 11gR1. The installer will acknowledge that an existing middleware deployment already exists and therefore provide you an option on whether or not to upgrade. Here is the link to download RCU 11.1.2.2. The database schema upgrade is also required as part of the OAM 11gR1PS2 installation.
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...