Starting and Stopping Oracle Identity Manager Configuration Artifacts External Dependencies

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

Oracle Identity Manager lifecycle events can be managed using one or more of the following command line tools and consoles: ■ Oracle WebLogic Scripting Tool WLST ■ Oracle WebLogic Server Administration Console ■ Oracle Enterprise Manager Fusion Middleware Control ■ Oracle WebLogic Node Manager

8.9.1.5 Configuration Artifacts

The configuration for the Oracle Identity Manager server is stored in the MDS repository and is managed using MBeans. The oim-config.xml file is the main configuration file. The OIM configuration can be managed using the MBean browser through the Oracle Enterprise Manager Fusion Middleware Control or through the command line MDS utilities. The oim-config.xml file is stored in the dboim-config.xml location of the MDS Repository. For more information about the MDS utilities, see the MDS utilities section of Oracle Fusion Middleware Developers Guide for Oracle Identity Manager. JMS is configured out of the box by the installer. All the necessary JMS queues, connection pools, data sources and so on are configured on the WebLogic application servers. The following queues are created when Oracle Identity Manager is deployed: ■ oimAttestationQueue ■ oimAuditQueue ■ oimDefaultQueue ■ oimKernelQueue ■ oimProcessQueue ■ oimReconQueue ■ oimSODQueue The Design Console and Remote Manager configuration is stored is the xlconfig.xml file.

8.9.1.6 External Dependencies

Oracle Identity Manager is a Java EE application that is deployed on an Oracle WebLogic Managed Server. Oracle Identity Manager uses the Worklist and Human workflow modules of the Oracle SOA Suite for request flow management. Oracle Identity Manager interacts with external repositories to store configuration and runtime data. Oracle Identity Manager requires these repositories to be available during initialization and during runtime. All Oracle Identity Manager credentials are Configuring High Availability for Identity Management Components 8-155 stored in the OIM repository. The external components required for the Oracle Identity Manager server to function are listed below: ■ Oracle WebLogic Server – Administration Server – Managed Server ■ Data Repositories – Configuration Repository MDS Schema – Runtime Repository OIM Schema – User Repository OIM Schema – SOA Repository SOA Schema ■ External LDAP Stores when using LDAP Sync ■ BI Publisher The Design Console is a tool used by the administrator for development and customization. The Design Console communicates directly with the Oracle Identity Manager engine, so it relies on the same components that the Oracle Identity Manager server relies on. Remote Manager is an optional independent standalone application, which calls the custom APIs on the local system. So it needs the JAR files for those custom APIs in its classpath.

8.9.1.7 Oracle Identity Manager Log File Locations