Google Search

Sunday, April 26, 2015

Configure OID as User Identity Store for OAM 11G R2 PS2

OAM’s default user store is weblogic’s embedded ldap server which is not a recommended user store for production environment.

After OAM installation it is suggested to set Oracle Internet Directory as OAM’s primary identity store.

Steps to configure OAM to use OID as Identity Store:

1. Create a group called “Administrators” in OID under dc= <your_domain>, cn=groups using ODSM
2. Create a user in OID under dc= <your_domain>, cn=users (This user will be used to connect to login to oam console)
3. Add this user to the “Administrator” group in OID. Use ODSM to create user/group in OID 11g
4. Login to OAM Console (http://server:7001/oamconsole where 7001 is Weblogic admin server port on which OAM is deployed)
5. Click tab “System Configuration” and select User Identity Stores under Data Source
6. From Actions -> select Create
7. Specify OID server location and credentials along with Users and Groups search base and click on Test Connections
8. Click Apply when connection is successful
9. Select newly created User Store from OAM Console and click “Set as System Store”. Also select “Set as Default Store”
10. Add the group Administrator that was created in OID to this Identity Store which will make users under this group to act as ‘admin’ for OAM. Click Apply.
11. In OAM console under System Configuration tab, go to Access Manager->Authentication modules–> LDAP Authentication Module.
Double click LDAP and change identity store to the New System Store value–> Click Apply

12. Log out from OAM console and login using newly created user in OID

ORA-00020 maximum number of processes exceeded

Cause: All process state objects are in use.
Action: Increase the value of the PROCESSES initialization parameter.

ORA-00020 comes under "Oracle Database Server Messages". These messages are generated by the Oracle database server when running any Oracle program.

Reference: Oracle Documentation

How to increase PROCESSES initialization parameter:

1.    Login as sysdba
    sqlplus / as sysdba
   
2. Check Current Setting of Parameters
    sql> show parameter sessions
    sql> show parameter processes
    sql> show parameter transactions

3.    If you are planning to increase "PROCESSES" parameter you should also plan to increase "sessions and "transactions" parameters

    A basic formula for determining  these parameter values is as follows:
   
        processes=x
        sessions=x*1.1+5
        transactions=sessions*1.1
       
4.    These paramters can't be modified in memory. You have to modify the spfile only (scope=spfile) and bounce the instance.
    sql> alter system set processes=500 scope=spfile;
    sql> alter system set sessions=555 scope=spfile;
    sql> alter system set transactions=610 scope=spfile;
    sql> shutdown abort
    sql> startup