|Oracle® Fusion Middleware Installation Guide for Oracle Identity Management
11g Release 1 (11.1.1)
Part Number E12002-05
This topic describes how to configure Oracle Adaptive Access Manager (OAAM) in an existing Oracle Identity Management domain that contains Oracle Access Manager (OAM), Oracle Identity Manager (OIM), and Oracle Identity Navigator (OIN).
It includes the following sections:
Perform the configuration in this topic if you want to install Oracle Adaptive Access Manager in an environment where you may want to set up integration between Oracle Identity Manager and Oracle Adaptive Access Manager. You may use Oracle Access Manager for Single Sign-On and access management. Oracle Identity Navigator enables you to discover and launch Consoles for these products from within the Oracle Identity Navigator user interface.
Performing the configuration in this section deploys the following:
Managed Server for Oracle Adaptive Access Manager
Oracle Adaptive 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.
Database schema for Oracle Adaptive Access Manager. For more information about schemas specific to Oracle Adaptive Access Manager, see Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU).
To configure Oracle Adaptive Access Manager in an existing Oracle Identity Management domain that contains Oracle Access Manager, Oracle Identity Manager, and Oracle Identity Navigator, complete the following steps:
Ensure that Oracle Access Manager, Oracle Identity Manager, and Oracle Identity Navigator are configured in a new WebLogic domain, as described in OIM, OAM, and OIN in a New WebLogic Domain.
<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 domain directory that contains Oracle Access Manager, Oracle Identity Manager, and Oracle Identity Navigator. Click Next. The Select Domain Source screen appears.
On the Select Extension Source screen, ensure that the Extend my domain automatically to support the following products: option is selected. Select Oracle Adaptive Access Manager Admin Server - 184.108.40.206.0 [Oracle_IDM2], which is mandatory.
When you select the Oracle Adaptive Access Manager Admin Server - 220.127.116.11.0 [Oracle_IDM2] option, the Oracle Identity Navigator - 18.104.22.168.0 [Oracle_IDM2] option is also selected, by default.
In addition, you can select Oracle Adaptive Access Manager - Server - 22.214.171.124.0 [Oracle_IDM2], which is optional. Click Next. The Configure JDBC Component Schema screen appears.
The screen lists the following component schemas:
OAAM Admin Schema
User Messaging Service
OAAM Admin MDS Schema
OIM MDS Schema
OWSM MDS Schema
SOA MDS Schema
On the Configure JDBC Component Schema screen, select a component 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, such as
oaam_server1 (default value).
On the Configuration Summary screen, review the domain configuration, and click Extend to start extending the domain.
Your existing Oracle Identity Management domain with Oracle Access Manager, Oracle Identity Manager, and Oracle Identity Navigator is extended to support Oracle Adaptive Access Manager.