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

Part Number E12002-11
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
PDF · Mobi · ePub

14 Understanding Domain Extension Scenarios

This chapter describes the scenarios in which an existing Oracle Identity Management domain can be extended to support new Oracle Identity Management products.

It includes the following topics:

14.1 Overview

When you extend an Oracle Identity Management domain, you are configuring new products in the existing domain to support new Oracle Identity Management products.

For example, you can extend an Oracle Identity Management 11.1.1.5.0 domain to support Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, or Oracle Identity Navigator. The existing Oracle Identity Management 11.1.1.5.0 domain may contain one or more of the various combinations of Oracle Identity Management products, such as Oracle Internet Directory, Oracle Virtual Directory, Oracle Directory Services Manager, Oracle Identity Federation, or Oracle Directory Integration Platform.

In addition, you can extend an Oracle Identity Management domain that contains any of the various combinations of Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, and Oracle Identity Navigator.

Note:

Note that the existing domain must have been created using the Oracle Identity Management 11g Release 1 (11.1.1) Installer and configured using the Oracle Identity Management 11g Configuration Wizard. You cannot extend an existing domain for Oracle Identity Management components if the domain was created by another program, such as the Oracle Fusion Middleware 11g Oracle SOA Suite Installer or the Oracle Fusion Middleware Configuration Wizard.

14.2 Important Notes Before You Begin

Before you start installing and configuring Oracle Identity Management products in any of the scenarios discussed in this chapter, keep the following points in mind:

14.3 Domain Extension Scenarios

The following lists the scenarios in which you can extend an existing Oracle Identity Management domain to support new Oracle Identity Management products:

14.3.1 Extending an Oracle Identity Management 11.1.1.5.0 Domain to Support OIM, OAM, OAAM or OIN on the Local Machine

You can extend an existing Oracle Identity Management 11.1.1.5.0 domain (containing OID,OVD,ODSM,ODIP, and OIF) to support Oracle Identity and Access Management 11.1.1.5.0 products.

This scenario involves the following tasks:

  1. Installing the latest version of Oracle SOA 11g Suite (for Oracle Identity Manager only), as described in Installing the Latest Version of Oracle SOA Suite (Oracle Identity Manager Users Only).

  2. Installing the Oracle Identity Management Suite under your existing Middleware Home, as described in Installing Oracle Identity and Access Management (11.1.1.5.0).

  3. Creating and loading the necessary schemas for the new components to be added, as described in Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU).

  4. Launching the Oracle Fusion Middleware Configuration Wizard <IAM_Home>/common/bin/config.sh script on UNIX (<IAM_Home>\common\bin\config.cmd on Windows).

  5. Selecting the Extend an existing WebLogic domain option on the Welcome screen.

  6. Selecting the existing Oracle Identity Management 11.1.1.5.0 domain on the Select a WebLogic Domain Directory screen.

  7. Selecting the required domain templates on the Select Extension Source screen to support Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, or Oracle Identity Navigator.

  8. Modifying JDBC component schemas, configuration of Managed Servers, Deployments and Services, and so on.

  9. Starting the Administration Server on the local machine, as described in Starting or Stopping the Oracle Stack.

  10. Starting Managed Servers, as described in Starting or Stopping the Oracle Stack.

Note:

When you extend an existing WebLogic domain to support Oracle Identity Manager, you should restart the Administration Server before launching the Oracle Identity Manager Configuration Wizard to configure Oracle Identity Manager Server.

14.3.2 Understanding Joint Configuration and Domain Extension Scenarios for OIM, OAM, OAAM, and OIN on the Local Machine

It is assumed that you have installed the latest versions of Oracle WebLogic Server and the Oracle Identity Management Suite. For Oracle Identity Manager, you should have installed the latest version of Oracle SOA 11g Suite. You should have created and loaded the necessary schemas by using Oracle Fusion Middleware Repository Creation Utility (RCU).

