Issue installing pre-reqs for IAMSuite on Redhat Linux 6.5

Issue:
*****************************************************************
Check Name:Packages
Check Description:This is a prerequisite condition to test whether the packages recommended for installing the product are available on the system.
Checking for binutils-2.20.51.0.2-5.11.el6-x86_64; found binutils-2.20.51.0.2-5.36.el6-x86_64. Passed
Checking for compat-libcap1-1.10-1-x86_64; found compat-libcap1-1.10-1-x86_64. Passed
Checking for compat-libstdc++-33-3.2.3-69.el6-x86_64; found compat-libstdc++-33-3.2.3-69.el6-x86_64. Passed
Checking for compat-libstdc++-33-3.2.3-69.el6-i686; Not found. Failed <<<<
Checking for libgcc-4.4.4-13.el6-i686; found libgcc-4.4.7-4.el6-i686. Passed
Checking for libgcc-4.4.4-13.el6-x86_64; found libgcc-4.4.7-4.el6-x86_64. Passed
Checking for libstdc++-4.4.4-13.el6-x86_64; found libstdc++-4.4.7-4.el6-x86_64. Passed
Checking for libstdc++-4.4.4-13.el6-i686; Not found. Failed <<<<
Checking for libstdc++-devel-4.4.4-13.el6-x86_64; found libstdc++-devel-4.4.7-4.el6-x86_64. Passed
Checking for sysstat-9.0.4-11.el6-x86_64; found sysstat-9.0.4-22.el6-x86_64. Passed
Checking for gcc-4.4.4-13.el6-x86_64; found gcc-4.4.7-4.el6-x86_64. Passed
Checking for gcc-c++-4.4.4-13.el6-x86_64; found gcc-c++-4.4.7-4.el6-x86_64. Passed
Checking for glibc-2.12-1.7.el6-i686; found glibc-2.12-1.132.el6-i686. Passed
Checking for glibc-2.12-1.7.el6-x86_64; found glibc-2.12-1.132.el6-x86_64. Passed
Checking for glibc-devel-2.12-1.7.el6-x86_64; found glibc-devel-2.12-1.132.el6-x86_64. Passed
Checking for glibc-devel-2.12-1.7.el6; found glibc-devel-2.12-1.132.el6-x86_64. Passed
Checking for libaio-0.3.107-10.el6-x86_64; found libaio-0.3.107-10.el6-x86_64. Passed
Checking for libaio-devel-0.3.107-10.el6-x86_64; found libaio-devel-0.3.107-10.el6-x86_64. Passed
Check complete. The overall result of this check is: Failed <<<<
***********************************************************************

Workaround:
***********************************************************************
1.Perform a "yum search" for the failed packages
2.yum search compact-libstdc++
3.yum install compat-libstdc++-33.i686
4.Resolve dependency for "libstdc++-4.4.4-13.el6-i686" package
#yum search libstdc++
#yum install libstdc++-devel.i686
***********************************************************************

OAAM Advanced integration with OAM11gR2PS1 using TAP Steps

