1 About the Oracle Identity and Access Management Installation

The standard installation for Oracle Identity and Access Management described in this guide creates the standard topology, which represents a sample starting topology for this product.

Note:

The product Oracle Identity Manager is referred to as Oracle Identity Manager (OIM) and Oracle Identity Governance (OIG) interchangeably in the guide.

About Oracle Identity and Access Management

Oracle Identity and Access Management 12c (12.2.1.4.0) suite has two components: Oracle Access Management (OAM) and Oracle Identity Governance (OIG)

Note:

The product Oracle Identity Manager is referred to as Oracle Identity Manager (OIM) and Oracle Identity Governance (OIG) interchangeably in the guide.

For information about Oracle Access Management 12c (12.2.1.4.0), and it’s features, refer to the following topics in the Administrator's Guide for Oracle Access Management:

For information about Oracle Identity Governance 12c (12.2.1.4.0), refer to the following topics in the Administering Oracle Identity Governance:

About the Modes of Installation

Oracle Identity and Access Management supports two modes of installation — standalone and collocated.

  • Standalone Mode of Installation:

    Standalone mode refers to the type of installation that is managed independently of WebLogic Server. However, this mode is NOT supported for Oracle Identity Governance and Oracle Access Management 12c (12.2.1.4.0). The only component that you can install using standalone mode is the Oracle Identity Governance Design Console.

  • Collocated Mode of Installation:

    Collocated mode refers to the type of installation that is managed through WebLogic Server. This mode is supported for both Oracle Identity Governance and Oracle Access Management. To install Oracle Identity and Access Management in collocated mode, you must also install the necessary dependant softwares.

The following table shows the modes supported for installing and configuring the components of Oracle Identity and Access Management, and their respective dependant softwares:

Table 1-1 Modes of Installation and Dependant Softwares for Oracle Identity and Access Management

Component Standalone Mode Collocated Mode
N/A Supported? Softwares Required Supported? Softwares Required

Oracle Access Management

No

-

Yes

Product Software:

  • Oracle Identity and Access Management 12c (12.2.1.4.0)

Dependant Software:

  • Oracle Fusion Middleware Infrastructure 12c (12.2.1.4.0)

Oracle Identity Governance

No

Only Oracle Identity Governance Design Console can be configured in standalone mode.

Product Software Required for Design Console:

  • Oracle Identity and Access Management 12c (12.2.1.4.0)

Yes

Product Software:

  • Oracle Identity and Access Management 12c (12.2.1.4.0)

Dependant Softwares:

  • Oracle Fusion Middleware Infrastructure 12c (12.2.1.4.0)

  • Oracle SOA Suite 12c (12.2.1.4.0)

Note:

A quickstart installer is available for Oracle Identity Governance 12c (12.2.1.4.0), which installs Infrastructure, Oracle SOA Suite, and Oracle Identity and Access Management 12c (12.2.1.4.0) in one go. In other words, no separate installers are required for installing all the three softwares. If you wish to use the simplified installation process for Oracle Identity Governance, see Installing and Configuring Oracle Identity Governance Using Simplified Installation Process.

For more information about the product distributions and the instructions for installing the dependant softwares, see About Product Distributions.

Using the Standard Installation Topology as a Starting Point

The standard installation topology is a flexible topology that you can use as a starting point in production environments.

The information in this guide helps you to create a standard installation topology for Oracle Identity and Access Management. If required, you can later extend the standard installation topology to create a secure and highly available production environment, see Next Steps After Configuring the Domain.

The standard installation topology represents a sample topology for this product. It is not the only topology that this product supports. See About the Standard Installation Topology in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.

About the Oracle Identity and Access Management Standard Installation Topology

This topology represents a standard WebLogic Server domain that contains an Administration Server and one or more clusters containing one or more Managed Servers.

The following figure shows the standard installation topology for Oracle Identity and Access Management.

See Table 1-2 for information on elements of this topology.

Figure 1-1 Standard Topology for Oracle Identity and Access Management

Description of Figure 1-1 follows
Description of "Figure 1-1 Standard Topology for Oracle Identity and Access Management"

For Oracle Access Management configuration instructions, see Configuring Oracle Access Management Domain.

For Oracle Identity Governance configuration instructions, see Configuring the Oracle Identity Governance Domain.

About Elements in the Standard Installation Topology Illustration

The standard installation topology typically includes common elements.

The following table describes all elements of the topology illustration:

Table 1-2 Description of Elements in Standard Installation Topologies

Element Description and Links to Related Documentation
APPHOST A standard term used in Oracle documentation to refer to the machine that hosts the application tier.
DBHOST A standard term used in Oracle documentation to refer to the machine that hosts the database.
WebLogic Domain A logically related group of Java components (in this case, the Administration Server, Managed Servers, and other related software components).

See What Is an Oracle WebLogic Server Domain? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

Administration Server Central control entity of a WebLogic domain. It maintains configuration objects for that domain and distributes configuration changes to Managed Servers.

See What Is the Administration Server? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

Enterprise Manager The Oracle Enterprise Manager Fusion Middleware Control is a primary tool used to manage a domain.

See Oracle Enterprise Manager Fusion Middleware Control in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

Cluster A collection of multiple WebLogic Server instances running simultaneously and working together.

See Overview of Managed Servers and Managed Server Clusters in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

Machine A logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between the Managed Servers and the Node Manager. In order to start or stop the Managed Servers using the Node Manager, associate the Managed Servers with a machine.
Managed Server A host for your applications, application components, web services, and their associated resources.

See Overview of Managed Servers and Managed Server Clusters in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

Infrastructure A collection of services that include the following:
  • Metadata repository (MDS) contains the metadata for Oracle Fusion Middleware components, such as the Oracle Application Developer Framework. See What Is the Metadata Repository? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

  • Oracle Application Developer Framework (Oracle ADF).

  • Oracle Web Services Manager (OWSM).

Using This Document to Extend an Existing Domain

The procedures in this guide describe how to create a new domain. The assumption is that no other Oracle Fusion Middleware products are installed on your system.

If you have installed and configured other Oracle Fusion Middleware products on your system (for example, Fusion Middleware Infrastructure, with a domain that is up and running) and wish to extend the same domain to include Oracle Identity and Access Management, see Installing Multiple Products in the Same Domain.