Oracle Identity Manager Component Characteristics

8-152 Oracle Fusion Middleware High Availability Guide Figure 8–16 Oracle Identity Manager Component Architecture

8.9.1.1 Oracle Identity Manager Component Characteristics

Oracle Identity Manager Server is Oracles self-contained, standalone identity management solution, based on Java EE standards. It provides User Administration, Workflow and Policy, Password Management, Audit and Compliance Management, User Provisioning and Organization and Role Management functionalities. Oracle Identity Manager is a standard Java EE application that is deployed on Oracle WebLogic Sever and uses a database to store runtime and configuration data. The MDS schema contains configuration information; the runtime and user information is stored in the OIM schema. Oracle Identity Manager connects to the SOA managed servers over RMI to invoke the SOA EJBs. Oracle Identity Manager uses the human workflow module of the Oracle SOA Suite for managing its request workflow. Oracle Identity Manager connects to SOA using SOA Soapurl for connecting to SOA web services. This is the front end URL for SOA; this should be the load balancer or webserver URL in case of clustered SOA servers. When the workflow is completed, SOA calls back Oracle Identity Manager web services using OIMFrontEndURL. Oracle SOA is deployed along with the Oracle Identity Manager. Several Oracle Identity Manager modules use JMS queues. Each queue is processed by a separate Message Driven Bean MDB, which is also part of the Oracle Identity WebLogic Server: OIM UI Component SPML Web Service SOA Soapurl Remote Manager BI Publisher OVD OAM OIM SOA MDS Oracle Database OimFrontEndURL SPML Callback Web Service OimFrontEndURL Policy Config URL SPML CLIENT Browser Design Console SOA BIPublisherURL LDAP URL OAM ssoConfig SOA Rmiurl SOA Callback Web Service OimFrontEndURL OIM Engine MDBs Scheduler OES JMS Queues Message Producer Configuring High Availability for Identity Management Components 8-153 Manager application. Message producers are also part of the Oracle Identity Manager application. Oracle Identity Manager uses embedded Oracle Entitlements Server microkernel, which is also part of the Oracle Identity Manager engine. Oracle Entitlements Server OES is used for authorization checks inside Oracle Identity Manager. For example, one of the policy constraints determines that only users with certain roles are allowed create users. This is defined using the Oracle Identity Manager user interface. Oracle Identity Manager uses a Quartz based scheduler for scheduled activities. There are various scheduled activities that happen in the background. For example, one of the scheduled tasks is to disable users after the end date of the users. Oracle Identity Manager simply links to Oracle BI Publisher for all the reporting features. BI Publisher is expected to be in a different domain or same domain, so the integration is only a simple static URL integration. There is no interaction between BI Publisher and Oracle Identity Manager runtime components. BI Publisher is configured to use the same OIM database schema for reporting purposes. When you enable LDAPSync to communicate directly with external Directory Servers such as Oracle Internet Directory, ODSEE, and Microsoft Active Directory, support for high availabilityfailover features requires that you configure the Identity Virtualization Library libOVD. To configure libOVD, use the WLST command addLDAPHost. To manage libOVD, see Managing Identity Virtualization Library libOVD Adapters in the guide Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager for a list of WLST commands.

8.9.1.2 Runtime Processes