Skip Headers
Oracle® Fusion Middleware Patching Guide
11g Release 1 (11.1.1.7.0)

Part Number E16793-25
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
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

8 Patching an Oracle Identity Management High Availability Environment

This chapter describes how to patch your existing Oracle Identity Management high availability environment to the latest version. To do so, complete the following tasks:

See:

Types of Oracle Identity Management Environments in the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management for information on the topologies.

Note:

Review Chapter 5, "Post-Patching Procedures" before completing the tasks in this chapter. You may need to perform additional tasks.

Note:

Back up your Oracle software, inventory, schema, and domain before applying this patch set, or before making any other changes to your existing Oracle software. Refer to your product administrator's guide for instructions on backing up your Oracle software and inventory. For more information, see "Advanced Administration: Backup and Recovery" in the Oracle Fusion Middleware Administrator's Guide.

8.1 Task 1: Stopping Servers and System Components

Before updating Oracle Identity Management, you must stop the following servers and components:

8.1.1 Stopping Managed Servers

You must stop the WLS_ODS1 and WLS_ODS2 Managed Servers running on IDMHOST1 and IDMHOST2 by using the Oracle WebLogic Server Administration Console. For more information, see the "Starting and Stopping Oracle Fusion Middleware" section in the Oracle Fusion Middleware Administrator's Guide.

8.1.2 Stopping the Administration Server

You must stop the IDMHOST1 Administration Server, for more information see the "Starting and Stopping Administration Servers" in the Oracle Fusion Middleware Administrator's Guide.

8.1.3 Stopping the Node Manager

Stop the Node Manager running on IDMHOST1 and IDMHOST2 by closing the command shell in which it is running or terminate the Node Manager Process. For example, run the following command on a UNIX operating system:

kill -9 pid

Replace pid with the process ID of the Node Manager process.

8.1.4 Stopping the Oracle Management Agent

To stop the Oracle Management Agent running on IDMHOST1 and IDMHOST2, run the following command:

opmnctl stopall

8.1.5 Stopping the System Components

You must stop all system components and processes running on Oracle Internet Directory (running on OIDHOST1 and OIDHOST2), Oracle Virtual Directory (running on OVDHOST1 and OVDHOST2), and Oracle HTTP Server (running on WEBHOST1 and WEBHOST2) by using the opmnctl command-line tool:

opmnctl stopall

8.1.6 Special Consideration for Patching OID Replication Environments

If you have configured OID replication in your environment:

  1. Stop the replication server on all the nodes of Directory Replication Group (DRG).

  2. Patch one node at a time to the latest version using the Patch Set Installer.

  3. Restart the replication server after patching all the nodes of DRG.

8.2 Task 2: Updating Oracle WebLogic Server to Version 10.3.5

Your existing Oracle WebLogic Server must be updated to version 10.3.5 on IDMHOST1, IDMHOST2, OIDHOST1, OIDHOST2, OVDHOST1 and OVDHOST2.

In order to update your WebLogic Server, you must use the upgrade installer, which requires a My Oracle Support account. For more information, see "Downloading an Upgrade Installer From My Oracle Support" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

8.3 Task 3: Updating the Oracle Identity Management Oracle Home using the Oracle Identity Management Patch Set Installer

You must update your existing Oracle Identity Management ORACLE_HOME to the latest version on IDMHOST1, IDMHOST2, OIDHOST1, OIDHOST2, OVDHOST1, and OVDHOST2 by using the Patch Set Installer for Oracle Identity Management.

For instructions, see Chapter 3, "Applying the Latest Oracle Fusion Middleware Patch Set".

After the installation is complete, the oracleRoot.sh confirmation dialog box is displayed. This dialog box advises you to run configuration scrip as root before the installation can proceed. Leaving the confirmation dialog box open, open another shell window, log in as root, and run the oracleRoot.sh script file.

After the script completes, click OK on the Confirmation Dialog box.

8.4 Task 4: Updating the Oracle HTTP Server Oracle Home Using the Oracle Web Tier Patch Set Installer

If Oracle HTTP Server is configured in the ORACLE_INSTANCE, then you must update the Oracle HTTP Server ORACLE_HOME to the latest version on WEBHOST1 and WEBHOST2 by using the Patch Set Installer for Oracle Web Tier.

For instructions, see Chapter 3, "Applying the Latest Oracle Fusion Middleware Patch Set".

8.5 Task 5: Updating the Oracle Identity Management Repository using Patch Set Assistant

You must run Patch Set Assistant to update the database schema for Oracle Internet Directory to the latest version. Patch Set Assistant performs an in-place schema update on your existing schemas.

