Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Identity Management
11g Release 1 (11.1.1)

Part Number E12002-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

19.4 OAM and OIN in a New WebLogic Domain

This topic describes how to configure Oracle Access Manager (OAM) and Oracle Identity Navigator (OIN) in a new WebLogic administration domain. It includes the following sections:

19.4.1 Appropriate Deployment Environment

Perform the configuration in this topic if you want to install Oracle Oracle Access Manager in an environment where you want to add other Oracle Identity Management products at a later time.

19.4.2 Components Deployed

Performing the installation and configuration in this section deploys the following:

  • Administration Server

  • Managed Server for Oracle Access Manager

  • Oracle Access Manager Console and Oracle Identity Navigator application on the Administration Server

19.4.3 Dependencies

The installation and configuration in this section depends on the following:

19.4.4 Procedure

Perform the following steps to install and configure Oracle Access Manager and Oracle Identity Navigator in a new WebLogic administration domain:

  1. Ensure that all the prerequisites, listed in Prerequisites, are satisfied. In addition, see Important Notes Before You Begin.

  2. Run the <Oracle_IDM2>/common/bin/config.sh script. (<Oracle_IDM2>\common\bin\config.cmd on Windows). The Oracle Fusion Middleware Configuration Wizard appears.

  3. On the Welcome screen, select the Create a new WebLogic domain option. Click Next. The Select Domain Source screen is displayed.

  4. On the Select Domain Source screen, select the Generate a domain configured automatically to support the following products: option.

  5. Select the following domain configuration options:

    • Oracle Access Manager with Database Policy Store - 11.1.1.3.0 [Oracle_IDM2]

      Note:

      When you select the Oracle Access Manager with Database Policy Store - 11.1.1.3.0 [Oracle_IDM2] option, the Oracle JRF - 11.1.1.0 [oracle_common] option is also selected, by default.
    • Oracle Identity Navigator - 11.1.1.3.0 [Oracle_IDM2]

  6. After selecting the domain configuration options, click Next. The Specify Domain Name and Location screen is displayed.

  7. On the Specify Domain Name and Location screen, enter a name and location for the domain to be created. In addition, enter a location to store applications for the domain. Click Next. The Configure Administrator User Name and Password screen is displayed.

  8. 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 is displayed.

  9. Choose JRockit SDK 160_17_R28.0.0-679 and Production Mode in the Configure Server Start Mode and JDK screen of the Oracle Fusion Middleware Configuration Wizard. Click Next. If you selected Oracle Access Manager with Database Policy Store - 11.1.1.3.0 [Oracle_IDM1] option on the Select Extension Source screen, the Configure JDBC Data Sources Screen is displayed. Configure the oamDS data source, as required. After the test succeeds, the Select Optional Configuration screen is displayed.

  10. On the Select Optional Configuration screen, you can configure Administration Server, Managed Servers, Clusters, and Machines, Deployments and Services, and RDBMS Security Store. Select the relevant check boxes and click Next.

    • Optional: Configure Administration Server, as required.

    • 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 ping command 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 RDBMS Security Store, as required.

  11. On the Configuration Summary screen, review the domain configuration, and click Create to start creating the domain.

The WebLogic domain with your configuration attributes is created.