To find a certified JDK, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

After you identify the Oracle JDK for the current Oracle Fusion Middleware release, you can download an Oracle JDK from the following location on Oracle Technology Network:

http://www.oracle.com/technetwork/java/index.html

Be sure to navigate to the download for the Java SE JDK.

You must install the JDK in the following locations:

• On the shared storage device, where it will be accessible from each of the application tier host computers, install the JDK in the location specified in File System and Directory Variables Used in This Guide.

• On the local storage device for each of the Web tier host computers. The Web tier host computers, which reside in the DMZ, do not necessarily have access to the shared storage on the application tier.

• On the local storage device for each of the directory tier host computers, in case of the directory hosts not utilizing the shared storage.

For more information about the recommended location for the JDK software, see Understanding the Recommended Directory Structure for an Enterprise Deployment.

Review the contents of the installation log files to make sure that no problems were encountered. For a description of the log files and where to find them, see Understanding Installation Log Files in Installing Software with the Oracle Universal Installer.

The contents of your installation vary based on the options that you select during the installation.

The addition of Oracle Identity Governance adds the following directory and sub-directories. Use the ls --format=single-column command to verify the directory structure.

IGD_ORACLE_HOME/

OPatch
cfgtoollogs
coherence
em
idm
inventory
jdeveloper
mft
oep
oraInst.loc
oracle_common
osb
oui
soa
wlserver

idm/

clone
common
connectors
designconsole
idmdiag
idmtools
jlib
libovd
mbeans
modules
oam
oic
opam-connectors
plugins
remote_manager
schema
server
upgrade

For more information about the directory structure you should see after installation, see What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

You can also view the contents of your Oracle home by using the viewInventory script. See Viewing the contents of an Oracle home in Installing Software with the Oracle Universal Installer.

Follow the instructions in this section to create and configure the domain for the topology.

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Create a new domain.

In the Domain Location field, specify the value of the IGD_ASERVER_HOME variable, as defined in File System and Directory Variables Used in This Guide.

Tip:

More information about the other options on this screen of the Configuration Wizard, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 2   Selecting the Configuration Templates

Select Oracle Identity Manager - 12.2.1.4.0[idm], the following template will be automatically selected:

• Oracle Enterprise Manager - 12.2.1.4.0[em]

• Oracle WSM Policy Manager - 12.2.1.4.0[oracle_common]

• Oracle JRF - 12.2.1.4.0[oracle_common]

• WebLogic Coherence Cluster Extension - 12.2.1.4.0[wlserver]

Tip:

More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 3   Configuring High Availability Options

This screen appears for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. After you select HA Options for a cluster, all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply HA options (that is, the Configuration Wizard creates the JDBC stores and configures ASM for them).

Note:

Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an oracle database and makes resources available for all the servers in the cluster. So, the Configuration Wizard steps assume that the JDBC persistent stores are used along with Automatic Service Migration.

If, for any reason, you want to use Files Stores, you can retain the default values for TLOGs and JMS persistent store options in this screen and configure them in a shared location later. See Configuring TLOGs File Persistent Store in a Shared Folder. Shared location is required to resume JMS and HA in a failover scenario.

You can also configure TLOGs and JMS persistent stores manually in a post step. For information about the differences between JDBC and Files Stores, and for specific instructions to configure them manually, see JDBC Persistent Stores vs. File Persistent Stores.

On the High Availability Options screen:

• Select Enable Automatic Service Migration with Database Leasing.

• Set JTA Transaction Log Persistence to JDBC TLog Store.

• Set JMS Server Persistence to JMS JDBC Store.

• Click Next.

Task 4   Selecting the Application Home Location

On the Application Location screen, specify the value of the APPLICATION_HOME variable, as defined in File System and Directory Variables Used in This Guide.

Tip:

More information about the options on this screen can be found in Application Location in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 5   Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.

Make a note of the user name and password specified on this screen; you will need these credentials later to boot and connect to the domain's Administration Server.

Click Next.

Task 6   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

