Integration Configuration in Oracle Identity Analytics

Integrating with Other Oracle Components 11-5 5. If there are any errors in the data collection, then Oracle Identity Manager indicates it with a FAILED status. If this happens, then the data collection session must be restarted. You can restart the data collection session by finalizing the current session using finalizeDataCollectionSession API and then running startDataCollection with a new session ID.

11.4 Oracle Identity Navigator

Oracle Identity Navigator OIN is a browser-based administrative portal designed to act as a launch pad for Oracle Identity Management components. It does not replace the individual component consoles. Rather, it allows you to access the Oracle Identity Management consoles from one site. When integrated with Oracle Identity Manager, OIN replaces the Oracle Identity Administration as the primary Oracle Identity Manager user interface. OIN has a product discovery feature that can be used to discover all active J2EE components in a domain, including the Oracle Identity Administration. For integration details, see Adding a Component Link to the Product Launcher by Using Product Discovery in the Oracle Fusion Middleware Administrators Guide for Oracle Identity Navigator.

11.5 Oracle Virtual Directory

If you install Oracle Identity Manager with LDAP, you must install Oracle Virtual Directory OVD. OVD connects to multiple enterprise directories and consolidates the contents of those directories into a unified view. For example, if your enterprise uses Oracle Internet Directory OID, iPlanet, and Active Directory, OVD can interface with all three directories and create a consolidated view. Oracle Identity Manager can then use a single connector to access the consolidated LDAP data on OVD. The LDAP Sync Provider also called the LDAP Provider connects Oracle Identity Manager and OVD. When integrated with Oracle Identity Manager, OVD provides the following benefits: ■ Oracle Identity Manager connector management is simplified - Only a single LDAP connector is needed for multiple directory providers although, multiple instances may be needed ■ LDAP connector reliability is improved - The same connector is used regardless of the underlying LDAP server. OVD handles the data translation that, in the past, required multiple LDAP connectors for multiple LDAP providers ■ The same identity virtualization capability is provided to all Fusion Middleware applications, reducing the overall footprint of components in the Enterprise For integration details, see the Oracle Fusion Middleware Installation Guide for Oracle Identity Management, which contains multiple procedures for integrating Oracle Identity Manager and Oracle Virtual Directory in various environments. Earlier releases of OVD are installed in Blocking IO BIO mode. The current release of OVD is installed in Non Blocking IO NIO mode by default. However, Oracle Identity Manager is not certified with NIO mode. Therefore, the OVD connection management in Oracle Identity Manager must be modified for working with OVD in NIO mode. The current release of OVD is also enhanced to include multiple change log support. These enhancements require changes to the OVD Changlog adapter parameters.