Skip to main content

Running Design Console - OIM 11gR2

  • After completing the OIM 11g R2 Installation design console can be run from the location <Middleware_home>/Oracle_IDM1/designconsole/xlclient.sh.
  • Before running the designconsole some of the post installation steps need to be completed.
  • Navigate to <Middleware_home>/wlserver_10.3/server/lib and Create wlfullclient.jar by running ‘java -jar wljarbuilder.jar’ command.
  • copy the wlfullclient.jar file to the <Middleware_home>/Oracle_IDM1/designconsole/ext directory.
  • Navigate to <Middleware_home>/Oracle_IDM1/designconsole/config folder and update xlconfig.xml file with right URL's.
  • update below values:                           <appServerName>weblogic</appServerName>                                                         <ApplicationURL>http://<OIM_Host>:14000/xlWebApp/loginWorkflowRenderer.do</ApplicationURL>                                                                                                  <java.naming.provider.url>t3://<OIM_Host>:14000/oim</java.naming.provider.url><java.naming.factory.initial>weblogic.jndi.WLInitialContextFactory</java.naming.factory.initial>

  • Navigate to <Middleware_home>/Oracle_IDM1/designconsole and update xlconfig.sh file.                                                                                                                    Change "-Djava.security.manager -Djava.security.auth.login.config=config/auth.conf \" to "-Djava.security.manager -Djava.security.auth.login.config=config/authwl.conf \.
    "
  • Now login with the Administrator account.
     

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.