• Select the Oracle Hotspot JDK in the JDK field.

Selecting Production Mode on this screen gives your environment a higher degree of security, requiring a user name and password to deploy applications and to start the Administration Server.

Tip:

More information about the options on this screen, including the differences between development mode and production mode, can be found in Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. See Creating the boot.properties File.

Click Next.

Task 7   Specifying the Database Configuration Type

On the Database Configuration Type screen:

• Select RCU Data to activate the fields on this screen.

  The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.

• Verify that Vendor is Oracle and Driver is *Oracle's Driver (Thin) for Service Connections; Versions: Any.

• Verify that Connection Parameters is selected.

Note:

If you choose to select Manual Configuration on this screen, you will have to manually fill in the parameters for your schema on the JDBC Component Schema screen.

After you select RCU Data, fill in the fields as shown in the following table:

Field	Description
Host Name	Enter the Single Client Access Name (SCAN) Address for the Oracle RAC database, which you entered in the Enterprise Deployment Workbook. For information about the Enterprise Deployment Workbook, see Using the Enterprise Deployment Workbook.
DBMS/Service	Enter the service name for the Oracle RAC database appropriate for this domain where you will install the product schemas. For example: iamedg.example.com Specify the service name based on the value configured earlier in the Preparing the Database for an Enterprise Deployment section.
Port	Enter the port number on which the database listens. For example, 1521.
Schema Owner Schema Password	Enter the user name and password for connecting to the database's Service Table schema. This is the schema user name and password that was specified for the Service Table component on the "Schema Passwords" screen in RCU (see Creating the Database Schemas). The default user name is prefix_STB, where prefix is the custom prefix that you defined in RCU.

Click Get RCU Configuration when you are finished specifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Click Next if the connection to the database is successful.

Tip:

More information about the RCU Data option can be found in Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

More information about the other options on this screen can be found in Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Specifying JDBC Component Schema Information

Verify that the values on the JDBC Component Schema screen are correct for all schemas.

The schema table should be populated, because you selected Get RCU Data on the previous screen. As a result, the Configuration Wizard locates the database connection values for all the schemas required for this domain.

At this point, the values are configured to connect to a single-instance database. However, for an enterprise deployment, you should use a highly available Real Application Clusters (RAC) database, as described in Preparing the Database for an Enterprise Deployment.

In addition, Oracle recommends that you use an Active GridLink datasource for each of the component schemas. For more information about the advantages of using GridLink data sources to connect to a RAC database, see Database Considerations in the High Availability Guide.

To convert the data sources to GridLink:

1. Select all the schemas by selecting the checkbox at in the first header row of the schema table.

2. Click Convert to GridLink and click Next.

Task 9   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in following table.

Element	Description and Recommended Value
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521)
ONS Host and Port	In the ONS Host field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, 6200).
Enable Fan	Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.

For more information about specifying the information on this screen, as well as information about how to identify the correct SCAN address, see Configuring Active GridLink Data Sources with Oracle RAC in the High Availability Guide.

You can also click Help to display a brief description of each field on the screen.

Click Next.

Task 10   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections you have just configured.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

Tip:

More information about the other options on this screen can be found in Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard

Click Next.

Task 11   Entering Credentials

Enter the credentials you wish to use for the Oracle Identity Governance components. You have the choice of choosing both a username and a password for the various objects.

• keystore: Set the username to "keystore" and the password to the password you wish to use for all automatically created keystores.

• OIMSchemaPassword: Set the username to the OIM schema which you created in the earlier sections. For example, IGD_OIM (username) and its associated password.

• Sysadmin: This is the administrative user you will use for OIM. This is typically xelsysadm, but can be anything. Set the password to a value you wish to use for this account.

• WebLogicAdminKey: This is the domain admin username and password. For example, weblogic.

Click Next.

Task 12   Keystore

Use this screen to specify details about the keystore to be used in the domain.

For a typical enterprise deployment, you can leave the default values.

See Keystore in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 13   Selecting Advanced Configuration

