5 Upgrading Oracle Internet Directory Highly Available Environments

Describes the process of upgrading an Oracle Internet Directory highly available environment from 11g Release 1 (11.1.1.9.0) to Oracle Identity Governance 12c (12.2.1.3.0).

Topics

• About the Oracle Internet Directory Multinode Upgrade Process
  Follow the steps in the task roadmap for upgrading Oracle Internet Directory highly available environments to 12c (12.2.1.3.0).
• Completing the Pre-Upgrade Tasks for OID Multi-Node Upgrade
  
• Replicating the Domain Configurations on OIDHOST2
  Replicate the domain configurations on OIDHOST2. This involves packing the upgraded domain on OIDHOST1 and unpacking it on OIDHOST2.

About the Oracle Internet Directory Multinode Upgrade Process

Follow the steps in the task roadmap for upgrading Oracle Internet Directory highly available environments to 12c (12.2.1.3.0).

The steps you take to upgrade your existing domain will vary depending on how your domain is configured and which components are being upgraded. Follow only those steps that are applicable to your deployment.

Table 5-1 Tasks for Upgrading Oracle Internet Directory Highly Available Environments

Task	Description
Required If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.	See: Introduction to Upgrading Oracle Internet Directory to 12c (12.2.1.3.0) Pre-Upgrade Requirements
Required Complete the following pre-upgrade tasks: Ensure that Oracle Internet Directory is integrated with Oracle WebLogic Server 10.3.6 in the existing 11.1.1.9.0 deployment. Copy the AS Instance folder that is created on OIDHOST2, to OIDHOST1.	See Completing the Pre-Upgrade Tasks for OID Multi-Node Upgrade.
Required Install the product distributions on both OIDHOST1 and OIDHOST2. You must install Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 12c (12.2.1.3.0) in a new Oracle home, for both 11.1.1.9.0 standalone and collocated deployments.	See Installing Oracle Internet Directory.
Optional Run a pre-upgrade readiness check. Pre-upgrade readiness check is not supported for standalone upgrade.	See Running a Pre-Upgrade Readiness Check.
Required Start the Repository Creation Utility (RCU) on OIDHOST1 to create the 12c schemas (that are missing in the 11g environment). You can also create this schema when you run the Upgrade Assistant (UA) to upgrade existing schemas.	The schemas you create will vary depending on your existing schema configuration. See Creating the Required 12c Schemas with the RCU.
Required Stop all servers and processes on both OIDHOST1 and OIDHOST2.	See Stopping Servers and Processes.
Required Run the Upgrade Assistant (UA) on OIDHOST1 to upgrade the necessary schemas to 12c.	See Upgrading Product Schemas.
Required Reconfigure the Oracle Internet Directory domain on OIDHOST1.	See About Reconfiguring the Domain.
Required Run the Upgrade Assistant (UA) to upgrade the Oracle Internet Directory domain configurations on OIDHOST1.	The Upgrade Assistant is used to update the reconfigured domain’s component configurations. See Upgrading Domain Component Configurations.
Required Replicate the domain configurations on OIDHOST2 using pack and unpack commands.	This includes packing the domain on OIDHOST1 and unpacking it on OIDHOST2. See Replicating the Domain Configurations on OIDHOST2.
Required Start the servers in the following order: Start the Administration Server and the Managed Servers on OIDHOST1. Start the Node Managers on OIDHOST1 and OIDHOST2. Start the Oracle Internet Directory system component on OIDHOST1. Start the Oracle Internet Directory system component on OIDHOST2 from OIDHOST1.	See Starting the Servers. Note: The OID servers should be started serially (and not simultaneously). Ensure that you start the OID server on OIDHOST2 from OIDHOST1. From DOMAIN_HOME/bin directory on OIDHOST1, start oid2 instance by executing startComponent.sh script: ./startComponent.sh oid2 Execute the script from OIDHOST1 machine, where AdminServer is setup and not from OIDHOST2.
Optional Oracle Internet Directory (OID) server in 12c does not support certificates signed with MD5 signatures. After upgrade, any MD5 signature based certificates created and used in 11g against OID server need to be changed to at least SHA1 based certificates to ensure proper SSL communication with OID server.	See Creating SSL Wallet in 12c.
Optional Verify the upgrade by accessing the new Oracle Directory Services Manager console.	See Accessing the New Oracle Directory Services Manager Console.

Note:

The Oracle Directory Integration Platform version label remains the same (that is 11g Release 1 (11.1.1.9.0) or 12c (12.2.1.2.0, depending on the starting point of the upgrade) after the upgrade to 12c (12.2.1.3.0).

Completing the Pre-Upgrade Tasks for OID Multi-Node Upgrade

1. Ensure that Oracle Internet Directory (OID) is integrated with Oracle WebLogic Server 10.3.6 in the existing 11.1.1.9.0 deployment.

   All of the nodes in a OID high availability setup must be registered with WebLogic server using opmnctl registerinstance command.

   If WebLogic Server was not installed in 11.1.1.9.0, then install Oracle WebLogic Server 10.3.6, create a domain by selecting the Enterprise Manager template, and then register all of the OID nodes using the opmnctl registerinstance command. The upgrade process should be carried out on the AdminServer machine.

   Note:

   For information about registering Oracle Internet Directory instance with WebLogic Server, see Registering an Oracle Instance or Component with the WebLogic Server in Administrator's Guide for Oracle Internet Directory for 11g Release 1 (11.1.1.9.0).

2. Copy the AS Instance folder from OIDHOST2 to OIDHOST1.

   The AS Instance folder and all of its contents on all of the OID nodes should be made available on the Weblogic AdminServer machine. These folders can either be copied over or made available via network file system sharing. These AS Instance folders, on the AdminServer machine, must have the same path as compared to their corresponding source OID node. This is required for transferring OID instance artifacts to WebLogic domain framework from OPMN framework during the upgrade process.

Replicating the Domain Configurations on OIDHOST2

Replicate the domain configurations on OIDHOST2. This involves packing the upgraded domain on OIDHOST1 and unpacking it on OIDHOST2.

To do this, complete the following steps:

1. On OIDHOST1, run the following command from the location $MW_HOME/oracle_common/common/bin to pack the upgraded domain:
   • On UNIX:

     sh pack.sh -domain=<Location_of_OID_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -template_name="OID Domain" -managed=true

   • On Windows:

     pack.cmd -domain=<Location_of_OID_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -template_name="OIDM Domain" -managed=true

2. Copy the domain configuration jar file created by the pack command on OIDHOST1 to any accessible location on OIDHOST2.
3. On OIDHOST2, run the following command from the location $MW_HOME/oracle_common/common/bin to unpack the domain:

   Note:

   The domain should be unpacked in a new location. The existing 11.1.1.9.0 domain in OIDHOSt2, if any, should be ignored, and the new unpacked domain should be used.
   • On UNIX:

     sh unpack.sh -domain=<Location_of_OID_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -overwrite_domain=true

   • On Windows:

     unpack.cmd -domain=<Location_of_OID_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -overwrite_domain=true