Thank you for your feedback!Categories
This chapter describes how to patch your existing Oracle Identity Management 11.1.1.2.0 high availability environment to 11.1.1.3.0. 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.Task 2: Updating Oracle WebLogic Server 10.3.2 to Oracle WebLogic Server 10.3.3
Task 4: Updating the Oracle HTTP Server Oracle Home Using the Oracle Web Tier Patch Set Installer
Task 5: Updating the Oracle Identity Management Repository using Patch Set Assistant
Task7: Updating the Version Number String Shown in Oracle Enterprise Manager
Task 8: Updating the Oracle Virtual Directory Version String in the Oracle Directory Service Manager
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 the "Advanced Administration: Backup and Recovery" part in the Oracle Fusion Middleware Administrator's Guide.Before migrating Oracle Identity Management, you must stop the following servers and components:
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.
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.
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 in UNIX, run the command kill -9 pid, where pid is the process id of the Node Manager process.
To stop the Oracle Management Agent running on IDMHOST1 and IDMHOST2, run the following command:
opmnctl stopall
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
If OID replication was configured in 11.1.1.2.0 then stop the replication server on all the nodes of Directory Replication Group (DRG), patch one node at a time to 11.1.1.3.0 using the Patch Set Installer and restart the replication server after patching all the nodes of DRG.
If Oracle WebLogic Server is installed in Oracle Identity Management 11.1.1.2.0, then you must migrate the Oracle WebLogic Server from 10.3.2 to 10.3.3 on IDMHOST1, IDMHOST2, OIDHOST1, OIDHOST2, OVDHOST1 and OVDHOST2.
In order to update your WebLogic Server, you must have a My Oracle Support account. There are two ways for you to update your WebLogic Server:
Use the Smart Update tool. For more information, see "Downloading and Installing Maintenance Packs" in Oracle Smart Update Installing Patches and Maintenance Packs.
Use the upgrade installers. For more information, see "Downloading an Upgrade Installer From My Oracle Support" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
You must migrate the Oracle Identity Management ORACLE_HOME from 11.1.1.2.0 to 11.1.1.3.0 on IDMHOST1, IDMHOST2, OIDHOST1, OIDHOST2, OVDHOST1, and OVDHOST2 by using the Patch Set Installer for Oracle Identity Management.
For instructions, see Chapter 4, "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.
Note:
If upgrade of your existing 10g Release 2 (10.1.2) or 10g (10.1.4) Oracle Identity Management to Oracle Identity Management 11g was performed to create an 11.1.1.2.0 Oracle home, then you must also run the
Sign In
oidRoot.sh script.After the script completes, click OK on the Confirmation Dialog box.
If Oracle HTTP Server is configured in the ORACLE_INSTANCE, then you must migrate the Oracle HTTP Server ORACLE_HOME from 11.1.1.2.0 to 11.1.1.3.0 on WEBHOST1 and WEBHOST2 by using the Patch Set Installer for Oracle Web Tier.
For instructions, see Chapter 4, "Applying the Latest Oracle Fusion Middleware Patch Set".
You must run Patch Set Assistant to update the database schema for Oracle Internet Directory 11.1.1.2.0 to 11.1.1.3.0. Patch Set Assistant performs an in-place schema update on an existing 11.1.1.2.0 schema.
For instructions, see Chapter 5, "Updating Your Schemas with Patch Set Assistant".
Note:
You must update the schema once for the entire topology.You must start the following:
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
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 | Aliveoid1 | oidldapd | 31520 | Aliveoid1 | oidmon | 31449 | AliveEMAGENT | EMAGENT | 31448 | Alive
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:
[abcd@strasha11 bin]$ /u01/app/oracle/ps1/admin/ovd_inst1/bin/opmnctl status Processes in Instance: ovd_inst1 ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- ovd1 | OVD | 31658 | Alive EMAGENT | EMAGENT | 31657 | Alive
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
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
You must start the IDMHOST1 Administration Server by running the following command:
On UNIX operating systems:
MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true
On Windows operating systems:
MW_HOME\user_projects\domains\domain_name\bin\startWebLogic.cmd -Dweblogic.management.username=weblogic -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true
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.
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
If you are using Oracle Internet Directory or Oracle Virtual Directory components from 11.1.1.2.0 and you have patched those components to11.1.1.3.0, you must use the opmnctl updatecomponentregistration command to manually update the version number string that is shown in Oracle Enterprise Manager.
For instructions, see Section 4.6.1.2, "Upgrading the Version Number String Shown in Oracle Enterprise Manager".
To update the Oracle Virtual Directory version string in the Oracle Directory Service Manager, follow the instructions in Section 4.7.2, "Updating the Oracle Virtual Directory Version Number in Oracle Directory Service Manager".