This chapter explains how to configure Oracle Identity Manager.
It includes the following topics:
Important Notes Before You Start Configuring Oracle Identity Manager
Creating a new WebLogic Domain for Oracle Identity Manager and SOA
Starting the Oracle Identity Manager 11g Configuration Wizard
Optional: Configuring Oracle Identity Manager Design Console
Optional: Configuring Oracle Identity Manager Remote Manager
Getting Started with Oracle Identity Manager After Installation
Note:
To invoke online help at any stage of the Oracle Identity Manager configuration process, click the Help button on the Oracle Identity Manager Configuration Wizard screens.
Before you start configuring Oracle Identity Manager, keep the following points in mind:
Before you start installing and configuring Oracle Identity and Access Management products in any of the scenarios discussed in this chapter, note that IAM_Home is used to refer to the Oracle Home directory that includes Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator. You can specify any name for this Oracle Home directory.
By performing the domain configuration procedures described in this chapter, you can create Managed Servers on a local machine (the machine on which the Administration Server is running). However, you can create and start Managed Servers for Oracle Identity and Access Management components on a remote machine. For more information, see the "Creating and Starting a Managed Server on a Remote Machine" topic in the guide Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.
You must use the Oracle Identity Manager Configuration Wizard to configure Oracle Identity Manager Server, Oracle Identity Manager Design Console (on Windows only), and Oracle Identity Manager Remote Manager.
If you are configuring Oracle Identity Manager Server, you must run the Oracle Identity Manager configuration wizard on the machine where the Administration Server is running. For configuring the Server, you can run the wizard only once during the initial setup of the Server. After the successful setup of Oracle Identity Manager Server, you cannot run the Oracle Identity Manager Configuration Wizard again to modify the configuration of Oracle Identity Manager Server. For such modifications, you must use Oracle Enterprise Manager Fusion Middleware Control.
If you are configuring only Design Console or Remote Manager, you can run the Oracle Identity Manager Configuration Wizard on the machine where Design Console or Remote Manager is being configured. You can configure Design Console or Remote Manager after configuring the Oracle Identity Manager Server. Note that you can run the Oracle Identity Manager Configuration Wizard to configure Design Console or Remote Manager as and when you need to configure them on new machines.
Note that Oracle Identity Manager requires Oracle SOA Suite 11g Release 1 (11.1.1.7.0), which should be exclusive to Oracle Identity and Access Management. You must install Oracle SOA Suite before configuring Oracle Identity Manager. If you are setting up integration between Oracle Identity Manager and Oracle Access Manager, ensure that Oracle Identity Manager, Oracle Access Manager, and Oracle SOA Suite are configured in the same domain.
This topic describes how to create a new WebLogic domain for Oracle Identity Manager and SOA. It includes the following sections:
Perform the configuration in this topic if you want to install Oracle Identity Manager in an environment where you may use Oracle Identity Manager as a provisioning or request solution. This option is also appropriate for Oracle Identity Manager environments that do not use Single Sign-On (SSO) or Oracle Access Manager.
Performing the configuration in this section installs the following components:
Administration Server
A Managed Server for Oracle Identity Manager
Oracle Identity Administration Console, Oracle Identity Manager Self Service Console, and Oracle Identity Manager Advanced Administration Console on the Oracle Identity Manager Managed Server
The configuration in this section depends on the following:
Oracle WebLogic Server 11g Release 1 (10.3.6) or Oracle WebLogic Server 11g Release 1 (10.3.5).
Installation of the Oracle Identity and Access Management 11g Release 1 (11.1.1.7.0) software.
Installation of Oracle SOA Suite 11g Release 1 (11.1.1.7.0).
Database schemas for Oracle Identity Manager and Oracle SOA 11g Suite. For more information, see Section 3.2.3, "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)".
Complete the following steps to create a new WebLogic domain for Oracle Identity Manager and SOA and to configure Oracle Identity Manager Server, Design Console, and Remote Manager:
Review the section Important Notes Before You Start Configuring Oracle Identity Manager.
Run the <IAM_Home>/common/bin/config.sh script (on UNIX). (<IAM_Home>\common\bin\config.cmd on Windows). The Welcome screen of the Oracle Fusion Middleware Configuration Wizard appears.
On the Welcome screen, select Create a new WebLogic domain, and click Next. The Select Domain Source screen appears.
On the Select Domain Source screen, ensure that the Generate a domain configured automatically to support the following products: option is selected.
Select Oracle Identity Manager - 11.1.1.3.0 [IAM_Home].
Note:
When you select the Oracle Identity Manager - 11.1.1.3.0 [IAM_Home] option, the following options are also selected, by default:
Oracle SOA Suite - 11.1.1.1.0 [Oracle_SOA1]
Oracle JRF 11.1.1.0 [oracle_common]
Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
Oracle WSM Policy Manager 11.1.1.0 [oracle_common]
Click Next. The Specify Domain Name and Location screen appears.
Enter a name and a location for the domain to be created, and click Next. The Configure Administrator User Name and Password screen appears.
Configure a user name and a password for the administrator. The default user name is weblogic. Click Next.
The Configure Server Start Mode and JDK screen appears. Choose a JDK from the Available JDKs and select a WebLogic Domain Startup Mode. Click Next. The Configure JDBC Component Schema screen appears. This screen displays a list of the following component schemas:
SOA Infrastructure
User Messaging Service
OIM MDS Schema
OWSM MDS Schema
SOA MDS Schema
OIM Infrastructure
On the Configure JDBC Component Schema screen, for the Oracle Identity Manager and its dependant schemas, specify the schema owner and password that you set in RCU when creating and loading the schemas. Click Next. The Test JDBC Component Schema screen appears. After the test succeeds, the Select Optional Configuration screen appears.
On the Select Optional Configuration screen, you can configure the Administration Server, JMS Distributed Destination, Managed Servers, Clusters, and Machines, Deployments and Services. Click Next.
Optional: Configure the following Administration Server parameters:
Name
Listen address
Listen port
SSL listen port
SSL enabled or disabled
Click Next.
Optional: Configure JMS Distributed Destination, as required. Click Next.
Optional: Configure Managed Servers, as required. Click Next.
Optional: Configure Clusters, as required. Click Next.
For more information about configuring clusters for Oracle Identity and Access Management products, see the "Configuring High Availability for Identity Management Components" topic in the guide Oracle Fusion Middleware High Availability Guide.
Optional: Assign Managed Servers to Clusters, as required. Click Next.
Optional: Configure Machines, as needed. This step is useful when you want to run the Administration Server on one machine and Managed Servers on another physical machine.Click Next.
Tip:
Before configuring a machine, use the ping command to verify whether the machine or host name is accessible.
Optional: Assign servers to machines. Click Next.
Optional: Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server. Click Next.
On the Configuration Summary screen, you can view summaries of your configuration for deployments, application, and service. Review the domain configuration, and click Create to start creating the domain.
After the domain configuration is complete, click Done to close the configuration wizard.
A new WebLogic domain to support Oracle Identity Manager is created in the <MW_HOME>\user_projects\domains directory (on Windows). On UNIX, the domain is created in the <MW_HOME>/user_projects/domains directory.
Start the Administration Server, as described in Appendix C, "Starting or Stopping the Oracle Stack".
Start the SOA Managed Server, as described in Appendix C, "Starting or Stopping the Oracle Stack".
Start the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard".
Configure the Oracle Identity Manager Server, Design Console, or Remote Manager, as described in Section 5.6, "Configuring Oracle Identity Manager Server", Section 5.7, "Optional: Configuring Oracle Identity Manager Design Console", and Section 5.8, "Optional: Configuring Oracle Identity Manager Remote Manager".
Note:
If weblogic is not your WebLogic administrator user name, you must complete a set of manual steps after starting the servers. For more information, see Section 2.6, "Optional: Updating the WebLogic Administrator Server User Name in Oracle Enterprise Manager Fusion Middleware Control (OIM Only)".
After installing and configuring Oracle Identity Manager in a WebLogic domain, you must run the Oracle WebLogic Administration Server and various Managed Servers, as described in Appendix C, "Starting the Stack".
Notes:
If weblogic is not your WebLogic administrator user name, you must complete a set of manual steps after starting the servers. For more information, see Section 2.6, "Optional: Updating the WebLogic Administrator Server User Name in Oracle Enterprise Manager Fusion Middleware Control (OIM Only).".
Oracle Identity Manager requires Oracle SOA Suite. In order to avoid concurrent update, Oracle Identity Manager and SOA servers should not be started simultaneously. Start the SOA server first, wait for the SOA server to come up and then start the Oracle Identity Manager server.
This section discusses the following topics:
Before configuring Oracle Identity Manager using the Oracle Identity Manager Wizard, ensure that you have installed and configured Oracle Identity Manager and SOA in a WebLogic.
The Oracle Identity Manager 11g Configuration Wizard prompts you to enter information about certain configurations, such as Database, Schemas, WebLogic Administrator User Name and Password, and LDAP Server. Therefore, keep this information ready with you before starting the Identity Management 11g Configuration Wizard.
This section discusses the following topics:
Prerequisites for Configuring Oracle Identity Manager Server
Prerequisites for Configuring Only Oracle Identity Manager Design Console on a Different Machine
Prerequisites for Configuring Only Oracle Identity Manager Remote Manager on a Different Machine
Before you can configure Oracle Identity Manager Server using the Oracle Identity Manager Configuration Wizard, you must complete the following prerequisites:
Installing a supported version of Oracle database. For more information, see Section 3.2.2, "Reviewing Database Requirements".
Creating and loading the required schemas in the database. For more information, see Section 3.2.3, "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU),".
Installing Oracle WebLogic Server and creating a Middleware Home directory. For more information, see Section 3.2.4, "Reviewing WebLogic Server and Middleware Home Requirements".
Installing Oracle SOA Suite 11g Release 1 (11.1.1.7.0) under the same Middleware Home directory. For more information, see Section 3.2.5, "Installing Oracle SOA Suite (Oracle Identity Manager Users Only)".
Installing the Oracle Identity and Access Management Suite (the suite that contains Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator) under the Middleware Home directory. For more information, see Installing Oracle Identity and Access Management (11.1.1.7.0).
Creating a new WebLogic domain or extending an existing Identity Management 11.1.1.7.0 domain for Oracle Identity Manager and Oracle SOA. For more information, see Section 5.2, "Creating a new WebLogic Domain for Oracle Identity Manager and SOA".
Starting the Oracle WebLogic Administration Server for the domain in which the Oracle Identity Manager application is deployed. For more information, see Appendix C, "Starting the Stack".
Starting the SOA Managed Server, as described in Appendix C, "Starting the Stack".
On the machine where you are installing and configuring Design Console, you must install the Oracle Identity and Access Management 11g (11.1.1.7.0) software containing Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator. For information, see Section 3.2.7, "Installing Oracle Identity and Access Management (11.1.1.7.0).".
Before you can configure Oracle Identity Manager Design Console by running the Oracle Identity Manager Configuration Wizard, you should have configured the Oracle Identity Manager Server, as described in Section 5.6, "Configuring Oracle Identity Manager Server" on a local or remote machine. In addition, the Oracle Identity Manager Server should be up and running.
Note:
Oracle Identity Manager Design Console is supported on Windows operating systems only. If you are installing and configuring only Design Console on a machine, you do not need to install Oracle WebLogic Server and create a Middleware Home directory before installing the Oracle Identity and Access Management software.
On the machine where you are installing and configuring Remote Manager, you must install the Oracle Identity and Access Management 11g (11.1.1.7.0) software containing Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator. For information, see Section 3.2.7, "Installing Oracle Identity and Access Management (11.1.1.7.0)".
Before you can configure Oracle Identity Manager Remote Manager by running the Oracle Identity Manager Configuration Wizard, you should have configured the Oracle Identity Manager Server, as described in Section 5.6, "Configuring Oracle Identity Manager Server". In addition, the Oracle Identity Manager Server should be up and running.
Note:
If you are installing and configuring only Remote Manager on a machine, you do not need to install Oracle WebLogic Server and create a Middleware Home directory before installing the Oracle Identity and Access Management software.
The Oracle Identity Management 11g Configuration Wizard enables you to configure Oracle Identity Manager Server, Design Console (Windows only), and Remote Manager.
If you are configuring Oracle Identity Manager Server, you must run this configuration wizard on the machine where the Administration Server is running.
You must complete this additional configuration for Oracle Identity Manager components after configuring Oracle Identity Manager in a new or existing WebLogic administration domain.
Note:
You can run the Oracle Identity Manager Configuration Wizard to configure Oracle Identity Manager Server only once during the initial setup. After the initial setup, you cannot run the Oracle Identity Manager Configuration Wizard again to modify the configuration of Oracle Identity Manager Server, Design Console, or Remote Manager. For such modifications, you must use Oracle Enterprise Manager Fusion Middleware Control.
This section discusses the following topics:
Scope of Configuration Using the Oracle Identity Manager 11g Configuration Wizard
Scenario 1: Oracle Identity Manager Server and Design Console on Different Machines
Scenario 2: Oracle Identity Manager Server and Remote Manager on Different Machines
You can use the Oracle Identity Manager 11g Configuration Wizard to configure the non-J2EE components and elements of Oracle Identity Manager. Most of the J2EE configuration is done automatically in the domain template for Oracle Identity Manager.
In this scenario, you configure Oracle Identity Manager Server on one machine, and install and configure only Oracle Identity Manager Design Console on a different Windows machine (a development or design system).
Perform the following tasks:
Install and configure Oracle Identity Manager Server on a machine after completing all of the prerequisites, as described in Section 5.6, "Configuring Oracle Identity Manager Server". Ensure that the Oracle Identity Manager Server is up and running.
On the Windows machine on which the Design Console is to be installed, install a JDK in a path without a space such as c:/jdk1.6.0_24.
Create a Middleware_Home folder such as c:/oracle/Middleware.
Run setup.exe from the installation media disk1 and follow the prompts selecting the Middleware_Home created above.
Note:
When you specify the location of the Middleware_Home, you will see a message "Specified middleware home is not valid. If you continue with this installation only Remote Manager and Design Console can be configured." This is a valid message if you intend to install only the Design Console.
The installer will install the Oracle Identity and Access Management suite needed to install the Design Console.
On the Windows machine where you installed the Oracle Identity and Access Management 11g software, run the Oracle Identity Manager Configuration Wizard to configure only Design Console. Note that you must provide the Oracle Identity Manager Server information, such as host and URL, when configuring Design Console. For more information, see Section 5.7, "Optional: Configuring Oracle Identity Manager Design Console".
In this scenario, you configure Oracle Identity Manager Server on one machine, and install and configure only Oracle Identity Manager Remote Manager on a different machine.
The following are the high-level tasks in this scenario:
Install and configure Oracle Identity Manager Server on a machine after completing all of the prerequisites, as described in Section 5.6, "Configuring Oracle Identity Manager Server". Ensure that the Oracle Identity Manager Server is up and running.
On a different machine, install the Oracle Identity and Access Management 11g software containing Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator. For information, see Section 3.2.7, "Installing Oracle Identity and Access Management (11.1.1.7.0)".
On the machine where you installed the Oracle Identity and Access Management 11g software, run the Oracle Identity Manager Configuration Wizard to configure only Remote Manager. Note that you must provide the Oracle Identity Manager Server information, such as host and URL, when configuring Remote Manager. For more information, see Section 5.8, "Optional: Configuring Oracle Identity Manager Remote Manager".
In this scenario, suitable for test environments, you install and configure Oracle Identity Manager Server, Design Console, and Remote Manager on a single Windows machine.
The following are the high-level tasks in this scenario:
Install and configure Oracle Identity Manager Server on a machine after completing all the prerequisites, as described in Section 5.6, "Configuring Oracle Identity Manager Server". Ensure that the Oracle Identity Manager Server is up and running.
On the same machine, configure Design Console, as described in Section 5.7, "Optional: Configuring Oracle Identity Manager Design Console".
On the same machine, configure Remote Manager, as described in Section 5.8, "Optional: Configuring Oracle Identity Manager Remote Manager".
To start the Oracle Identity Manager 11g Configuration Wizard, execute the <IAM_Home>/bin/config.sh script (on UNIX) on the machine where the Administration Server is running. (<IAM_Home>\bin\config.bat on Windows). The Oracle Identity Management 11g Configuration Wizard starts, and the Welcome Screen appears.
Note:
If you have extended an existing WebLogic domain to support Oracle Identity Manager, you must restart the Administration Server before starting the Oracle Identity Manager Configuration Wizard to configure Oracle Identity Manager Server, Design Console, or Remote Manager.
This topic describes how to install and configure only Oracle Identity Manager Server. It includes the following sections:
Completing the Prerequisites for Enabling LDAP Synchronization
Setting oamEnabled Parameter for Identity Virtualization Library
Enabling LDAP Sync after Installing and Configuring Oracle Identity Manager Server at a Later Point
Perform the configuration in this topic if you want to install Oracle Identity Manager Server on a separate host.
Performing the configuration in this section deploys only Oracle Identity Manager Server.
The installation and configuration in this section depends on Oracle WebLogic Server, on Oracle SOA Suite, and on the installation of Oracle Identity and Access Management 11g software. For more information, see Preparing to Install and Installing Oracle Identity and Access Management (11.1.1.7.0).
Perform the following steps to configure only Oracle Identity Manager Server:
Ensure that all the prerequisites, described in Section 5.4.1.1, "Prerequisites for Configuring Oracle Identity Manager Server", are satisfied. In addition, see Section 5.1, "Important Notes Before You Start Configuring Oracle Identity Manager".
On the machine where the Administration Server is running, start the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard". The Welcome screen appears.
On the Welcome screen, click Next. The Components to Configure screen appears.
On the Components to Configure screen, ensure that only the OIM Server option is selected. It is selected, by default. Click Next. The Database screen appears.
On the Database screen, enter the full path, listen port, and service name for the database in the Connect String field. For a single host instance, the format of connect string is hostname:port:servicename. For example, if the hostname is aaa.bbb.com, port is 1234, and the service name is xxx.bbb.com, then you must enter the connect string for a single host instance as follows:
aaa.bbb.com:1234:xxx.bbb.com
If you are using a Real Application Cluster database, the format of the database connect string is as follows:
hostname1:port1^hostname2:port2@servicename
Note:
You can use the same database or different databases for creating the Oracle Identity Manager schema and the Metadata Services schema.
In the OIM Schema User Name field, enter the name of the schema that you created for Oracle Identity Manager using the Oracle Fusion Middleware Repository Creation Utility (RCU). For more information, see Section 3.2.3, "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)".
In the OIM Schema Password field, enter the password for the Oracle Identity Manager schema that you set while creating the schema using the Oracle Fusion Middleware Repository Creation Utility (RCU).
If you want to use a different database for the Metadata Services (MDS) schema, select the Select different database for MDS Schema check box.
If you choose to use a different database for MDS schema, in the MDS Connect String field, enter the full path, listen port, and service name for the database associated with the MDS schema. For the format of the connect string, see Step 4.
In the MDS Schema User Name field, enter the name of the schema that you created for AS Common Services - Metadata Services using the Oracle Fusion Middleware Repository Creation Utility (RCU). For more information, see Section 3.2.3, "Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU)".
In the MDS Schema Password field, enter the password for the AS Common Services - Metadata Services schema that you set while creating the schema using the Oracle Fusion Middleware Repository Creation Utility (RCU). Click Next. The WebLogic Admin Server screen appears.
On the WebLogic Admin Server screen, in the WebLogic Admin Server URL field, enter the URL of the WebLogic Administration Server of the domain in the following format:
t3://hostname:port
In the UserName field, enter the WebLogic administrator user name of the domain in which the Oracle Identity Manager application and the Oracle SOA Suite application are deployed. If you are setting up integration between Oracle Identity Manager and Oracle Access Manager, the Oracle Access Manager application is also configured in the same domain.
In the Password field, enter the WebLogic administrator password of the domain in which the Oracle Identity Manager application and the Oracle SOA Suite application are deployed. Click Next.
The OIM Server screen appears. The OIM Server screen enables you to set a password for the system administrator (xelsysadm).
On the OIM Server screen, in the OIM Administrator Password field, enter a new password for the administrator. A valid password contains at least 6 characters; begins with an alphabetic character; includes at least one number, one uppercase letter, and one lowercase letter. The password cannot contain the first name, last name, or the login name for Oracle Identity Manager.
In the Confirm User Password field, enter the new password again.
In the OIM HTTP URL field, enter the http URL that front-ends the Oracle Identity Manager application.
The URL is of the format: http(s)://<oim_host>:<oim_port>. For example, https://localhost:7002.
In the KeyStore Password field, enter a new password for the keystore. A valid password can contain 6 to 30 characters, begin with an alphabetic character, and use only alphanumeric characters and special characters like Dollar ($), Underscore (_), and Pound (#). The password must contain at least one number.
In the Confirm Keystore Password field, enter the new password again. Click Next. The OIM Server screen appears.
Optional: To enable LDAP Sync, you must select the Enable LDAP Sync option on the OIM Server screen.
Note:
If you want to enable LDAP Sync, before enabling LDAP Sync you must complete the steps, as described in Section 5.6.5, "Completing the Prerequisites for Enabling LDAP Synchronization".
Once LDAP Sync is enabled on the OIM Server screen and prerequisites are completed, you must continue to configure the Oracle Identity Manager Server. After you have configured the Oracle Identity Manager Server and exited the Oracle Identity Management Configuration Wizard, you must run the LDAP post-configuration utility as described in Section 5.6.6, "Running the LDAP Post-Configuration Utility".
After making your selections, click Next on the OIM Server screen. If you chose to enable LDAP Sync, the LDAP Server screen appears.
The LDAP Server screen enables you to specify the following information:
Directory Server Type - Select the desired Directory Server from the dropdown list. You have the following options:
OID
ACTIVE_DIRECTORY
IPLANET
OVD
Notes:
IPLANET is also referred to as Oracle Directory Server Enterprise Edition (ODSEE) in this guide.
If you choose to use OID, ACTIVE_DIRECTORY or IPLANET as the Directory Server and if you want to integrate Oracle Identity Manager and Oracle Access Manager, you must set the oamEnabled parameter to true. To set the oamEnabled parameter to true in case of Identity Virtualization Library, see Section 5.6.9, "Setting oamEnabled Parameter for Identity Virtualization Library".
Directory Server ID - enter the Directory Server ID. It can be any unique value.
For example: oid1 for OID, iplanet1 for IPLANET, and ad1 for ACTIVE_DIRECTORY
Server URL - enter the LDAP URL in the format ldap://oid_host:oid_port.
Server User - enter the user name for Directory Server administrator.
For example: cn=oimAdminUser,cn=systemids,dc=mycompany,dc=com
Server Password - enter the Oracle Identity Manager admin password.
Server SearchDN - enter the Distinguished Names (DN). For example, dc=exampledomain, dc=com. This is the top-level container for users and roles in LDAP, and Oracle Identity Manager uses this container for reconciliation.
Click Next. The LDAP Server Continued screen appears.
On the LDAP Server Continued screen, enter the following LDAP information:
LDAP RoleContainer - enter a name for the container that will be used as a default container of roles in the LDAP directory. You can configure isolation rules in Oracle Identity Manager to create roles in different containers in LDAP. For example, cn=groups, dc=mycountry, dc=com.
LDAP RoleContainer Description - enter a description for the default role container.
LDAP Usercontainer - enter a name for the container that will be used as a default container of users in the LDAP directory. You can configure isolation rules in Oracle Identity Manager to create users in different containers in LDAP. For example, cn=users, dc=mycountry, dc=com.
LDAP Usercontainer Description - enter a description for the default user container.
User Reservation Container - enter a name for the container that will be used for reserving user names in the LDAP directory while their creation is being approved in Oracle Identity Manager. When the user names are approved, they are moved from the reservation container to the user container in the LDAP directory. For example, cn=reserve, dc=mycountry, dc=com.
After enabling LDAP synchronization and after running the LDAP post-configuration utility, you can verify it by using the Oracle Identity Manager Administration Console. For more information, see Section 5.6.7, "Verifying the LDAP Synchronization". Click Next. The Configuration Summary screen appears.
If you did not choose the Enable LDAP Sync option on the OIM Server screen, the Configuration Summary screen appears after you enter information in the OIM Server screen.
The Configuration Summary screen lists the applications you selected for configuration and summarizes your configuration options, such as database connect string, OIM schema user name, MDS schema user name, WebLogic Admin Server URL, WebLogic Administrator user name, and OIM HTTP URL.
Review this summary and decide whether to start the configuration. If you want to modify any of the configuration settings at this stage, select a topic in the left navigation page and modify your choices. To continue installing this configuration of the Oracle Identity Manager Server, click Configure.
Note:
Before configuring an application, you can save your configuration settings and preferences in a response file. Response files are text files that you can create or edit in a text editor. You can use response files to perform a silent installation or use as templates or customized settings for your environment. For more information, see Appendix F, "Performing a Silent Installation".
After you click Configure, the Configuration Progress screen appears. Click Next.
A configuration log is saved to the logs directory under Oracle Inventory directory. For information about the log files, see Appendix G, "Installation Log Files". If the Configuration Progress screen displays any errors, click Abort to stop the installation and restart the Oracle Identity Manager Configuration Wizard.
Click Finish.
Restart the WebLogic Administration Server and SOA Managed Server, as described in Appendix C, "Restarting Servers".
Note:
If the configuration fails, click Abort to stop the installation and restart the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard".
You must complete the following prerequisites:
Before you can use your LDAP directory as an Identity store, you must preconfigure it.
Note:
Follow the steps in this section if you are using any one of the Directory Servers mentioned below for LDAP Synchronization:
OID
Active Directory
iPlanet/ODSEE
OVD
You must complete the following steps to preconfigure the Identity Store if you have not configured already:
Create User, Group and Reserve Containers.
Create the proxy user for OIM, namely oimadminuser in the Directory Server outside the search base used for OIM reconciliation. This OIM proxy user should not be reconciled into OIM Database.
Create the oimadmingroup and assign the oimadminuser to the group.
Add the ACIs to the group and user container for the OIM proxy user to have access to all entries in those containers.
Extend OIM Schema for non-OID Directory Servers.
For Active Directory
The OIM Schema for Active Directory is in the following location:
$MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/oimtemplates
Run the following command to extend Active Directory schema:
On Windows:
extendadschema.bat -h AD_host -p AD_port -D <administrator@mydomain.com> -q -AD <dc=mydomain,dc=com> -OAM true -schemaFiles adUpgradeOrclIDXPerson.ldif
On UNIX:
sh extendadschema.sh -h AD_host -p AD_port -D administrator@mydomain.com -q -AD dc=mydomain,dc=com -OAM true -schemaFiles adUpgradeOrclIDXPerson.ldif
For ODSEE/iPlanet
The OIM Schema for iPlanet (also known as ODSEE) is in the following location:
$MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/oimtemplates/sunOneSchema.ldif
Run the following command to extend ODSEE schema:
ldapmodify -h <ODSEE Server> -p <ODSEE port> -D <ODSEE Admin ID> -w <ODSEE Admin password> -f sunOneSchema.ldif
If you want to enable OAM-OIM integration, extend the following OAM Schema:
For OID
To extend OAM Schema for OID, locate the following files:
$IAM_HOME/oam/server/oim-intg/ldif/oid/schema/OID_oblix_pwd_schema_add.ldif
$IAM_HOME/oam/server/oim-intg/ldif/oid/schema/OID_oblix_schema_add.ldif
$IAM_HOME/oam/server/oim-intg/ldif/oid/schema/OID_oim_pwd_schema_add.ldif
$IAM_HOME/oam/server/oim-intg/ldif/oid/schema/OID_oblix_schema_index_add.ldif
Use ldapmodify from the command line to load the four LDIF files:
cd $IAM_HOME/oam/server/oim-intg/ldif/oid/schema/
ldapmodify -h <OID Server> -p <OID port> -D <OID Admin ID> -w <OID Admin password> -f OID_oblix_pwd_schema_add.ldif
ldapmodify -h <OID Server> -p <OID port> -D <OID Admin ID> -w <OID Admin password> -f OID_oblix_schema_add.ldif
ldapmodify -h <OID Server> -p <OID port> -D <OID Admin ID> -w <OID Admin password> -f OID_oim_pwd_schema_add.ldif
ldapmodify -h <OID Server> -p <OID port> -D <OID Admin ID> -w <OID Admin password> -f OID_oblix_schema_index_add.ldif
For Active Directory
To extend OAM Schema for Active Directory, locate the following files:
$IAM_HOME/oam/server/oim-intg/ldif/ad/schema/ADUserSchema.ldif
$IAM_HOME/oam/server/oim-intg/ldif/ad/schema/AD_oam_pwd_schema_add.ldif
In both the above files, replace the domain-dn with the appropriate domain-dn value.
Use ldapadd from the command line to load the two LDIF files, as follows:
cd $IAM_HOME/oam/server/oim-intg/ldif/ad/schema/
ldapadd -h <activedirectoryhostname> -p <activedirectoryportnumber> -D <AD_administrator> -q -c -f ADUserSchema.ldif
ldapadd -h <activedirectoryhostname> -p <activedirectoryportnumber> -D <AD_administrator> -q -c -f AD_oam_pwd_schema.ldif
where AD_administrator is a user which has schema extension privileges to the directory.
For example:
ldapadd -h activedirectoryhost.mycompany.com -p 389 -D adminuser –q -c -f ADUserSchema.ldif
For ODSEE/iPlanet
To extend OAM Schema for ODSEE, locate the following files:
$IAM_HOME/oam/server/oim-intg/ldif/iplanet/schema/iPlanet7_user_index_add.ldif
$IAM_HOME/oam/server/oim-intg/ldif/iplanet/schema/iPlanet7_user_index_generic.ldif
$IAM_HOME/oam/server/oim-intg/ldif/iplanet/schema/iPlanet_oam_pwd_schema_add.ldif
$IAM_HOME/oam/server/oim-intg/ldif/iplanet/schema/iPlanet_user_schema_add.ldif
$IAM_HOME/oam/server/oim-intg/ldif/iplanet/schema/iPlanet_user_index_add.ldif
Note:
If you are not sure about the which index-root you should use, instead of iPlanet7_user_index_add.ldif, please use iPlanet7_user_index_generic.ldif file which also has step by step instructions on finding index-root.
Use ldapmodify from the command line to load the four LDIF files:
cd $IAM_HOME/oam/server/oim-intg/ldif/iplanet/schema/
ldapmodify -h <ODSEE Server> -p <ODSEE port> -D <ODSEE Admin ID> -w <ODSEE Admin password> -f iPlanet_oam_pwd_schema_add.ldif
ldapmodify -h <ODSEE Server> -p <ODSEE port> -D <ODSEE Admin ID> -w <ODSEE Admin password> -f iPlanet_user_schema_add.ldif
ldapmodify -h <ODSEE Server> -p <ODSEE port> -D <ODSEE Admin ID> -w <ODSEE Admin password> -f iPlanet_user_index_add.ldif
If you are using Oracle Directory Server Enterprise Edition (ODSEE), you must enable moddn and Changelog properties in the ODSEE Directory Server.
Skip this step if you are using Oracle Internet Directory (OID) or Active Directory.
Note:
The preconfiguration differs, depending on the directory store you wish to use to hold your identity information. For a sample procedure of preconfiguring the Identity Store, refer to Appendix D, "Preconfiguring Oracle Directory Server Enterprise Edition (ODSEE)".
Oracle Virtual Directory communicates with other directories through adapters.Before you can start using Oracle Virtual Directory as an identity store, you must create adapters to each of the directories you want to use.The procedure is slightly different, depending on the directory you are connecting to.
Note:
This procedure is applicable only if you are using OVD as the Directory Server. If you choose to use OID, Active Directory or Oracle Directory Server Enterprise Edition (ODSEE) as the Directory Server, the required adapters are created and configured while installing and configuring the Oracle Identity Manager server. For more information on managing the adapters, see "Managing Identity Virtualization Library (libOVD) Adapters" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
The User Management and Changelog adapters for Identity Virtualization Library configured by the Oracle Identity Manager installer are stored in adapters.os_xml file. The adapters.os_xml will be in the following location:
$DOMAIN_HOME/config/fmwconfig/ovd/<context>/
For example:
$DOMAIN_HOME/config/fmwconfig/ovd/oim1/adapters.os_xml
The following sections show how to create adapters for the respective directories:
Create the user adapter for Oracle Virtual Directory. Follow the steps below to create the User Adapter in Oracle Virtual Directory using Oracle Directory Services Manager.
Open a browser and bring up the ODSM console at http://hostname:port/odsm
Note:
The default port number is 7005.
Connect to Oracle Virtual Directory by using the appropriate connection entry.
On the Home page, click the Adapter tab.
Start the New Adapter Wizard by clicking Create Adapter at the top of the adapter window.
Create a new adapter using the New Adapter Wizard, with the following parameters:
Table 5-1 Parameters for User Adapter Creation
| Screen | Field | Value/Step |
|---|---|---|
|
Type |
Adapter Type |
|
|
Adapter Name |
|
|
|
Adapter Template |
|
|
|
Connection |
Use DNS for Auto Discovery |
No |
|
Host |
|
|
|
Port |
389 |
|
|
Server Proxy Bind DN |
|
|
|
Proxy Password |
Password for |
|
|
Connection Test |
Validate that the test succeeds. |
|
|
Namespace |
Remote Base |
|
|
Mapped Namespace |
|
Verify that the summary is correct and then click Finish.
Edit the User Adapter as follows:
Select the User Adapter.
Click the Plug-ins Tab.
Click the User Management Plug-in, then click Edit in the plug-ins table. The plug-in editing window appears.
In the Parameters table, update the parameter values as follows:
Table 5-2 User Adapter Parameter Values
| Parameter | Value |
|---|---|
|
directoryType |
|
|
pwdMaxFailure |
|
|
oamEnabled |
Note that this parameter should be set to |
|
mapObjectclass |
container= |
Click OK.
Click Apply.
Create the change log adapter for Oracle Virtual Directory. Follow the steps below to create the Change Log Adapter in Oracle Virtual Directory using Oracle Directory Services Manager.
Open a browser and bring up the ODSM console at http://hostname:port/odsm
Note:
The default port number is 7005.
Connect to Oracle Virtual Directory by using the appropriate connection entry.
On the Home page, click on the Adapter tab.
Start the New Adapter Wizard by clicking Create Adapter at the top of the adapter window.
Create a new adapter using the New Adapter Wizard, with the following parameters:
Table 5-3 Parameters for Change Log Adapter Creation
| Screen | Field | Value/Step |
|---|---|---|
|
Type |
Adapter Type |
|
|
Adapter Name |
|
|
|
Adapter Template |
|
|
|
Connection |
Use DNS for Auto Discovery |
No |
|
Host |
|
|
|
Port |
389 |
|
|
Server Proxy Bind DN |
|
|
|
Proxy Password |
Password for |
|
|
Connection Test |
Validate that the test succeeds |
|
|
Namespace |
Remote Base |
Remote Base should be empty |
|
Mapped Namespace |
|
Verify that the summary is correct, then click Finish.
To edit the change adapter follow the steps below:
Select the OIM Change Log Adapter.
Click the Plug-ins tab.
In the Deployed Plus-ins table, click the changelog plug-in, then click Edit in the plug-ins table. The plug-in editing window appears.
In the Parameters table, update the parameter values.
Edit the Change Log Adapter to either add or modify the properties so that they match the values shown in the following table. You must add the modifierDNFilter, sizeLimit, and targetDNFilter properties to the adapter.
Table 5-4 Changelog Adapter Parameter Values
| Parameter | Value |
|---|---|
|
directoryType |
|
|
mapAttribute |
|
|
requiredAttribute |
|
|
modifierDNFilter |
!( Note: This is an example. This value can be of any Proxy DN that the customer defines. For example: rootSuffix can be |
|
sizeLimit |
1000 |
|
targetDNFilter |
Optional parameter. For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
|
oamEnabled |
Note that this parameter should be set to |
|
mapUserState |
For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
|
virtualDITAdapterName |
Name of the OID User Management adapter. For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
Click OK.
Click Apply.
Note:
For more information about these plug-in parameters, refer to the Understanding the Oracle Virtual Directory Plug-ins section in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory 11g Release 1 (11.1.1).
Restarting Oracle Virtual Directory
Restart Oracle Virtual Directory, as described in Appendix C, "Starting or Stopping the Oracle Stack".
Create the user adapter for Oracle Virtual Directory. Follow these steps to create the User Adapter in Oracle Virtual Directory using Oracle Directory Services Manager.
Start the Administration Server and the ODSM Managed Server as described in Appendix C, "Starting or Stopping the Oracle Stack".
Open a browser and bring up the ODSM console at http://hostname:port/odsm
Note:
The default port number is 7005.
Connect to Oracle Virtual Directory by using the appropriate connection entry.
On the Home page, click the Adapter tab.
Start the New Adapter Wizard by clicking Create Adapter at the top of the adapter window.
Create a new adapter using the New Adapter Wizard, with the following parameters:
Table 5-5 Parameters for New User Adapter Creation
| Screen | Field | Value/Step |
|---|---|---|
|
Type |
Adapter Type |
|
|
Adapter Name |
|
|
|
Adapter Template |
|
|
|
Connection |
Use DNS for Auto Discovery |
No |
|
Host |
Active Directory host/virtual name |
|
|
Port |
Active Directory SSL port |
|
|
Server Proxy Bind DN |
|
|
|
Proxy Password |
Password for |
|
|
User SSL/TLS |
Selected |
|
|
SSL Authentication Mode |
Server Only Authentication |
|
|
Connection Test |
Validate that the test succeeds. |
|
|
Namespace |
Remote Base |
|
|
Mapped Namespace |
|
Verify that the summary is correct and then click Finish.
Edit the User Adapter as follows:
Select the OIM User Adapter.
Click the Plug-ins Tab.
Click the User Management Plug-in, then click Edit in the plug-ins table. The plug-in editing window appears.
In the Parameters table, update the parameter values as follows:
Table 5-6 User Adapter Parameter Values
| Parameter | Value |
|---|---|
|
directoryType |
|
|
mapAttribute |
|
|
mapAttribute |
|
|
addAttribute |
|
|
mapAttribute |
|
|
mapAttribute |
|
|
mapObjectclass |
|
|
mapObjectclass |
|
|
mapObjectclass |
|
|
mapPassword |
|
|
exclusionMapping |
|
|
pwdMaxFailure |
|
|
oamEnabled |
Note that this parameter should be set to |
|
oimLanguages |
For language support, you need to edit the User Management plugin to add a new configuration parameter See "Important Notes on User Management Plugin Configuration". |
Click OK.
Click Apply.
Important Notes on User Management Plugin Configuration
oimLanguages attribute: For language support, you need to edit the User Management plugin to add a new configuration parameter oimLanguages.
For example, if the Managed Localization for the DisplayName while creating the User in OIM is selected as French, then the value for oimLanguages in the User Management adapter plugin should be fr. If you have other languages to be supported, say Japanese, then the value for the parameter should be fr,ja.
This parameter is functional only when the directoryType parameter is set to activedirectory.
The User Management plugin has the following configuration parameters:
oimLanguages , <separated list of language codes to be used in attribute language subtypes>.
Table 5-7 Language Codes'for the MLS Enabled Attributes
| Objectclasses | MLS Enabled Attributes | Language Codes |
|---|---|---|
|
orclIDXPerson |
|
|
|
orclIDXGroup |
|
|
Note:
If you are using Identity Virtualization Library, then see "Managing Identity Virtualization Library (libOVD) Adapters" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
Follow the steps below to create the Change Log Adapter in Oracle Virtual Directory using Oracle Directory Services Manager.
Open a browser and bring up the ODSM console at http://hostname:port/odsm
Note:
The default port number is 7005.
Connect to Oracle Virtual Directory by using the appropriate connection entry.
On the Home page, click on the Adapter tab.
Start the New Adapter Wizard by clicking Create Adapter at the top of the adapter window.
Create a new adapter using the New Adapter Wizard, with the following parameters:
Table 5-8 Parameters for New Change Log Adapter Creation
| Screen | Field | Value/Step |
|---|---|---|
|
Type |
Adapter Type |
|
|
Adapter Name |
|
|
|
Adapter Template |
|
|
|
Connection |
Use DNS for Auto Discovery |
No |
|
Host |
Active Directory host/virtual name |
|
|
Port |
389 |
|
|
Server Proxy Bind DN |
|
|
|
Proxy Password |
Password for |
|
|
Connection Test |
Validate that the test succeeds |
|
|
Namespace |
Remote Base |
Remote Base should be empty |
|
Mapped Namespace |
|
Verify that the summary is correct and then click Finish.
To edit the change adapter follow the steps below:
Select the OIM Change Log Adapter.
Click the Plug-ins tab.
In the Deployed Plus-ins table, click the changelog plug-in, then click Edit in the plug-ins table. The plug-in editing window appears.
In the Parameters table, update the parameter values.
Edit the Change Log Adapter to either add or modify the properties so that they match the values shown in Table 5-9. You must add the sizeLimit, and targetDNFilter properties to the adapter.
Table 5-9 Changelog Adapter Parameter Values
| Parameter | Value |
|---|---|
|
directoryType |
|
|
mapAttribute |
|
|
requiredAttribute |
samaccountname |
|
sizeLimit |
1000 |
|
targetDNFilter |
Optional parameter. For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration" . |
|
oamEnabled |
Note that this parameter should be set to |
|
mapUserState |
For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration" . |
|
virtualDITAdapterName |
The name of the User adapter For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
Note:
The parameter modifierDNFilter should not be added to Active Directory Changelog plugin adapter.
Click OK.
Click Apply.
Create the user adapter for Oracle Virtual Directory. Follow the steps below to create the User Adapter in Oracle Virtual Directory using Oracle Directory Services Manager.
Start the Administration Server and the ODSM Managed Server as described in Appendix C, "Starting or Stopping the Oracle Stack".
Open a browser and bring up the ODSM console at http://hostname:port/odsm
Note:
The default port number is 7005.
Connect to Oracle Virtual Directory by using the appropriate connection entry.
On the Home page, click on the Adapter tab.
Start the New Adapter Wizard by clicking on Create Adapter at the top of the adapter window.
Create a new adapter using the New Adapter Wizard, with the following parameters:
Table 5-10 Parameters for New User Adapter Creation
| Screen | Field | Value/Step |
|---|---|---|
|
Type |
Adapter Type |
|
|
Adapter Name |
|
|
|
Adapter Template |
|
|
|
Connection |
Use DNS for Auto Discovery |
No |
|
Host |
Sun Java System Directory Server host/virtual name |
|
|
Port |
Sun Java System Directory Server port |
|
|
Server Proxy Bind DN |
|
|
|
Proxy Password |
Password for ( |
|
|
Connection Test |
Validate that the test succeeds. |
|
|
Namespace |
Remote Base |
|
|
Mapped Namespace |
|
Verify that the summary is correct and then click Finish.
Note:
For information about creating Oracle Identity Manager user adapter by using Oracle Directory Services Manager, refer to the "Creating LDAP Adapters" topic in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.
Edit the User Adapter as follows:
Select the OIM User Adapter.
Click the Plug-ins Tab.
Click the User Management Plug-in, then click Edit in the plug-ins table. The plug-in editing window appears.
In the Parameters table, update the parameter values as follows:
Table 5-11 User Adapter Parameter Values
| Parameter | Value |
|---|---|
|
directoryType |
|
|
mapAttribute |
|
|
mapObjectclass |
|
|
pwdMaxFailure |
|
|
oamEnabled |
Note that this parameter should be set to |
Click OK.
Click Apply.
Follow the steps below to create the Change Log Adapter in Oracle Virtual Directory using Oracle Directory Services Manager.
Open a browser and bring up the ODSM console at http://hostname:port/odsm
Note:
The default port number is 7005.
Connect to Oracle Virtual Directory by using the appropriate connection entry.
On the Home page, click on the Adapter tab.
Start the New Adapter Wizard by clicking on Create Adapter at the top of the adapter window.
Create a new adapter using the New Adapter Wizard, with the following parameters:
Table 5-12 Parameters for New Change Log Adapter Creation
| Screen | Field | Value/Step |
|---|---|---|
|
Type |
Adapter Type |
|
|
Adapter Name |
|
|
|
Adapter Template |
|
|
|
Connection |
Use DNS for Auto Discovery |
No |
|
Host |
Sun Java System Directory Server host virtual name |
|
|
Port |
Sun Java System Directory Server port |
|
|
Server Proxy Bind DN |
|
|
|
Proxy Password |
Password for ( |
|
|
Connection Test |
Validate that the test succeeds. |
|
|
Namespace |
Remote Base |
|
|
Mapped Namespace |
|
Verify that the summary is correct, then click Finish.
Note:
For information about creating Oracle Identity Manager user adapter by using Oracle Directory Services Manager, refer to the "Creating LDAP Adapters" topic in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory.
To edit the change adapter follow the steps below:
Select the OIM Change Log Adapter.
Click the Plug-ins tab.
In the Deployed Plus-ins table, click the changelog plug-in, then click Edit in the plug-ins table. The plug-in editing window appears.
In the Parameters table, update the parameter values.
Edit the Change Log Adapter to either add or modify the properties so that they match the values shown in the following table. You must add the mapObjectclass, modifierDNFilter, sizeLimit, and targetDNFilter properties to the adapter.
Table 5-13 Changelog Adapter Parameter Values
| Parameter | Value |
|---|---|
|
directoryType |
|
|
mapAttribute |
|
|
mapObjectclass |
|
|
modifierDNFilter |
Note : This is an example. This value can be of any Proxy DN that the customer defines.For example: rootSuffix can be |
|
sizeLimit |
1000 |
|
virtualDITAdapterName |
Name of the iPlanet User Management adapter. For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
|
targetDNFilter |
Optional parameter. For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
|
oamEnabled |
Note that this parameter should be set to |
|
mapUserState |
For more information, see Section 5.6.5.2.4, "Important Notes on Changelog Plugin Configuration". |
Click OK.
Click Apply.
Note:
For more information about these plug-in parameters, refer to the Understanding the Oracle Virtual Directory Plug-ins section in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory 11g Release 1 (11.1.1).
The virtualDITAdapterName parameter must be added after the changelog adapter is created.
virtualDITAdapterName identifies the corresponding user profile adapter name. For example, in a single-directory deployment, you can set this parameter value to A1, which is the user adapter name.
If you set this parameter virtualDITAdapterName to A1, the plug-in fetches the mapAttribute and mapObjectclass configuration in the UserManagementPlugin of adapter A1, so you do not have to duplicate those configurations.
This configuration is a must for directoryType=ActiveDirectory for the GUID mapping to happen in the case of incremental reconciliation to avoid the missing required attribute exception. (LDAP GUID=null).
Add the attribute virtualDITAdapterName and set it to the value of the Active Directory User Management adapter name in the Active Directory changelog plugin. This is required to pick up the attribute mappings set in the Active Directory User Management adapter plugin as the Active Directory schema and OIM schema are different.
targetDNFilter attribute should be set if you want to perform reconciliation from a certain user container and group container instead of from the root suffix.
These values should be the ones entered for User Container and Role Container during the configuration of Oracle Identity Manager when LDAP Sync is enabled.
For example:
targetDNFilter : cn=Users,dc=mycountry,dc=mycompany,dc=com
targetDNFilter : cn=Groups,dc=mycountry,dc=mycompany,dc=com
These settings would pull in/reconcile all users and groups from the above mentioned containers in the backend Directory Server.
The changelog adapter plugin should always have the attribute mapUserState set to true for the attribute orclaccountenabled to return in the search result.
Note:
If you are using Identity Virtualization Library, then see "Managing Identity Virtualization Library (libOVD) Adapters" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
For more information about these plug-in parameters, refer to the "Understanding the Oracle Virtual Directory Plug-ins" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory 11g Release 1 (11.1.1).
You must run the LDAP post-configuration utility after you have configured the Oracle Identity Manager Server and exited the Oracle Identity Management Configuration Wizard. The LDAP configuration post-setup script enables all the LDAP Sync-related incremental Reconciliation Scheduler jobs, which are disabled by default.
Note:
This procedure is applicable to all the Directory Server options. The LDAP post-configuration utility must be run after configuring Oracle Identity Manager server. This procedure is required only if you chose to enable and configure LDAP Sync during the Oracle Identity Manager Server configuration.
Setting Up Environment Variables
Before you run the LDAP post-configuration utility, you must ensure that the following environment variables are set:
APP_SERVER - is set to the application server on which Oracle Identity Manager is running. Set APP_SERVER to weblogic.
JAVA_HOME - is set to the directory where the JDK is installed on your machine.
MW_HOME - is set to the Middleware home path provided during the Oracle Identity Manager installation.
OIM_ORACLE_HOME - is set to the directory where Oracle Identity Manager is deployed.
For example:
On UNIX, it is the <MW_HOME>/IAM_Home directory.
On Windows, it is the <MW_HOME>\IAM_Home directory.
WL_HOME - is set to the wlserver_10.3 directory under your Middleware Home.
For example:
On UNIX, it is the <MW_HOME>/wlserver_10.3 directory.
On Windows, it is the <MW_HOME>\wlserver_10.3 directory.
DOMAIN_HOME - is set to the domain of the WebLogic Server.
For example:
On UNIX, it is the <MW_HOME>/user_projects/domains/base_domain directory.
On Windows, it is the <MW_HOME>\user_projects\domains\base_domain directory.
Running the LDAP Post-Configuration Utility
Run the LDAP post-configuration utility as follows:
Open the ldapconfig.props file in a text editor. This file is located in the server/ldap_config_util directory under the IAM_Home for Oracle Identity and Access Management.
In the ldapconfig.props file, set values for the following parameters:
OIMServerType - Specify the application server on which Oracle Identity Manager is deployed.
For example:
OIMServerType=WLS
OIMProviderURL - Specify the URL for the OIM provider.
If the OIMServerType is WLS, then
OIMProviderURL=t3://localhost:ManagedServerPort
For example:
OIMProviderURL=t3://localhost:14000
LDAPURL - Specify the URL for the OVD instance.
If OVD server is selected during Oracle Identity Manager installation, then provide value for LDAPURL. If OVD server is not selected during Oracle Identity Manager installation, then leave LDAPURL blank.
LDAPURL=ldap://<OVD server>:<OVD Port>
For example:
LDAPURL=ldap://OVDserver.examplehost.exampledomain.com:6501
Note:
If you have selected Active Directory or ODSEE as the directory server during Oracle Identity Manager installation, after enabling LDAPSync, do not specify the value for the LDAPURL parameter. Leave LDAPURL blank. For example: LDAPURL=
Enter OVD server and OVD port number and specify the URL as value only if you are using Oracle Virtual Directory (OVD) as the directory server.
LDAPAdminUsername - Specify the user name for the OVD Administrator.
If OVD server is selected during Oracle Identity Manager installation, then provide the Admin user name to connect to LDAP/OVD Server.
For example:
LDAPAdminUsername=cn=oimAdminUser,cn=systemids,dc=mycompany,dc=com
Notes:
LDAPAdminUsername is the name of user used to connect to Identity Store. For example: cn=oimAdminUser,cn=systemids,dc=mycompany,dc=com
This LDAPAdminUsername should not be located in the user container where customer's user accounts reside. For example: cn=Users,cn=oracleAccounts,dc=mycompany,dc=com. This user should be outside the search scope in order to avoid reconciliation of this user into OIM.
If you have selected Active Directory or ODSEE as the directory server during Oracle Identity Manager installation, after enabling LDAPSync, do not specify the value for the LDAPAdminUsername parameter. Leave LDAPAdminUsername blank. For example: LDAPAdminUsername=
Enter the OVD user admin name as value only if you are using Oracle Virtual Directory (OVD) as the directory server.
LIBOVD_PATH_PARAM - Specify the configuration directory path of libOVD.
If OVD server is not selected during Oracle Identity Manager installation, then provide the following value for this parameter:
LIBOVD_PATH_PARAM=<Middleware_Home>/user_projects/domains/base_domain/config/fmwconfig/ovd/oim
Notes:
If you have selected Active Directory or ODSEE as the directory server during Oracle Identity Manager installation, after enabling LDAPSync, specify the value for this property similar to the example given above.
If OVD server is selected during Oracle Identity Manager installation, then leave this parameter blank. For example: LIBOVD_PATH_PARAM=
ChangeLogNumber - Leave this parameter blank.
Ensure the required environment variables are set, as described in "Setting Up Environment Variables".
Start the Oracle Identity Manager Managed Server. For more information, see Section 5.3, "Starting the Servers".
The utility and the properties files are located in the server/ldap_config_util directory under your IAM_Home. IAM_Home is the Oracle Identity and Access Management home directory for Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator.
On the command line, run the LDAP configuration post-setup script as follows:
On Windows:
LDAPConfigPostSetup.bat <location of the directory containing the ldapconfig.props file>
For example:
LDAPConfigPostSetup.bat c:\Oracle\Middleware\IAM_Home\server\ldap_config_util
On UNIX:
LDAPConfigPostSetup.sh <location of the directory containing the ldapconfig.props file>
For example:
LDAPConfigPostSetup.sh <MW_Home>/IAM_Home/server/ldap_config_util
When prompted, enter the OIM administrator's password and the LDAP administrator password as applicable.
Notes:
If you have selected Active Directory or ODSEE as the directory server during Oracle Identity Manager installation, then after enabling LDAPSync when you run this utility, it will prompt only for the OIM admin password. This OIM admin password is the xelsyadm password.
If you have selected OVD as the directory server during Oracle Identity Manager installation, then after enabling LDAPSync when you run this utility, it will prompt for following passwords:
LDAP admin password- LDAP admin password is the OVD server's admin password.
OIM admin password- LDAP admin password is the xelsyadm password.
To verify the configuration of LDAP with Oracle Identity Manager, complete the following steps:
Ensure that the WebLogic Administration Server is up and running.
Invoke the Oracle Identity Manager Administration Console (http://<host>:<port>/oim), which is deployed on the Administration Server.
In this console, click Search under Configurations -> Manage IT Resource. If the LDAP information is correct, the resource information is displayed.
For more information, see “Managing IT Resources” in the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager.
Create a normal user using the same console.
If a user is created, verify the creation in the chosen LDAP store or OVD using any ldap client.
Note:
Ensure that the chosen Directory server or OVD and Oracle Identity Manager are up and running.
After installing and configuring Oracle Identity Manager Server, you must complete the following manual steps:
Set the XEL_HOME variable in the setenv script (setenv.bat on Windows, and setenv.sh on UNIX) as follows:
On Windows: Open the <IAM_Home>\server\bin\setenv.bat file and search for XEL_HOME variable. Update the path of the XEL_HOME variable to the absolute path of <IAM_Home>\server. For example, if your IDM_Home is the C:\oracle\Middleware\IAM_Home directory, then set XEL_HOME in the setenv.bat file to the C:\oracle\Middleware\IAM_Home\server directory.
On UNIX: Open the <IAM_Home>/server/bin/setenv.sh file and search for XEL_HOME variable.Update the path of the XEL_HOME variable to the absolute path of <IAM_Home>/server. For example, if your IDM_Home is the /test/Middleware/IAM_Home directory, then set XEL_HOME in the setenv.sh file to the /test/Middleware/IAM_Home/server directory.
Follow these steps for setting oamEnabled parameter. You must set oamEnabled parameter to true only if you want to integrate Oracle Identity Manager and Oracle Access Manager at a later time. This procedure applies only if you use Identity Virtualization Library.
Log in into Oracle Enterprise Manager Fusion Middleware Control at
http://adminvhn.mycompany.com:7001/em as user weblogic.
Right click on Oim(11.1.1.3.0), and click System Mbean Browser.
Go to: Application defined MBeans -> com.oracle -> Domain:base_domain -> OVD
There are two AdaptersConfig options. Click on the one that has a plus (+) symbol, indicating a subtree. Then click on OVDAdaptersConfig. You should see CHANGELOG_oid1 and oid1.
Configure oamenabled in both the adapters.
Follow these steps to configure oamenabled in the Changelog adapter:
Click on CHANGELOG_oid1 and keep going down the tree until the very end. You should see changelog with a bean symbol. Double click on changelog.
Click on the operations subtab.
Click on removeParam operation.
Enter oamEnabled in the textbox and click invoke. It should give you a false or a true.
Return to the original page with operations.
Click on AddParam operation.
Edit the names and values to contain oamEnabled and true.
Click invoke to complete the addParam operation.
Follow these steps to configure oamenabled in the Usermanagement adapter:
Click on oid1 and keep going down the tree until the very end. You should see oid1 with a bean symbol. Double click on oid1.
Click on the operations subtab.
Click on removeParam operation.
Enter oamEnabled in the textbox and click invoke. It should give you a false or a true.
Return to the original page with operations.
Click on AddParam operation.
Edit the names and values to contain oamEnabled and true.
Click invoke to complete the addParam operation.
Restart Oracle Identity Manager Managed Server and SOA Managed Server.
LDAP Sync can be enabled at any point after installing and configuring Oracle Identity Manager Server. For more infromation on enabling LDAP Sync after installing and configuring Oracle Identity Manager Server, see "Enabling LDAP Synchronization" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
This topic describes how to install and configure only Oracle Identity Manager Design Console, which is supported on Windows operating systems only.
It includes the following sections:
Perform the installation and configuration in this topic if you want to install Oracle Identity Manager Design Console on a separate Windows machine where Oracle Identity Manager Server is not configured. For more information, see Section 5.4.2.2, "Scenario 1: Oracle Identity Manager Server and Design Console on Different Machines".
Performing the installation and configuration in this section deploys only Oracle Identity Manager Design Console on the Windows operating system.
The installation and configuration in this section depends on the installation of Oracle Identity and Access Management 11g software and on the configuration of Oracle Identity Manager Server. For more information, see Section 3.2.7, "Installing Oracle Identity and Access Management (11.1.1.7.0)" and Section 5.6, "Configuring Oracle Identity Manager Server".
Perform the following steps to install and configure only Oracle Identity Manager Design Console on the Windows operating system:
Ensure that all the prerequisites, described in Section 5.4.1.2, "Prerequisites for Configuring Only Oracle Identity Manager Design Console on a Different Machine", are satisfied. In addition, see Section 5.1, "Important Notes Before You Start Configuring Oracle Identity Manager".
On the Windows machine where Oracle Identity Manager Design Console should be configured, start the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard". The Welcome screen appears.
On the Welcome screen, click Next. The Components to Configure screen appears.
On the Components to Configure screen, select only the OIM Design Console check box. Click Next. The OIM Server Host and Port screen appears.
On the OIM Server Host and Port screen, enter the host name of the Oracle Identity Server Manager Server in the OIM Server Hostname field. In the OIM Server Port field, enter the port number for the Oracle Identity Manager Server on which the Oracle Identity Manager application is running. Click Next. The Configuration Summary screen appears.
The Configuration Summary screen lists the application that you selected for configuration and summarizes your configuration options, such as OIM Server host name and port.
Review this summary and decide whether to start the configuration. If you want to modify any of the configuration settings at this stage, select a topic in the left navigation page and modify your choices. To continue installing this configuration of the Oracle Identity Management Design Console, click Configure.
Note:
Before configuring an application, you can save your configuration settings and preferences in a response file. Response files are text files that you can create or edit in a text editor. You can use response files to perform a silent installation or use as templates or customized settings for your environment. For more information, see Appendix F, "Performing a Silent Installation".
After you click Configure, the Configuration Progress screen appears. A configuration log is saved to the logs directory under Oracle Inventory directory. For information about the log files, see Appendix G, "Installation Log Files". If the Configuration Progress screen displays any errors, click Abort to stop the installation and restart the Oracle Identity Manager Configuration Wizard.
Click Finish.
Note:
If the configuration fails, click Abort to stop the installation and restart the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard".
Complete the following steps after configuring the Oracle Identity Manager Design Console on the Windows operating system:
On the machine where Oracle WebLogic Server is installed (the machine where Oracle Identity Manager Server is installed), create the wlfullclient.jar file as follows:
Use the cd command to move from your present working directory to the <MW_HOME>\wlserver_10.3\server\lib directory.
Ensure that JAVA_HOME is set, as in the following example:
D:\oracle\<MW_HOME>\jdk160_24
To set this variable, right-click the My Computer icon and select Properties. The System Properties screen is displayed. Click the Advanced tab and click the Environment Variables button. The Environment Variables screen is displayed. Ensure that the JAVA_HOME variable in the User Variables section is set to the path of the JDK directory installed on your machine.
After setting the JAVA_HOME variable, select the Path variable in the System Variables section on the same Environment Variables screen, and click Edit. The Edit System Variable dialog box is displayed. In the variable value field, enter the complete path to your JAVA_HOME, such as D:\oracle\<MW_HOME>\jdk160_24, preceded by a semicolon (;). The semicolon is used as the delimiter for multiple paths entered in this field.
After verifying the values, click OK.
Use the following steps to create a wlfullclient.jar file for JDK 1.6 client application:
Change directories to the server/lib directory.
cd WL_HOME/server/lib
Use the following command to create wlfullclient.jar in the server/lib directory:
java -jar wljarbuilder.jar
This command generates the wlfullclient.jar file.
Copy the wlfullclient.jar file to the <IAM_Home>\designconsole\ext\ directory on the machine where Design Console is configured.
Ensure that the Administration Server and the Oracle Identity Manager Managed Server are started. For information about starting the servers, see Starting the Stack.
Start the Design Console client by running the xlclient.cmd executable script, which is available in the <IAM_Home>\designconsole\ directory.
Log in to the Design Console with your Oracle Identity Manager user name and password.
To update the xlconfig.xml file and start the Design Console on a new port as opposed to what was set during configuration, complete the following steps:
In a text editor, open the <IAM_Home>\designconsole\config\xlconfig.xml file.
Edit the following tags:
ApplicationURL
java.naming.provider.url
Change the port number.
Restart the Design Console.
Note:
You do not have to perform this procedure during installation. It is required if you want to change ports while using the product. You must ensure that the Oracle Identity Manager server port is changed to this new port before performing these steps.
To configure the Design Console to use SSL, complete the following steps:
Add the WebLogic Server jar files required to support SSL by copying the webserviceclient+ssl.jar file from the <WL_HOME>/server/lib directory to the <IAM_Home>/designconsole/ext directory.
Use the server trust store in Design Console as follows:
Log in to the Oracle WebLogic Administration Console using the WebLogic administrator credentials.
Under Domain Structure, click Environment > Servers. The Summary of Servers page is displayed.
Click on the Oracle Identity Manager server name (for example, oim_server1). The Settings for oim_server1 is displayed.
Click the Keystores tab.
From the Trust section, note down the path and file name of the trust keystore.
Set the TRUSTSTORE_LOCATION environment variable as follows:
If Oracle Identity Manager Design Console and Oracle Identity Manager Server are installed and configured on the same machine, set the TRUSTSTORE_LOCATION environment variable to the location of the trust keystore that you noted down.
For example, setenv TRUSTSTORE_LOCATION=/test/DemoTrust.jks
If Oracle Identity Manager Design Console and Oracle Identity Manager Server are installed and configured on different machines, copy the trust keystore file to the machine where Design Console is configured. Set the TRUSTSTORE_LOCATION environment variable to the location of the copied trust keystore file on the local machine.
If the Design Console was installed without SSL enabled, complete the following steps:
Open the <IAM_Home>/designconsole/config/xlconfig.xml file in a text editor.
Edit the <ApplicationURL> entry to use HTTPS, T3S protocol, and SSL port to connect to the server, as in the following example:
<ApplicationURL>https://<host>:<sslport>/xlWebApp/loginWorkflowRenderer.do</ApplicationURL>
Note:
For a clustered installation, you can send an https request to only one of the servers in the cluster, as shown in the following element:
<java.naming.provider.url>t3s://<host>:<sslport></java.naming.provider.url>
Save the file and exit.
Specify Java permissions for Crypto-J librairies as follows:
Open the IAM_HOME/designconsole/config/xl.policy file in a text editor.
Add the following at the end and save the file.
grant codeBase "file:MW_HOME/modules/cryptoj.jar"{permission java.security.AllPermission;};
This topic describes how to install and configure only Oracle Identity Manager Remote Manager. It includes the following sections:
Perform the installation and configuration in this topic if you want to install Oracle Identity Manager Remote Manager on a separate machine. For more information, see Section 5.4.2.3, "Scenario 2: Oracle Identity Manager Server and Remote Manager on Different Machines".
Performing the installation and configuration in this section deploys only Oracle Identity Manager Remote Manager.
The installation and configuration in this section depends on the installation of Oracle Identity and Access Management 11g software and on the configuration of Oracle Identity Manager Server. For more information, see Section 3.2.7, "Installing Oracle Identity and Access Management (11.1.1.7.0)" and Section 5.4.1.3, "Prerequisites for Configuring Only Oracle Identity Manager Remote Manager on a Different Machine".
Perform the following steps to install and configure only Oracle Identity Manager Remote Manager:
Ensure that all the prerequisites, described in Section 5.4.1.3, "Prerequisites for Configuring Only Oracle Identity Manager Remote Manager on a Different Machine", are satisfied. In addition, see Section 5.1, "Important Notes Before You Start Configuring Oracle Identity Manager".
On the machine where Oracle Identity Manager Remote Manager should be configured, start the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard". The Welcome screen appears.
On the Welcome screen, click Next. The Components to Configure screen appears.
On the Components to Configure screen, select only the OIM Remote Manager check box. Click Next. The Remote Manager screen appears.
On the Remote Manager screen, enter the service name in the Service Name field. Oracle Identity Manager Remote Manager will be registered under this service name. The service name is used with the Registry URL to a build fully qualified service name, such as rmi://host:RMI Registry Port/service name.
In the RMI Registry Port field, enter the port number on which the RMI registry should be started. The default port number is 12345.
In the Listen Port (SSL) field, enter the port number on which a secure socket is opened to listen to client requests. The default port number is 12346. Click Next. The Keystore Password screen appears.
On the KeyStore Password screen, in the KeyStore Password field, enter a new password for the keystore. A valid password contains 6 to 30 characters, begins with an alphabetic character, and uses only alphanumeric characters and special characters like Dollar ($), Underscore (_), and Pound (#). The password must contain at least one number. In the Confirm KeyStore Password field, enter the new password again. Click Next. The Configuration Summary screen appears.
The Configuration Summary screen lists the application that you selected for configuration and summarizes your configuration options, such as Remote Manager Service Name, RMI Registry Port, and Remote Manager Listen Port (SSL).
Review this summary and decide whether to start the configuration. If you want to modify any of the configuration settings at this stage, select a topic in the left navigation page and modify your choices. To continue installing this configuration of the Oracle Identity Manager Remote Manager, click Configure.
Note:
Before configuring an application, you can save your configuration settings and preferences in a response file. Response files are text files that you can create or edit in a text editor. You can use response files to perform a silent installation or use as templates or customized settings for your environment. For more information, see Appendix F, "Performing a Silent Installation".
After you click Configure, the Configuration Progress screen appears. A configuration log is saved to the logs directory under Oracle Inventory directory. For information about the log files, see Appendix G, "Installation Log Files". If the Configuration Progress screen displays any errors, click Abort to stop the installation and restart the Oracle Identity Manager Configuration Wizard.
Click Finish.
Note:
Oracle Identity Manager Server certificates, such as xlserver.cert, are created in the DOMAIN_HOME/config/fmwconfig/ directory. You can use these certificates if you require server-side certificates for configuring Oracle Identity Manager Remote Manager.
If the configuration fails, click Abort to stop the installation and restart the Oracle Identity Manager Configuration Wizard, as described in Section 5.5, "Starting the Oracle Identity Manager 11g Configuration Wizard".
Before you can verify the Oracle Identity Manager installation, ensure that the following servers are up and running:
Administration Server for the domain in which the Oracle Identity Manager application is deployed
Managed Server hosting Oracle Identity Manager
Managed Server hosting the Oracle SOA 11g suite
You can verify your Oracle Identity Manager installation by:
Checking the Oracle Identity Manager Server URL, such as http://<Hostname>:<Port>/oim/faces/faces/pages/Admin.jspx.
Checking the Identity Management shell, such as http://<Hostname>:<Port>/admin/faces/pages/Admin.jspx. This shell is used for Users and Role Management tasks.
Checking the Oracle Identity Manager Self Service URL, such as http://<Hostname>:<Port>/oim.
Verifying the configuration between Oracle Identity Manager and Oracle SOA (BPEL Process Manager) as follows:
Log in to the Oracle Identity Manager Administration Console, with xelsysadm:
http://<host>:<oim_port>/oim/faces/pages/Admin.jspx
Create a Request, such as modifying a user profile.
Log in to the SOA Infrastructure to verify whether the composite applications are displayed.
http://<host>:<bpel_port>/soa-infra
Log in to the BPEL Worklist application, with xelsysadm:
http://<host>:<soa_port>/integration/worklistapp
In the list of tasks, verify whether the request has come for approval.
Click on the task, and click Approve in the Actions tab.
Click on the refresh icon. The request comes back. Approve it again.
Go to http://<host>:<oim_port>/oim/faces/pages/Admin.jspx and verify whether the request is completed.
Go to http://<host>:<oim_port>/admin/faces/pages/Admin.jspx and verify whether the user profile is modified.
Logging in to the Design Console, xelsysadm, and the appropriate password. A successful login indicates that the installation was successful.
Starting the Remote Manager service by running remotemanager.sh or remotemanager.bat, as appropriate. (remotemanager.sh on UNIX or remotemanager.bat on Windows resides in your Oracle Home directory under a folder named remote_manager.
For information about setting up integration between Oracle Identity Manager and Oracle Access Manager, see "Integrating Oracle Access Manager and Oracle Identity Manager" in the Oracle Fusion Middleware Integration Guide for Oracle Access Manager.
Oracle Identity Manager supports the following languages:
Arabic, Brazilian Portuguese, Czech, Danish, Dutch, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Slovak, Spanish, Swedish, Thai, Traditional Chinese, and Turkish
Diagnostic Dashboard is a stand-alone application that helps you validate some of the Oracle Identity Manager prerequisites and installation.You must have the appropriate system administrator permissions for your Application Server and Oracle Identity Manager environments to use this tool. You need DBA-level permissions to execute some database-related tests.
Note:
The Diagnostic Dashboard and Oracle Identity Manager must be installed on the same application server.
For more information about installing and using the Diagnostic Dashboard for Oracle Identity Manager, see the "Working with the Diagnostic Dashboard" topic in the Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager.
After installing Oracle Identity Manager, refer to Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.