Note:

This is not required for Access infrastructure.

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

• Administration Server

  This is required to properly configure the listen address of the Administration Server.

• Node Manager

  This is required to configure Node Manager.

• Topology

  This is required to add, delete, or modify the Settings for Server Templates, Managed Servers, Clusters, Virtual Targets, and Coherence.

• Domain Frontend Host Capture:

  This allows you to specify the public entry point for OIM.

Note:

When using the Advanced Configuration screen in the Configuration Wizard, if any of the above options are not available on the screen, then return to the Templates screen, and be sure you selected the required templates for this topology.

Click Next.

Task 14   Configuring the Administration Server Listen Address

On the Administration Server screen:

1. In the Server Name field, retain the default value - AdminServer.

2. In the Listen Address field, enter the virtual host name that corresponds to the VIP of the ADMINVHN that you procured in Procuring Resources for an Enterprise Deployment and enabled in Preparing the Host Computers for an Enterprise Deployment.

   For more information on the reasons for using the ADMINVHN virtual host, see Reserving the Required IP Addresses for an Enterprise Deployment.

3. In the Listen Port field, enter the port number to access the administration server. This guide recommends you to use the default port 7101 for Governance.

   Leave the other fields at their default values. In particular, be sure that no server groups are assigned to the Administration Server.

Click Next.

Task 15   Configuring Node Manager

Select Per Domain Default Location as the Node Manager type, then specify the following Node Manager credentials you will use to connect to the Node Manager:

• Username: This is the user name used to connect to the Node Manager. For example, admin.

• Password and Confirm Password: Enter the password you wish to associate with the Node Manager username.

Tip:

For more information about the options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

For more information about per domain and per host Node Manager implementations, see About the Node Manager Configuration in a Typical Enterprise Deployment.

For information about Node Manager configurations, see Configuring Node Manager on Multiple Machines in Administering Node Manager for Oracle WebLogic Server.

Click Next.

Task 16   Configuring Managed Servers

Use the Managed Servers screen to create two new Managed Servers:

1. Click the Add button to create a new Managed Server.

2. Specify WLS_WSM1 in the Server name column.

3. In the Listen Address column, enter OIMHOST1.

   Be sure to enter the host name that corresponds to OIMHOST1; do not use the IP address.

4. In the Listen Port column, enter WSM_PORT – 7010.

5. In the Server Groups drop-down list, select JRF-MAN-SVR and WSMPM-MAN-SVR.

   These server groups ensure that the Oracle JRF and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers that you are creating.

   Server groups target Fusion Middleware applications and services to one or more servers by mapping defined groups of application services to each defined server group. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. See Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.

   Note:

   Nonce caching for Oracle Web Services is initialized automatically by the WSM-CACHE-SVR server group and is suitable for most custom applications. This initialization is automatically performed in SOA, OSB, and other FMW servers that run JRF and create a coherence cluster. Nonce is a unique number that can be used only once in a SOAP request and is used to prevent replay attacks. Nonce caching naturally scales with the number of added Managed Servers that run Web service applications.

   For information about advanced caching configurations, see Caching the Nonce with Oracle Coherence in Securing Web Services and Managing Policies with Oracle Web Services Manager, which provides additional guidance for the use of nonce caching and the WSM-CACHE-SVR server-group in custom WLS servers.

6. Repeat this process to create a second Managed Server named WLS_WSM2.

   For the Listen Address, enter OIMHOST2. For the Listen Port, enter 7010. Apply the same server groups that you applied to the first managed server to the WLS_WSM2.

The Managed Server names suggested in this procedure (WLS_WSM1 and WLS_WSM2) are referenced throughout this document; if you choose different names then be sure to replace them as needed.

On the Managed Servers screen, a new Managed Server for Oracle SOA Suite and Oracle Identity Manger appears in the list of servers. This server was created automatically by the Oracle SOA Suite configuration template you selected in Table 8-3.

