This topic describes how to configure Oracle Access Manager (OAM) in a Oracle Identity Management domain that has Oracle Identity Manager (OIM) and Oracle Identity Navigator (OIN) installed. It includes the following sections:
Perform the configuration in this topic if you want to install Oracle Access Manager in an environment where Oracle Identity Manager and Oracle Identity Navigator are already installed. You can use Oracle Identity Navigator to discover and launch the Oracle Access Manager Console and the Oracle Identity Manager Consoles (Oracle Identity Administration Console, Oracle Identity Manager Self Service Console, and Oracle Identity Manager Advanced Administration Console) from within the Oracle Identity Navigator user interface. At a later time, you can also set up integration between Oracle Identity Manager and Oracle Access Manager, as described in Integration Between OIM and OAM.
Performing the configuration in this section deploys the following:
Managed Server for Oracle Access Manager
Oracle Access Manager Console on the existing Administration Server
The configuration in this section depends on the following:
Oracle WebLogic Server.
Installation of the Oracle Identity Management 11g software.
Installation of the latest version of Oracle SOA Suite
Database schemas for Oracle Identity Manager, Oracle SOA Suite, and Oracle Access Manager. For more information, see Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU).
Installation and configuration of Oracle Identity Manager with Oracle Identity Navigator in a new WebLogic domain.
Perform the following steps to configure Oracle Access Manager in a WebLogic domain that contains Oracle Identity Manager and Oracle Identity Navigator:
Configure Oracle Identity Manager and Oracle Identity Navigator in a new WebLogic domain, as described in OIM and OIN in a New WebLogic Domain. A new WebLogic domain to support Oracle Identity Manager and Oracle Identity Navigator is created in the
<MW_HOME>\user_projects\domains directory (on Windows). On UNIX, the domain is created in the
<Oracle_IDM2>/common/bin/config.sh script (on UNIX). (
<Oracle_IDM2>\common\bin\config.cmd on Windows). The Oracle Fusion Middleware Configuration Wizard appears.
On the Welcome screen, select the Extend an existing WebLogic domain option. Click Next.
On the Select a WebLogic Domain Directory screen, browse to the directory that contains the WebLogic domain in which you configured Oracle Identity Manager and Oracle Identity Navigator. Click Next. The Select Extension Source screen appears.
On the Select Extension Source screen, select the Oracle Access Manager with Database Policy Store - 22.214.171.124.0 [Oracle_IDM2] domain configuration option.
After selecting the domain configuration options, click Next. The Configure JDBC Data Sources Screen is displayed. Configure the
oamDS data source, as required. After the test succeeds, the Configure JDBC Component Schema screen is displayed.
On the Configure JDBC Component Schema screen, select a component schema, such as the OIM Infrastructure Schema, the SOA Infrastructure Schema, the User Messaging Service Schema, the OWSM MDS Schema, the OIM MDS Schema, or the SOA MDS Schema, that you want to modify.
You can set values for Schema Owner, Schema Password, Database and Service, Host Name, and Port. 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 Managed Servers, Clusters, and Machines, Deployments and Services, and JMS File Store. Select the relevant check boxes and click Next.
Optional: Configure Managed Servers, as required.
Optional: Configure Clusters, as required.
For more information about configuring clusters for Oracle Identity 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.
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.
Tip:Before configuring a machine, use the
pingcommand to verify whether the machine or host name is accessible.
Optional: Assign the Administration Server to a machine.
Optional: Select Deployments, such as applications and libraries, and Services to target them to a particular cluster or server.
Optional: Configure JMS File Store, as required.
On the Configuration Summary screen, review the domain configuration, and click Extend to start extending the domain.
Your existing WebLogic domain with Oracle Identity Manager and Oracle Identity Navigator is extended to support Oracle Access Manager.