1. After starting OAAM Admin Server (startAdminOAAM.sh) and OAAM
Managed Server (startOAAM.sh), login as keith.warren/Oracle123 to OAAM
Admin Console (http://oam.example.com:14200/oaam_admin)
2. Restore a snapshot to upload OAAM data: goto Environment --> System
Snapshots and click on Load from File
3. Uncheck Back up current system now and click on Continue
4. Click on Continue again to confirm the non backup of the current system
configuration.
5. Click on Browse and select oaam_base_snapshot.zip from
/app/u01/middleware/Oracle_IDM1/oaam/init
6. Click on Load
7. Click on Restore
8. Create a directory where you will store the Keystore file
9.Connect using WLST to Admin Server
 cd /app/u01/middleware/Oracle_IDM1/common/bin
 ./wlst.sh
 connect()
 username : weblogic
 password : Oracle123
 server URL : t3://oam.example.com:7001
10.Register OAAM as Thirdparty TAP Partner using the following command :
? registerThirdPartyTAPPartner(partnerName = "OAAMTAPPartner",
keystoreLocation =
"/app/u01/middleware/keystore/TAP_OAAM_OAM/TAPkeystore.jks" ,
password="Oracle123", tapTokenVersion="v2.0",
tapScheme="TAPScheme",
tapRedirectUrl="http://oam.example.com:14300/oaam_server/oamLogin
Page.jsp")
11. Update in the OAM Console the TAPScheme to have challenge parameter
MatchLDAPAttribute=uid as we are using UID as login attribute in our
deployment (Policy Configuration --> TAPScheme
12. Update the IAMSuiteAgent's profile and set Access Client Password to
Oracle123 (System Configuration --> Access Manager --> SSO Agents -->
OAM Agents --> Search and Edit IAMSuiteAgent)
13. As we have updated IAMSuiteAgent's password, we need to update
IAMSuiteAgent provider in Weblogic Security Realms with the same
Oracle123 password (WLS Console --> Security Realms --> myrealm -->
Providers --> IAMSuiteAgent --> Provider Specific --> Agent Password)
14. Copy the cli directory to a temporary location (for example /app/u05/tmp)
from /app/u01/middleware/Oracle_IDM1/oaam:
15.Copy the config file oaam_cli.properties from ~/labs that has been updated for
you reflecting the environment: cp ~/labs/oaam_cli.properties
/app/u05/tmp/cli/conf/bharosa_properties/
16.For your information here are the parameters that have been updated in the
configuration file template. 
17. To setup TAP integration with OAM, execute the script
setupOAMTapIntegration.sh and provide all requested information:
export ORACLE_MW_HOME=/app/u01/middleware
export JAVA_HOME=/app/u01/jdk1.6.0_33
cd /app/u05/tmp/cli
chmod +x setupOAMTapIntegration.sh
chmod +x findjar.sh
export PATH=$PATH:.
./setupOAMTapIntegration.sh
/app/u05/tmp/cli/conf/bharosa_properties/oaam_cli.properties
Default value for Weblogic Server Home Directory: press Enter (wait few
seconds)
OAAM AdminServer User Name: weblogic
OAAM AdminServer Password: Oracle123
OAAM DB User name: DEV_OAAM
OAAM DB User password: Oracle123
OAM WebGate credentials to stored in the CSF: Oracle123
OAM TAP Key store file password: Oracle123
18. Successful message should be: SetupOAMIntegration script ran successfully
19. Restart OAM Admin Server (startAdminOAM.sh), OAM Server (startOAM.sh)
and OAAM Server (startOAAM.sh)
20. Login to the OAM admin console and change Authentication Scheme to
TAPScheme for webgate11g_1 Protected Resource Policy
21. Check that you are prompted for credentials using the OAAM authenticator
when accessing http://oam.example.com:7777
22. Notice that you are redirected to http://oam.example.com:14300/oaam_server
which is OAAM managed server for authentication. Enter user.4 and click on
Continue.
23.The TextPad OAAM device is used for getting the password
24. Don't go through the registration steps clicking on Skip
25.You should see the OHS default welcome page.
26.Have a look to the cookies that have been created

Decoder and Encoder Tool

JWT Decoder(JWT Token Decoder)

https://developers.google.com/wallet/digital/docs/jwtdecoder

Base64 Encoder

http://www.base64encode.org/

RCU-6107:DB Init Param Prerequisite failure for:OPEN_CURSORS in Oracle Identity Management 11gR2 RCU Utility

Error info:

Workaround:

1. Login on your database.

  o Use the system user.

2. Execute the next command to validate the current value for the OPEN_CURSORS.

  o SHOW PARAMETERS OPEN_CURSORS

3. If its value is less than 800 then write the following command.

  o ALTER SYSTEM SET OPEN_CURSORS=500 SCOPE=SPFILE;

4. Restart your Database.

5. Start the RCU and try now.

http://mhabib.wordpress.com/2010/07/20/rcu6107-db-init-param-error/

Oracle Unified Directory (OUD) 11g installation and Configuration memo

OUD download Location:

http://www.oracle.com/technetwork/middleware/id-mgmt/oid-11g-161194.html
or
https://edelivery.oracle.com

1. Installation Steps:
1.1 Run the following command:
Linux
<download-path>/oud/Disk1/runInstaller -jreLoc JAVA_HOME

Windows x64:
Double click <download-path>\oud\Disk1\install\win64\setup.exe

1.2 On Welcome page, click Next.
1.3 Select 'Skip update software', and click Next
1.4 Specify installing directory and click Next
1.5 Click Install and Click Next
1.6 Click Finish.

2. Setup Directory Server
2.1 <install-path>/Oracle_OUD1/oud-setup
2.2 On the Welcome page, click Next
2.3 Setup the server info and click Next
2.4 Select stand alone server and click Next
2.5 Specify the root entry name and select import sample data, then click Next
2.6 Click Close

003 Setup Proxy Server without configure
3.1. Run the following command:
<install-path>/Oracle_OUD1/oud-proxy-setup
3.2. On Welcome page, click Next
3.3. Specify Server info, and click Next
3.4. Select configure later and click Next
3.5. Click Next

004 Install & Configure ODSM
4.1. Install WLS
4.2. Install Application Development Framework
Note: You must install the Oracle Application Development Framework as the same user who installed OUD.
Note: The Middleware Home directory must be the same directory as the OUD Base Location Home that you defined when you installed OUD.
4.3. Create EM and ODSM WLS domain
4.4. Select EM and ODSM domain source

OUD:
Chinese topic
http://fusionmiddleware11g.wordpress.com/2012/11/26/oud-11g-r2/