For instructions, see Chapter 4, "Updating Your Schemas with Patch Set Assistant".

Note:

You must update the schema once for the entire topology.

8.6 Task 6: Performing Manual Post-Patching Procedures

Depending on the components you are upgrading, and the starting versions of those components, you may need to preform additional manual procedures after applying a patch set. Review "Chapter 5, "Post-Patching Procedures" to determine if any additional tasks are required.

8.7 Task 7: Restarting System Components and Servers

You must start the following:

8.7.1 Starting System Components

You must start the following system components:

Note:

If you have not started OPMN, then you must start OPMN by running the following command:

opmnctl start

8.7.1.1 Starting Oracle Internet Directory Processes

To start the Oracle Internet Directory processes, use the following OPMN command:

opmnctl startproc ias-component=oid_component_name

To verify that the Oracle Internet Directory Instances have started, run the following opmnctl status command:

opmnctl status

Example:

Processes in Instance: oid_inst1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
oid1                             | oidldapd           |   31522 | Alive
oid1                             | oidldapd           |   31520 | Alive
oid1                             | oidmon             |   31449 | Alive
EMAGENT                          | EMAGENT            |   31448 | Alive

8.7.1.2 Starting Oracle Virtual Directory Processes

To start the Oracle Virtual Directory processes, use the following OPMN command:

opmnctl startproc ias-component=ovd_component_name

To verify that the Oracle Virtual Directory Instances have started, run the following opmnctl status command:

opmnctl status

Example:

$ ovd_instance_home/bin/opmnctl status
 
Processes in Instance: ovd_inst1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ovd1                             | OVD                |   31658 | Alive
EMAGENT                          | EMAGENT            |   31657 | Alive

8.7.1.3 Starting Oracle HTTP Server

If Oracle HTTP Server is configured in the ORACLE_INSTANCE, then start it using the following command:

opmnctl startproc ias-component=ohs_component_name

To verify that the Oracle HTTP Server instances have started, run the following OPMN command:

opmnctl status

Example:

[abcd@stajz13 Disk1]$ /u01/app/oracle/ps1/admin/ohs_inst1/bin/opmnctl status
 
Processes in Instance: ohs_inst1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ohs1                             | OHS                |    7144 | Alive

8.7.2 Starting Node Manager

You must start Node Manager, running on IDMHOST1 and IDMHOST2, by using the startNodeManager.sh script (UNIX, located at WL_HOME/server/bin directory) or startNodeManager.cmd script (Windows, located at WL_HOME\server\bin directory) as follows:

On UNIX operating systems:

MW_HOME/wl_server_n/server/bin/startNodeManager.sh

On Windows operating systems:

MW_HOME\wl_server_n\server\bin\startNodeManager.cmd

8.7.3 Starting the Oracle WebLogic Administration Server

You must start the IDMHOST1 Administration Server by running the following command:

On UNIX operating systems:

DOMAIN_HOME/bin/startWebLogic.sh

         -Dweblogic.management.username=weblogic

         -Dweblogic.management.password=password

         -Dweblogic.system.StoreBootIdentity=true

On Windows operating systems:

DOMAIN_HOME\bin\startWebLogic.cmd

         -Dweblogic.management.username=weblogic

         -Dweblogic.management.password=password

         -Dweblogic.system.StoreBootIdentity=true

8.7.4 Starting the Managed Server

You must start Node Manager, running on IDMHOST1 and IDMHOST2. For more information see "Starting and Stopping Managed Servers Using Fusion Middleware Control" in Oracle Fusion Middleware Administrator's Guide.

8.7.5 Starting Oracle Management Agent

To start the Oracle Management Agent for the Oracle WebLogic Server running on IDMHOST1 and IDMHOST2, use the following OPMN command:

opmnctl startproc ias-component=EMAGENT

To verify that the Oracle Management Agent Instances have started, run the following opmnctl status command:

opmnctl status

Example:

Processes in Instance: wls_ods1---------------------------------+--------------------+---------+---------ias-component                    | process-type       |     pid | status---------------------------------+--------------------+---------+---------EMAGENT                          | EMAGENT            |   10971 | Alive

8.8 Task 8: Updating the Version Number String Shown in Fusion Middleware Control

If you are using existing Oracle Internet Directory or Oracle Virtual Directory components and you have patched those components to the latest version, you must use the opmnctl updatecomponentregistration command to manually update the version number string that is shown in Fusion Middleware Control.

For instructions, see "Updating the Component Registration of an Oracle Instance by Using opmnctl" in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.