Perform the following tasks to modify the default Oracle SOA Suite and Oracle Identity Manager Managed Server and create a second Managed Server:

1. Rename the default Managed Server to oim_server1 to WLS_OIM1.

   Rename the default Managed Server soa_server1 to WLS_SOA1.

2. Click Add to create a new Oracle Identity Governance Managed Server, and name it WLS_OIM2.

   Tip:

   The server names recommended here will be used throughout this document; if you choose different names, be sure to replace them as needed.

3. Click Add to create a new Oracle SOA Suite Managed Server, and name it WLS_SOA2.

4. Use the information in Oracle Identity Governance Managed Server Details to fill in the rest of the columns for each Oracle Identity Governance Managed Server.

For more information about the options on the Managed Server screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

Server Name	Listen Address	Listen Port	Enable SSL	SSL Listen Port	Server Groups
WLS_OIM1	OIMHOST1	14000	No	Disabled	OIM-MGD-SVRS
WLS_OIM2	OIMHOST2	14000	No	Disabled	OIM-MGD-SVRS
WLS_SOA1	OIMHOST1	8001	No	Disabled	SOA-MGD-SVRS
WLS_SOA2	OIMHOST2	8001	No	Disabled	SOA-MGD-SVRS

Click Next.

Task 17   Configuring a Cluster

In this task, you create a cluster for each set of Managed Servers. You can then target the Oracle Identity Governance and Oracle SOA Suite components to the relevant cluster.

Create the following clusters:

• OIM_Cluster

• SOA_Cluster

• WSM-PM_Cluster

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify the cluster name in the Cluster Name field.

3. Repeat the steps to create all of the clusters.

Note:

By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.

Click Next.

For more information about the options on this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 18   Assigning Server Templates

Click Next .

Task 19   Configuring Dynamic Servers

Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.

1. Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.

2. Confirm the Server Template selection is Unspecified.

3. Click Next.

Note:

This screen will not be displayed if you are creating the Access Infrastructure.

Task 20   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign your managed servers to the clusters you have just created. At the end of this you will have the following assignments:

Cluster	Managed Servers
OIM_Cluster	WLS_OIM1 WLS_OIM2
SOA_Cluster	WLS_SOA1 WLS_SOA2
WSM-PM_Cluster	WLS_WSM1 WLS_WSM2

1. In the Clusters pane, select the cluster to which you want to assign the servers.

2. In the Servers pane, assign the Managed Servers to the cluster as in the table above, using one of the following methods:

   • Click on the Managed Server to select it, and then click on the right arrow to move it beneath the selected cluster in the Clusters pane.

   • Double-click on the Managed Server to move it beneath the selected cluster in the clusters pane.

3. Repeat to assign each of the Managed Server to the respective cluster.

4. Click Next.

For more information about the options on this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 21   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain.

In the Cluster Listen Port, enter 9991.

Note:

For Coherence licensing information, Oracle Coherence Products in Oracle Fusion Middleware Licensing Information User Manual.

Click Next.

Task 22   Creating Machines

Use the Machines screen to create new machines in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.

You must create a machine even if your topology contains just the Administration Server.

1. Select the Unix Machine tab.

2. Click the Add button to create new UNIX machines.

   Use the values in Values to Use When Creating Unix Machines to define the Name and Node Manager Listen Address of each machine.

3. Verify the port in the Node Manager Listen Port field.

   The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

Table 14-2 Values to Use When Creating Unix Machines

Name	Node Manager Listen Address	Node Manager Listen Port
ADMINHOST	Enter the value of the ADMINVHN variable.	5556
OIMHOST1	The value of the OIMHOST1 host name variable or OIMHOST1 alias. For example, OIMHOST1.example.com.	5556
OIMHOST2	The value of the OIMHOST2 host name variable or OIMHOST2 alias. For example, OIMHOST2.example.com.	5556

Note:

If you are installing OIM on the same host as Oracle Access Management (OAM), ensure that the Node Manager ports are unique to each deployment.

Tip:

More information about the options on this screen can be found in Machines in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 23   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Oracle Identity Governance Managed Servers to the corresponding machines in the domain.

Assign the machines as shown in the following table:

Servers	Machines
AdminHost	AdminServer
WLS_OIM1 WLS_SOA1 WLS_WSM1	OIMHOST1
WLS_OIM2 WLS_SOA2 WLS_WSM2	OIMHOST2

1. In the Machines pane, select the machine to which you want to assign the servers.

2. In the Servers pane, assign the Managed Servers to the machine as in the table above, using one of the following methods:

   • Click on the Managed Server to select it, and then click on the right arrow to move it beneath the selected machines in the machines pane.

   • Double-click on the Managed Server to move it beneath the selected machine in the machines pane.

3. Repeat to assign each of the Managed Server to the respective machine.

4. Click Next.

For more information about the options on this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 24   Creating Virtual Targets

Click Next.

Task 25   Creating Partitions

Click Next.

Task 26   Configuring Domain Front End Host

In the Domain Front End host screen you specify the main entry point for OIM. This will equate to the name on the load balancer. For example, set Plain to http://prov.example.com.

Note:

Even though you are specifying this value it will never be used.

SSL: https://prov.example.com

Default: SSL

Click Next.

Task 27   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Domain creation will not begin until you click Create.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 28   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the following items about the domain you just configured:

• Domain Location

• Administration Server URL

You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Administration Server.

Click Finish to dismiss the Configuration Wizard.

..

Follow the instructions in this section to create and configure the domain for the topology.

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Create a new domain.

In the Domain Location field, specify the value of the ASERVER_HOME variable, as defined in File System and Directory Variables Used in This Guide.

Tip:

More information about the other options on this screen of the Configuration Wizard, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 2   Selecting the Configuration Templates

On the Templates screen, make sure that Create Domain Using Product Templates is selected, then select the following templates:

• Oracle Identity Manager - 12.2.1.4.0[oim]

• Oracle Enterprise Manager - 12.2.1.4.0[em]

  Selecting this template automatically selects the following dependencies:

  • Oracle JRF - 12.2.1.4.0[oracle_common]

  • WebLogic Coherence Cluster Extension - 12.2.1.4.0[wlserver]

• Oracle WSM Policy Manager - 12.2.1.4.0[oracle_common]

Tip:

More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 3   Configuring High Availability Options

This screen appears for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. After you select HA Options for a cluster, all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply these HA options.

On the High Availability Options screen, complete the following steps:

1. Verify that Enable Automatic Service Migration is not selected.

2. Verify that Default Persistent Store is selected as the JTA Transaction Log Persistence option.

3. Select JDBC Store as the JMS Service Persistence option.

You can configure only JMS Server persistence for Dynamic Clusters by using the Configuration Wizard. You cannot configure Service Migration and JTA Transaction Logs Persistence for Dynamic Clusters by using the Configuration Wizard, you have to configure them manually. Instructions are covered in later chapters of this guide.

Click Next.

Task 4   Selecting the Application Home Location

On the Application Location screen, specify the value of the APPLICATION_HOME variable, as defined in File System and Directory Variables Used in This Guide.

Tip:

More information about the options on this screen can be found in Application Location in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 5   Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.

Make a note of the user name and password specified on this screen; you need to use these credentials later to boot and connect to the Administration Server domain.

Click Next.

Task 6   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

• Select only Production in the Domain Mode field.

• Select the Oracle Hotspot JDK in the JDK field.

Selecting Production Mode on this screen gives your environment a higher degree of security, requiring a user name and password to deploy applications and to start the Administration Server.

Tip:

More information about the options on this screen, including the differences between development mode and production mode, can be found in Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. See Creating the boot.properties File.

Click Next.

Task 7   Specifying the Database Configuration Type

On the Database Configuration Type screen:

• Select RCU Data to activate the fields on this screen.

  The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema. This connection automatically retrieves schema information for the schemas to configure the domain.

