12 Extending the Domain to Include ODSM

This chapter describes how to extend the Identity Management domain to include Oracle Directory Services Manager.

This chapter includes the following topics:

Section 12.1, "Overview of Extending the Domain to Include ODSM"
Section 12.2, "Prerequisites"
Section 12.3, "Extending the Oracle WebLogic Domain IDMDomain"
Section 12.4, "Expanding the ODSM Cluster"
Section 12.5, "Provisioning the Managed Servers in the Managed Server Directory"
Section 12.6, "Validating the Application Tier Configuration"
Section 12.7, "Backing Up the ODSM Configuration"

12.1 Overview of Extending the Domain to Include ODSM

The Application Tier consists of multiple computers hosting the Oracle Directory Services Manager and Oracle Access Manager instances. In the complete configuration, requests are balanced among the instances on the Application Tier computers to create a high-performing, fault tolerant application environment.

Oracle Directory Services Manager is a unified graphical user interface (GUI) for managing instances of Oracle Internet Directory and Oracle Virtual Directory. Oracle Directory Services Manager enables you to configure the structure of the directory, define objects in the directory, add and configure users, groups, and other entries.

This chapter describes how to install and configure Oracle Directory Services Manager (ODSM).

12.2 Prerequisites

Ensure that the system, patch, kernel and other requirements are met. These are listed in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management manual in the Oracle Fusion Middleware documentation library for the platform and version you are using.
If you plan on provisioning the Instance Home or the Managed Server domain directory on shared storage, ensure that the appropriate shared storage volumes are mounted on IDMHOST1 as described in Section 4.3, "About Recommended Locations for the Different Directories."
Ensure that port 7006 (ODSM_PORT) is not in use by any service on the computer by issuing these commands for the operating system you are using. If a port is not in use, no output is returned from the command.

On Linux:
```
netstat -an | grep "7006"
```
where 7006 is (ODSM_PORT). If the port is in use (if the command returns output identifying the port), you must free it.

On Linux:

Remove the entries for ODSM_PORT in the /etc/services file and restart the services, as described in Section 21.1, "Starting and Stopping Oracle Identity Management Components," or restart the computer.

12.3 Extending the Oracle WebLogic Domain IDMDomain

Follow these steps to install and configure Oracle Directory Services Manager in the domain IDMDomain:

Create a file containing the ports used by ODSM. On Disk1 of the installation media, locate the file stage/Response/staticports.ini. Copy it to a file called odsm_ports.ini. Delete all entries in odsm_ports.ini except for ODSM Server Port No. Change the values of ODSM Server Port No. to 7006 (ODSM_PORT in Section A.3).

Note:

If the port name in the file is slightly different from those listed in this step, use the name in the file.
Start the Oracle Identity Management 11g Configuration Wizard by running the config.sh script located under the IDM_ORACLE_HOME/bin directory on IDMHOST1. For example:
```
IDM_ORACLE_HOME/bin/config.sh
```
On the Welcome screen, click Next.
On the Select Domain screen, select Extend Existing Domain and enter the domain details:
- Hostname: ADMINVHN.mycompany.com
- Port: 7001 (WLS_ADMIN_PORT)
- User Name: weblogic
- User Password: user password
Click Next.

A dialog box with the following message appears:

The selected domain is not a valid Identity Management domain or the installer
cannot determine if it is a valid domain. If you created the domain using the
Identity Management installer, you can ignore this message and continue. If
you did not create the domain using the Identity Management installer, refer
to the Identity Management documentation for information on how to verify the
domain is valid.

Click Yes to continue.

This is a benign warning that you can ignore.

