Runtime Processes Component and Process Lifecycle

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

Oracle Identity Manager is a Java EE application that is deployed on Oracle WebLogic Server as a no stage application. The Oracle Identity Manager server is initialized when the WebLogic Server it is deployed on starts up. As part of the application initialization, the quartz based scheduler is also started. Once initialization is done, the system is ready to receive requests from clients. Remote Manager and Design Console need to be started as standalone utilities separately.

8.9.1.3 Component and Process Lifecycle

Oracle Identity Manager is deployed to an Oracle WebLogic Server as an externally managed application. By default, the Oracle WebLogic Server starts, stops, monitors and manages other lifecycle events for the Oracle Identity Manager application. Oracle Identity Manager is a standard Java EE application, and it starts up after the application server components have been started up. Also Oracle Identity Manager uses the authenticator which is part of the Oracle Identity Manager component mechanism; it starts up before the WebLogic JNDI are initialized and the application is started. This is loaded from the OIM ORACLE_HOME. Oracle Identity Manager uses a Quartz technology-based scheduler. Quartz starts the scheduler thread on all the WebLogic Server instances. It uses the database as the centralized storage for picking and executing the scheduled activities. If one of the scheduler instances picks up a job, the other instances will not pick up that same job. Oracle Identity Manager caches certain system configuration values in the cache in memory of the server instance from the database. These caches are independently loaded and not shared among the servers. Any changes to the system configuration triggers the cache cleanup; this process notifies all the servers in the cluster. Oracle 8-154 Oracle Fusion Middleware High Availability Guide Identity Manager uses oscache, jgroups for this purpose. Jgroups uses multicast addresses. A valid multicast address is randomly generated during installation and seeded to the Oracle Identity Manager metadata repository file. WebLogic Node Manager can be configured to monitor the server process and restart it in case of failure. The Oracle Enterprise Manager Fusion Middleware Control is used to monitor as well as to modify the configuration of the application.

8.9.1.4 Starting and Stopping Oracle Identity Manager