You should have configured a new domain to support any of the various combinations of Oracle Access Manager (OAM), Oracle Adaptive Access Manager (OAAM), and Oracle Identity Navigator (OIN).

For example, you can configure Oracle Identity Manager in an existing Oracle Identity Management domain that contains Oracle Access Manager or Oracle Identity Navigator.

Several combinations are possible, based on your Oracle Identity Management environment and deployment.

This scenario involves the following tasks:

  1. Creating and loading the necessary schemas for the new components to be added, as described in Creating Database Schema Using the Oracle Fusion Middleware Repository Creation Utility (RCU).

  2. Launching the Oracle Fusion Middleware Configuration Wizard <IAM_Home>/common/bin/config.sh script on UNIX (<IAM_Home>\common\bin\config.cmd on Windows).

  3. Selecting the Extend an existing WebLogic domain option on the Welcome screen.

  4. Selecting the existing Oracle Identity Management domain (the domain that contains any of the various combinations of Oracle Access Manager, Oracle Adaptive Access Manager, and Oracle Identity Navigator) on the Select a WebLogic Domain Directory screen.

  5. Selecting the required domain templates on the Select Extension Source screen to support Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, or Oracle Identity Navigator. The choice of domain templates in this step depends on the component you are trying to configure in the same domain.

  6. Modifying JDBC component schemas, configuration of Managed Servers, Deployments and Services, and so on.

  7. Starting the Administration Server on the local machine, as described in Starting or Stopping the Oracle Stack.

  8. Starting Managed Servers, as described in Starting or Stopping the Oracle Stack.

Note:

When you extend an existing WebLogic domain to support Oracle Identity Manager, you should restart the Administration Server before launching the Oracle Identity Manager Configuration Wizard to configure Oracle Identity Manager Server.

14.4 Starting the Administration Server on the Local Machine

In some scenarios, you may want to install the Administration Server on one machine and component-specific Managed Servers on another machine. You must start the Administration Server on the machine where it is installed before you can create and run Managed Servers on the remote machine.

14.5 Creating Managed Servers on a Remote Machine

Before you can create and run Managed Servers on a remote machine, you must install Oracle WebLogic Server and Oracle Identity Management Suite on the remote machine. Then you must use the pack and unpack commands to create Managed Servers on the remote machine.

14.5.1 Installing Oracle WebLogic Server and Oracle Identity Management Suite on the Remote Machine

You must install Oracle WebLogic Server and Oracle Identity Management Suite on the remote machine.

After this installation, you can create and start Managed Servers on the remote machine, as described in the following topic.

14.5.2 Creating and Starting Managed Servers on a Remote Machine

To create and start a Managed Server on a remote machine, complete the following steps:

  • On the local machine where the domain is configured and the Administration Server is created, use the pack command located in the \common\bin directory under your IDM_Home directory to create a Managed Server template that contains a subset of the files in a domain that are required to create a Managed Server domain directory hierarchy on a remote machine.

    The -managed={true} parameter of the pack command specifies whether the template is to be used to create Managed Servers on remote machines.

  • Ensure that the Administration Server is up and running on the local machine.

  • On the remote machine, use the unpack command located in the \common\bin directory under your IDM_Home directory to create the Managed Server domain directory on the remote machine.

Note:

For Oracle Identity Manager users only:

If you want to start the SOA Server on a remote machine, then you must manually copy the composite files from the <DOMAIN_HOME>/soa/autodeploy directory on the local machine to the <DOMAIN_HOME>/soa/autodeploy directory on the remote machine after running the unpack command on the remote machine. If the <DOMAIN_HOME>/soa/autodeploy directory does not exist on the remote machine, you must create this directory before copying the composite files.

For more information, see the topic "Creating and Starting a Managed Server on a Remote Machine" in the guide Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands. In addition, see the topic "Extending WebLogic Domains" in the guide Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.