Skip to main content

High Level steps to install OIM 11g R2 PS1

1.      Install Oracle DB.
2.      Run rcu 11.1.2.1 and create schema in the database.
3.      Install Weblogic Middleware home.
4.      Install 11.1.1.6 SOA server in the Middleware.
5.      Download and Install IAM 11.1.2.1 suite in the Middleware.
6.      Install SOA patches number 16385074, 13973356, 16024267, 14196234, 16366204 on the SOA home (<Middleware_home>/Oracle_SOA1)
7.      Run config.sh script from <Middleware_home>/oracle_common/common/bin and create a domain for OIM.
8.      Install IAM Patch number 16400771 on oracle common home (<Middleware_home>/oracle_common)
9.      Install IAM Patch 16513008 on Oracle IAM home (<Middleware_home>/Oracle_IDM)
10. There are some other patches also for specific bugs and requirement. This can be checked with below link:-
11. Create wlfullclient.jar by running ‘java -jar wljarbuilder.jar’ in <Middleware_home>/wlserver_10.3/server/lib.
12.  Run OIM config from <Middleware_home>/Oracle_IDM1/bin and provide the admin user name and password and do the LDAP sync if desired.
13.  Create the Database credential store by running the following command:
<MW_HOME>/oracle_common/common/bin/wlst.sh <IAM_HOME>/common/tools/configureSecurityStore.py -d <domaindir> -c IAM -p <opss_schema_password> -m create
If IAM components are configured in 2 different domains then Cred store is created with the first domain and other domains are joined with existing credential store.

14. To run the design console copy the wlfullclient jar created above in <ORACLE_IAM_HOME>/designconsole/ext.

Comments

Popular posts from this blog

Developing Prepopulate Adapter with OIM 11g R2

1.      Prepopulate Adapter in OIM uses the plugin point oracle.iam.request.plugins.PrePopulationAdapte r. 2.      Write the Java code which returns the value which has to be populated on the form. 3.      This code will implement the plugin point oracle.iam.request.plugins.PrePopulationAdapte r. Code Snippet: - package com.oracle.oim.utility.eventhandler; import java.io.Serializable; import java.util.Iterator; import java.util.List; import java.util.logging.Logger; import oracle.iam.identity.exception.NoSuchUserException; import oracle.iam.identity.exception.UserLookupException; import oracle.iam.identity.usermgmt.api.UserManager; import oracle.iam.identity.usermgmt.vo.User; import oracle.iam.platform.Platform; import oracle.iam.platform.authz.exception.AccessDeniedException; import oracle.iam.request.exception.RequestServiceException; import oracle.iam.request.vo.Beneficiary; import oracle.iam.request.vo.RequestData; public c

OIM Tuning

Application Module tuning is a critical setting which will affect the UI performance. Following are the recommended application module settings for OIM and these are already set out-of-box (OOB) in later releases of OIM 11g R2. Ensure that these settings are implemented as recommended in your environment. -Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1 -Djbo.ampool.maxavailablesize=120 -Djbo.recyclethreshold=60 - Djbo.ampool.timetolive=-1 -Djbo.load.components.lazily=true - Djbo.doconnectionpooling=true -Djbo.txn.disconnect_level=1 - Djbo.connectfailover=false -Djbo.max.cursors=5 - Doracle.jdbc.implicitStatementCacheSize=5 - Doracle.jdbc.maxCachedBufferSize=19 open DOMAIN_HOME/bin/setDomainEnv.sh file for the WebLogic Server instance.find these lines: JAVA_OPTIONS="${JAVA_OPTIONS}" export JAVA_OPTIONS and change it to: JAVA_OPTIONS="-Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1 -Djbo.ampool.maxavailablesize=120 -D

What is Application Instance

Application instance is a provisionable entity. It is a combination of IT resource instance (target connectivity and connector configuration) and resource object (provisioning mechanism) . Creating and managing application instances are performed by using the Oracle Identity System Administration. Once Created Application Instance can be requested from the catalog. Application instances can be connected or disconnected.  Connected application  instance -It has a connector defined for the provisioning of entities. Account is created in the target system real time in case of connected Application Instance. Disconnected  application instance - It is used for the provisioning of a disconnected resource, for which  a connector is not defined, and therefore, the provisioning is performed manually by the administrator. A mail trigger system can also be attached which sends the account creation/modification/deletion mails to the application owner.