• Verify that Vendor is Oracle and Driver is *Oracle's Driver (Thin) for Service Connections; Versions: Any.

• Verify that Connection Parameters is selected.

Note:

If you choose to select Manual Configuration on this screen, you have to manually fill in the parameters for the schema on the JDBC Component Schema screen.

After you select RCU Data, fill in the fields as shown in the following table:

Field	Description
Host Name	Enter the Single Client Access Name (SCAN) Address for the Oracle RAC database, which you entered in the Enterprise Deployment Workbook.
DBMS/Service	Enter the service name for the Oracle RAC database where you will install the product schemas. For example: orcl.example.com Be sure to specify the common service name that is used to identify all the instances in the Oracle RAC database; do not use the host-specific service name.
Port	Enter the port number on which the database listens. For example, 1521.
Schema Owner Schema Password	Enter the user name and password for connecting to the database's Service Table schema. The schema user name and password that was specified for the Service Table component on the "Schema Passwords" screen in RCU (see Creating the Database Schemas) is used here. The default user name is prefix_STB, where prefix is the custom prefix that you defined in RCU.

Click Get RCU Configuration when you are finished specifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Click Next if the connection to the database is successful.

Tip:

More information about the RCU Data option can be found in Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

More information about the other options on this screen can be found in Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard

Task 8   Specifying JDBC Component Schema Information

Verify that the values on the JDBC Component Schema screen are correct for all schemas.

The schema table is populated because you selected Get RCU Data on the previous screen. As a result, the Configuration Wizard locates the database connection values for all the schemas required for this domain.

At this point, the values are configured to connect to a single-instance database. However, for an enterprise deployment, you must use a highly available Real Application Clusters (RAC) database, as described in Preparing the Database for an Enterprise Deployment.

In addition, Oracle recommends that you use an Active GridLink datasource for each of the component schemas. For more information about the advantages of using GridLink data sources to connect to a RAC database, see Database Considerations in theHigh Availability Guide.

To convert the data sources to GridLink:

1. Select all the schemas by selecting the checkbox at in the first header row of the schema table.

2. Click Convert to GridLink and click Next.

Task 9   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in following table.

Element	Description and Recommended Value
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521)
ONS Host and Port	In the ONS Host field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, 6200).
Enable Fan	Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.

For more information about specifying the information on this screen, as well as information about how to identify the correct SCAN address, see Configuring Active GridLink Data Sources with Oracle RAC in the High Availability Guide.

You can also click Help to display a brief description of each field on the screen.

Click Next.

Task 10   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections you have configured.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

Tip:

More information about the other options on this screen can be found in Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard

Click Next.

Task 11   Entering Credentials

Enter the credentials you wish to use for the Oracle Identity Governance components. You have the choice of choosing both a username and a password for the various objects.

• keystore: Set the username to keystore and the password to the password you wish to use for all automatically created keystores.

• OIMSchemaPassword: Set the username to the OIM schema which you created in the earlier sections. For example, IGD_OIM (username) and its associated password.

• Sysadmin: This is the administrative user you will use for OIM. This is typically xelsysadm, but can be anything. Set the password to a value you wish to use for this account.

• WebLogicAdminKey: This is the domain admin username and password. For example, weblogic.

Click Next.

Task 12   Keystore

Use this screen to specify details about the keystore to be used in the domain.

For a typical enterprise deployment, you can leave the default values.

See Keystore in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 13   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

• Administration Server

  This is required to configure the listen address of the Administration Server.

• Node Manager

  This is required to configure Node Manager.

• Topology

  This is required to add, delete, or modify the Settings for Server Templates, Managed Servers, Clusters, Virtual Targets, and Coherence.

Note:

When using the Advanced Configuration screen in the Configuration Wizard:

• If any of the options are not available on the screen, then return to the Templates screen, and ensure that you have selected the required templates for this topology.

• Do not select the Domain Frontend Host Capture advanced configuration option. Later, you have to configure the frontend host property for specific clusters, rather than for the domain.

Click Next.