On the Specify Installation Location screen, specify the following values (the values for the Oracle Middleware Home Location and the Oracle Home Directory fields are prefilled. The values default to the Middleware home and Oracle home previously installed on IDMHOST1:
- Oracle Middleware Home Location: IAM_MW_HOME
- Oracle Home Directory: idm
- WebLogic Server Directory: IAM_MW_HOME/wlserver_10.3
- Oracle Instance Location: ODS_ORACLE_INSTANCE
- Oracle Instance Name: ODS_ORACLE_INSTANCE
Click Next.
On the Specify Email for Security Updates screen, specify these values:
- Email Address: Provide the email address for your My Oracle Support account.
- Oracle Support Password: Provide the password for your My Oracle Support account.
- Check the check box next to the I wish to receive security updates via My Oracle Support field.
Click Next.
On the Configure Components screen, select Management Components - Oracle Directory Services Manager.

Deselect all the other components.

Select the Clustered check box.

Click Next.
On the Configure Ports screen, you use the odsm_ports.ini file you created in Step 1 to specify the ports to be used. This enables you to bypass automatic port configuration.
1. Select Specify Ports using a Configuration File.
2. In the file name field specify odsm_ports.ini.
3. Click Save, then click Next.
On the Installation Summary screen, review the selections to ensure that they are correct (if they are not, click Back to modify selections on previous screens), and click Configure.
On the Configuration Progress screen, multiple configuration assistants are launched in succession; this process can be lengthy. Wait until it completes.
On the Installation Complete screen, click Finish to confirm your choice to exit.

12.4 Expanding the ODSM Cluster

Follow these steps to extend the WebLogic Server domain and install and configure Oracle Directory Service Manager on IDMHOST2:

Ensure that the system, patch, kernel and other requirements are met. These are listed in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management manual in the Oracle Fusion Middleware documentation library for the platform and version you are using.
If you plan on provisioning the Instance Home or the Managed Server domain directory on shared storage, ensure that the appropriate shared storage volumes are mounted on IDMHOST2 as described in Section 4.3, "About Recommended Locations for the Different Directories."
Ensure that port number 7006 (ODSM_PORT) is not in use by any service on the computer by issuing this command for the operating system you are using. If a port is not in use, no output is returned from the command.

On Linux:
```
netstat -an | grep "7006"
```
If the port is in use (if the command returns output identifying the port), you must free it.

On Linux:

Remove the entries for port 7006 (ODSM_PORT) in the /etc/services file if the port is in use by a service and restart the services, as described in Section 21.1, "Starting and Stopping Oracle Identity Management Components," or restart the computer.
Start the Oracle Identity Management 11g Configuration Wizard by running the config.sh script located under the IDM_ORACLE_HOME/bin directory on IDMHOST2. For example: IDM_ORACLE_HOME/bin
On the Welcome screen, click Next.
On the Select Domain screen, select the Expand Cluster option and specify these values:
- Hostname: ADMINVHN.mycompany.com
- Port: 7001 (WLS_ADMIN_PORT)
- UserName: weblogic
- User Password: password for the webLogic user
Click Next.

A dialog box with the following message appears:

The selected domain is not a valid Identity Management domain or the installer
cannot determine if it is a valid domain. If you created the domain using the
Identity Management installer, you can ignore this message and continue. If you
did not create the domain using the Identity Management installer, refer to the
Identity Management documentation for information on how to verify the domain
is valid.

Click YES to continue.

This is a benign warning that you can safely ignore.

On the Specify Installation Location screen, specify the following values. The values for the Oracle Middleware Home Location and the Oracle Home Directory fields are prefilled. The values default to the Middleware home and Oracle home previously installed on IDMHOST1:
- Oracle Middleware Home Location: IAM_MW_HOME
- Oracle Home Directory: idm
- WebLogic Server Directory: IAM_MW_HOME /wlserver_10.3
- Oracle Instance Location: ODS_ORACLE_INSTANCE
- Oracle Instance Name: ODS_ORACLE_INSTANCE
Click Next.
On the Email for Security Updates screen, specify these values:
- Email Address: Provide the email address for your My Oracle Support account.
- Oracle Support Password: Provide the password for your My Oracle Support account.
- Check the check box next to the I wish to receive security updates via My Oracle Support field.
Click Next.
On the Configure Components screen, de-select all the products and then click Next.
On the Configure Ports screen, you use the odsm_ports.ini file you created in Section 12.3, "Extending the Oracle WebLogic Domain IDMDomain" to specify the ports to be used. This enables you to bypass automatic port configuration.
1. Select Specify Ports using a Configuration File.
2. In the file name field specify odsm_ports.ini.
3. Click Save, then click Next.
On the Installation Summary screen, review the selections to ensure that they are correct (if they are not, click Back to modify selections on previous screens), and click Configure.
On the Configuration Progress screen, multiple configuration assistants are launched in succession; this process can be lengthy. Wait until it completes.
On the Installation Complete screen, click Finish to confirm your choice to exit.

12.5 Provisioning the Managed Servers in the Managed Server Directory

This section provides the steps to provision the Managed Server on the local disk. Proceed as follows:

Stop the ODS instances on both IDMHOST1 and IDMHOST2. Follow the steps in Section 21.1, "Starting and Stopping Oracle Identity Management Components"

On IDMHOST1, pack the Managed Server domain using the pack command located under the ORACLE_COMMON_HOME/common/bin directory. Make sure to pass -managed=true flag to pack the Managed Server. Type:

ORACLE_COMMON_HOME/common/bin/pack.sh -managed=true -domain=path_to_adminServer_domain -template=templateName.jar -template_name=templateName

For example

ORACLE_COMMON_HOME/common/bin/pack.sh -managed=true -domain=ASERVER_HOME -template=managedServer.jar -template_name=ManagedServer_Template

Unpack the Managed Server to the managed server directory on IDMHOST1 using the unpack command located under the ORACLE_COMMON_HOME /common/bin directory.

ORACLE_COMMON_HOME/common/bin/unpack.sh -domain=path_to_domain_on_localdisk -template=templateName.jar -app_dir=path_to_appdir_on_localdisk -overwrite_domain=true

For example:

ORACLE_COMMON_HOME/common/bin/unpack.sh -domain=MSERVER_HOME -template=managedServer.jar -app_dir=MSERVER_HOME/applications -overwrite_domain=true

Copy the Managed Server template directory from IDMHOST1 to IDMHOST2.

Unpack the Managed Server to the managed server directory on IDMHOST2 using the unpack command located under the ORACLE_COMMON_HOME/common/bin directory.

ORACLE_COMMON_HOME/common/bin/unpack.sh -domain=path_to_domain_on_localdisk -template=templateName.jar -app_dir=path_to_appdir_on_localdisk

For example:

ORACLE_COMMON_HOME/common/bin/unpack.sh -domain=/MSERVER_HOME -template=managedServer.jar -app_dir=MSERVER_HOME/applications

Delete the ASERVER_HOME/servers/wls_ods1 directory on IDMHOST1 and the ASERVER_HOME/servers/wls_ods2 directory on IDMHOST2.

These directories are created by the Oracle Universal Installer when the domain is originally configured and are no longer required after the provisioning the Managed Server to the managed server directory.
Start the managed servers wls_ods1 and wls_ods2 as described in Section 21.1, "Starting and Stopping Oracle Identity Management Components."

12.6 Validating the Application Tier Configuration

Validate the Application Tier configuration as follows:

12.6.1 Validating Browser Connection to ODSM Site

Follow these steps to validate that you can connect the Oracle Directory Services Manager site in a browser:

In a web browser, verify that you can connect to Oracle Directory Services Manager (ODSM) at:
```
http://HOSTNAME.mycompany.com:port/odsm
```
For example, on IDMHOST1, enter this URL, where 7006 is ODSM_PORT in Section A.3:
```
http://IDMHOST1.mycompany.com:7006/odsm
```
and on IDMHOST2, enter this URL:
```
http://IDMHOST2.mycompany.com:7006/odsm
```
In a web browser, verify that you can access ODSM through the load balancer address:

http://ADMIN.mycompany.com/odsm

12.6.2 Validating ODSM Connections to Oracle Internet Directory

Validate that Oracle Directory Services Manager can create connections to Oracle Internet Directory.

Create a connection to the Oracle Internet Directory on each ODSM instance separately. Even though ODSM is clustered, the connection details are local to each node. Proceed as follows:

Launch Oracle Directory Services Manager from IDMHOST1:
```
http://IDMHOST1.mycompany.com:7006/odsm
```
Create a connection to the Oracle Internet Directory virtual host by providing the following information in ODSM:
- Server: OIDSTORE.mycompany.com
- Port: 636 (LDAP_LBR_SSL_PORT)
- Enable the SSL option
- User: cn=orcladmin
- Password: ldap-password
Launch Oracle Directory Services Manager from IDMHOST2.

Follow Step b to create a connection to Oracle Internet Directory from IDMHOST2
```
http://IDMHOST2.mycompany.com:7006/odsm
```
Create a connection to the Oracle Internet Directory virtual host by providing the corresponding information in ODSM

Note:

Accept the certificate when prompted.

12.7 Backing Up the ODSM Configuration

Back up the Web Tier and the WebLogic Domain, as described in Section 21.6.3, "Performing Backups During Installation and Configuration."