Task 14   Configuring the Administration Server Listen Address

On the Administration Server screen:

1. In the Server Name field, retain the default value: AdminServer.

2. In the Listen Address field, enter the virtual host name that corresponds to the VIP of the ADMINVHN that you procured in Procuring Resources for an Enterprise Deployment and enabled in Preparing the Host Computers for an Enterprise Deployment.

   For more information on the reasons for using the ADMINVHN virtual host, see Reserving the Required IP Addresses for an Enterprise Deployment.

3. In the Listen Port field, enter the port number to access the administration server. This guide recommends you to use the default port 7001 for Access and 7101 for Governance.

   Leave the other fields at their default values. In particular, be sure that no server groups are assigned to the Administration Server.

Click Next.

Task 15   Configuring Node Manager

Select Per Domain Default Location as the Node Manager type, then specify the following Node Manager credentials you will use to connect to the Node Manager:

• Username: This is the user name used to connect to the Node Manager. For example, admin.

• Password and Confirm Password: Enter the password you wish to associate with the Node Manager username.

Tip:

For more information about the options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

For more information about per domain and per host Node Manager implementations, see About the Node Manager Configuration in a Typical Enterprise Deployment.

For additional information, see Configuring Node Manager on Multiple Machines in Administering Node Manager for Oracle WebLogic Server.

Click Next.

Task 16   Configuring Managed Servers

On the Managed Servers screen, a new Managed Server for Oracle Identity Governance appears in the list of servers. These servers were created automatically by the Oracle Identity Governance configuration template you selected in File System and Directory Variables Used in This Guide.

Static Managed Server definitions are not needed for dynamic cluster configurations. To remove the default Managed Servers, complete the following steps:

1. Click on the Managed Server.

2. Click Delete.

3. Repeat for each of the Managed Servers.

4. Click Next.

Task 17   Configuring a Cluster

In this task, you create a cluster of Managed Servers to which you can target the Oracle Identity Governance software.

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify OIM_Cluster in the Cluster Name field.

3. From the Dynamic Server Groups drop-down list, select OIM-DYN-CLUSTER.

4. Create a second cluster called SOA_Cluster and assign the Dynamic Server group SOA-DYN-CLUSTER.

5. Create a third cluster called WSM-PM_Cluster and assign the Dynamic Server group WSMPM-DYN-CLUSTER.

Note:

By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.

Tip:

More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Tips:

For more information about the options on this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 18   Assigning Server Templates

Use the Server Templates screen to configure the template:

1. Verify that wsmpm-server-template is selected in the Name field.

2. Specify 7009 in the Listen Port field.

3. Leave the Enable SSL option unchecked.

4. Verify OIM-server-template is listed in the Name field.

5. Specify 13999 in the Listen Port field.

6. Leave the Enable SSL option unchecked.

7. Specify 8000 for the Listen Port for template soa-server-template.

8. Click Next .

Task 19   Configuring Dynamic Servers

Use the Dynamic Clusters screen to configure the following clusters:

Cluster Name	Server Name Prefix	Server Template	Dynamic Cluster Size	Machine Name Match Expression	Calculated Machine Names
oim_cluster	WLS_OIM	oim-server-template	2	OIMHOST*	Selected
soa_cluster	WLS_SOA	soa-server-template	2	OIMHOST*	Selected
WSM-PM_Cluster	WLS_WSM	wsmpm-server-template	2	OIMHOST*	Selected

Complete the following steps on this screen:

1. Verify OIM_Cluster is listed in the Cluster Name field.

2. Specify WLS_OIM in the Server Name Prefix field.

3. From the Server Template drop-down list, select OIM-server-template.

4. Specify 2 in the Dynamic Server Count field.

5. Specify OIMHOST* in the Machine Name Match Expression field.

6. Select Calculated Machine Names, Calculated Listen Ports, and Dynamic Cluster fields.

   Note:

   Dynamic clusters with the Calculated Listen Port option selected will have incremental port numbers for each dynamic managed server that is created automatically: dynamic server 1 will use Listen Port+1, dynamic server 2 will use Listen Port+2.

   Since the Listen Port configured is 13999 and calculated ports is checked, OIM dynamic servers will use the following:

   • WLS_OIM1:14000

   • WLS_OIM2:14001

   Since the SOA Listen Port configured is 8000 and calculated ports is checked, SOA dynamic servers will use the following:

   • WLS_SOA1:8001

   • WLS_SOA2:8002

   Since the Listen Port that is configured is 7009 and calculated ports is checked, WSMPM dynamic servers use the following ports:

   • WLS_WSM1: 7010

   • WLS_WSM2: 7011

7. Repeat the steps 1 through 6 for each of the clusters to be created.

8. Click Next.

Note:

The Configuration Wizard does not allow you to specify a specific listen address for dynamic servers. For information about setting a specific listen address for WebLogic servers that are members of a dynamic cluster, see Configuring Listen Addresses in Dynamic Cluster Server Templates.

Task 20   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain.

In the Cluster Listen Port, enter 9991.

Note:

For Coherence licensing information, Oracle Coherence Products in Oracle Fusion Middleware Licensing Information User Manual.

Click Next.

Task 21   Creating Machines

Use the Machines screen to create new machines in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.

1. Select the Unix Machine tab.

2. Click the Add button to create the new UNIX machines.

   Use the values in Table 14-3 to define the Name and Node Manager Listen Address of each machine.

3. Verify the port in the Node Manager Listen Port field.

   The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

Table 14-3 Values to Use When Creating Unix Machines

Name	Node Manager Listen Address	Node Manager Listen Port
ADMINHOST	Enter the value of the ADMINVHN variable.	5556
OIMHOST1	The value of the OIMHOST1 host name variable or OIMHOST1 alias. For example, OIMHOST1.example.com.	5556
OIMHOST2	The value of the OIMHOST2 host name variable or OIMHOST2 alias. For example, OIMHOST2.example.com.	5556

Note:

The name of the machine should reflect the value that you have specified in the Machine Match Expression field with the addition of a sequential number. That is, if you have specified OIMHOST* in the Machine Match Expression field, then the names of your machines should be OIMHOST1, OIMHOST2, and so on.

Tip:

More information about the options on this screen can be found in Machines in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 22   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign any statically defined managed servers to the appropriate machines. Servers that are part of a dynamic cluster are assigned to the calculated machine names automatically.

Assign AdminServer to the ADMINHOST machine.

Click Next.

Task 23   Creating Virtual Targets

Click Next.

Task 24   Creating Partitions

Click Next.

Task 25   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Click Update to execute the domain extension.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 26   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Domain creation begins when you click Create.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Click Next.

Task 27   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows the following items about the domain you have configured:

• Domain Location

• Administration Server URL

You must make a note of both items because you need them later; the domain location is required to access the scripts that are used to start the Administration Server.

Click Finish to dismiss the Configuration Wizard.

These users will be created as a part of Preparing an Existing LDAP Directory.

• Admin User DN:

  cn=weblogic_iam,cn=users,dc=example,dc=com
  

• Admin Group DN:

  cn=WLSAdministrators,cn=groups,dc=example,dc=com

• Product-specific LDAP Connector User:

  cn=oimLDAP,cn=systemids,dc=example,dc=com

  This is the user that you use to connect WebLogic Managed Servers to the LDAP authentication provider. This user must have permissions to read and write to the Directory Trees:

  cn=users,dc=example,dc=com
  cn=groups,dc=example,dc=com

  cn=reserve,dc=example,dc=com

cn=orclFAUserReadPrivilegeGroup,cn=groups,dc=example,dc=com
cn=orclFAUserWritePrivilegeGroup,cn=groups,dc=example,dc=com
cn=orclFAGroupReadPrivilegeGroup,cn=groups,dc=example,dc=com
cn=orclFAGroupWritePrivilegeGroup,cn=groups,dc=example,dc=com