4 Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

You can upgrade Oracle Directory Integration Platform from Oracle Fusion Middleware Release 12c (12.2.1.4.0) to 14c (14.1.2.1.0) .

Complete the steps in the following topics to perform the upgrade:

Parent topic: In-Place Upgrade of Oracle Internet Directory

About the Oracle Directory Integration Platform Upgrade Process

Review the flowchart and roadmap for an overview of the upgrade process for Oracle Directory Integration Platform.

Caution:

Before upgrading to 14c (14.1.2.1.0) release, ensure that the 12c (12.2.1.4.0) EXISTING_DOMAIN_HOME is outside the ORACLE_HOME.

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 4-1 Tasks for Upgrading Oracle Directory Integration Platform

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:

Required

Shut down the 12c (12.2.1.4.0) environment (stop all Administration and Managed Servers).

WARNING: Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes.

Required

Install Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 14c (14.1.2.1.0) in the new Oracle home.

See Installing Oracle Internet Directory.

Optional

Run the Upgrade Assistant in -readiness mode to perform a pre-upgrade readiness check

See Running a Pre-Upgrade Readiness Check

Required

Run the Upgrade Assistant to upgrade schemas

See Upgrading Product Schemas

Required

Run the Reconfiguration Wizard to reconfigure the domain

See Reconfiguring the Domain

Required for Collocated only

Run the Upgrade Assistant to upgrade the domain configurations

Skip this step for standalone domain configurations.

See Upgrading Domain Component Configurations

Note:

For the list of new features for a release, see What's New in Oracle Directory Integration Platform? in Administering Oracle Directory Integration Platform.

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Stopping Servers and Processes

Before you proceed, you must shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components such as Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

The procedures in this section describe how to stop the existing, pre-upgrade servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control or the WebLogic Server Administration Console.

To stop your pre-upgrade Fusion Middleware environment, navigate to the pre-upgrade domain and follow the steps below:

Step 1: Stop System Components

To stop system components, use the stopComponent script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop the Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Step 3: Stop Oracle Identity Management Components

Stop any Oracle Identity Management components, such as Oracle Internet Directory:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

Step 4: Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop the Administration Server, use the stopWebLogic script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 5: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after setting the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. See stopNodeManager in WLST Command Reference for Oracle WebLogic Server.

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Installing Oracle Internet Directory

Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Internet Directory (OID) 14c (14.1.2.1.0) distributions on the target system and install them using Oracle Universal Installer.

Note:

Apply the one-off ADF patch (search for Bug ID 37376076 at https://support.oracle.com) manually using OPatch to the Oracle Internet Directory 14c (14.1.2.1.0) ORACLE_HOME after installation and before domain creation. This applies only to collocated OID installations and does not apply to standalone Oracle Internet Directory 14c (14.1.2.1.0) installations.

To install the 14c (14.1.2.1.0) distributions:

  1. Sign in to the target system.
  2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
    • (Required for collocated domains) Oracle Fusion Middleware Infrastructure (fmw_14.1.2.0.0_infrastructure.jar)
    • Oracle Internet Directory (UNIX: fmw_14.1.2.1.0_oid_<platform>.bin), (Windows: setup_fmw_14.1.2.1.0_oid_win64.exe)
  3. Change to the directory where you downloaded the product distribution
  4. Start the installation program for Oracle Fusion Middleware Infrastructure:
    • (UNIX) JDK_HOME/bin/java -jar fmw_14.1.2.0.0_infrastructure.jar
    • (Windows) JDK_HOME\bin\java -jar fmw_14.1.2.0.0_infrastructure.jar
  5. On UNIX operating systems, the Installation Inventory Setup screen is displayed.
    If prompted, specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  7. On the Auto Updates screen, select an option:

    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
  9. On the Installation Type screen, select the following:
    • For Infrastructure, select Fusion Middleware Infrastructure.

    Click Next.

    Note:

    The topology in this document does not include server examples. Oracle strongly recommends that you do not install examples into a production environment.
  10. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  11. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  12. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  13. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
  14. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for Oracle Internet Directory and repeat the steps above to navigate through the installer screens:
    (UNIX) ./fmw_14.1.2.1.0_oid_<platform>.bin
    (Windows) setup_fmw_14.1.2.1.0_oid_win64.exe
  15. After a successful installation of 14c (14.1.2.1.0), install patches as documented in the 14c (14.1.2.1.0) Fusion Middleware Release Notes.

Note:

  • Apply the one-off ADF patch (search for Bug ID 37376076 at https://support.oracle.com) manually using OPatch to the Oracle Internet Directory 14c (14.1.2.1.0) ORACLE_HOME after installation. This applies only to collocated OID installations and does not apply to standalone Oracle Internet Directory 14c (14.1.2.1.0) installations
  • For more information about installing Oracle Internet Directory, see Installing the Oracle Internet Directory Software in the Installing Oracle Internet Directory.
  • For more information about installing Oracle Fusion Middleware Infrastructure, see Installing the Infrastructure Software in the in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Upgrading Product Schemas

After stopping servers and processes, use the Upgrade Assistant to upgrade your 12.2.1.4.0 schemas to the 14c (14.1.2.1.0) release of Oracle Fusion Middleware.

Note:

If your domain has the WLSSchemaDataSource data source, then you will need to verify which database user is assigned to it. If <PREFIX>_WLS_RUNTIME is assigned to it, then you need to change that to <PREFIX>_WLS . For more information, see Verify the Database User for the WLSSchemaDataSource Data Source.

Note:

As of 14c (14.1.2.1.0) the following schema changes have been made to help you prepare for an optional zero downtime upgrade to a future release:

  • Schemas created prior to 14c (14.1.2.1.0) with editions disabled and then upgraded to 14c (14.1.2.1.0) will become editions enabled.

  • Oracle Internet Directory does not support editions. Oracle Internet Directory schemas need to be created with edition disabled.

  • Schemas created in 14c (14.1.2.1.0) will be created with editions enabled.

The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain. The option you select determines which Upgrade Assistant screens you will use.

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 14c (14.1.2.1.0).

Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time. For information about creating a user for running Upgrade Assistant, see Creating a Non-SYSDBA User to Run the Upgrade Assistant.

To start the Upgrade Assistant:

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

Parent topic: Upgrading Product Schemas

Upgrading Oracle Directory Integration Platform Schemas

Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.

To upgrade product schemas with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the Selected Schemas screen, select the schema upgrade operation that you want to perform:
    • Individually Selected Schemas if you have a standalone installation or if you want to select individual schemas for upgrade and you do not want to upgrade all of the schemas used by the domain.

      Caution:

      Upgrade only those schemas that are used to support your 14c (14.1.2.1.0) components. Do not upgrade schemas that are currently being used to support components that are not included in Oracle Fusion Middleware 14c (14.1.2.1.0).
    • All Schemas Used by a Domain to allow the Upgrade Assistant to discover and select all components that have a schema available to upgrade in the domain specified in the Domain Directory field. This is also known as a domain assisted schema upgrade. Additionally, the Upgrade Assistant pre-populates connection information on the schema input screens.

      Note:

      Oracle recommends that you select All Schemas Used by a Domain for most upgrades to ensure all of the required schemas are included in the upgrade. However, use the Individually Selected Schemas option for standalone installations.

    Click Next.

  3. If you selected Individually Selected Schemas: On the Available Components screen, select the components for which you want to upgrade schemas. When you select a component, the schemas and any dependencies are automatically selected.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5. On the Schema Credentials screen(s), specify the database connection details for each schema you are upgrading (the screen name changes based on the schema selected):

    • Select the database type from the Database Type drop-down menu.

    • Enter the database connection details, and click Connect.

    • Select the schema you want to upgrade from the Schema User Name drop-down menu, and then enter the password for the schema. Be sure to use the correct schema prefix for the schemas you are upgrading.

  6. On the Examine screen, review the status of the Upgrade Assistant as it examines each schema, verifying that the schema is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  7. On the Upgrade Summary screen, review the summary of the schemas that will be upgraded and/or created.
    Verify that the correct Source and Target Versions are listed for each schema you intend to upgrade.
    If you want to save these options to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
    Click Next .
  8. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any schemas are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  9. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard.

    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails, you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Parent topic: Upgrading Product Schemas

Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 14c (14.1.2.1.0).

When you reconfigure a WebLogic Server domain, the following items are automatically updated, depending on the applications in the domain:

  • WebLogic Server core infrastructure

  • Domain version

Note:

Before you begin the domain reconfiguration, note the following limitations:

  • Make sure that the original Middleware home does not include any deployments that can cause an error.

  • The Reconfiguration Wizard does not update any of your own applications that are included in the domain.

  • Transforming a non-dynamic cluster domain to a dynamic cluster domain during the upgrade process is not supported.

    The dynamic cluster feature is available when running the Reconfiguration Wizard, but Oracle only supports upgrading a non-dynamic cluster upgrade and then adding dynamic clusters. You cannot add dynamic cluster during the upgrade process.

Specifically, when you reconfigure a domain, the following occurs:

  • The domain version number in the config.xml file for the domain is updated to the Administration Server's installed WebLogic Server version.

  • Reconfiguration templates for all installed Oracle products are automatically selected and applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version.

  • Start scripts are updated.

    If you want to preserve your modified start scripts, be sure to back them up before starting the Reconfiguration Wizard.

Note:

When the domain reconfiguration process starts, you can’t undo the changes that it makes. Before running the Reconfiguration Wizard, ensure that you have backed up the domain as covered in the pre-upgrade checklist. If an error or other interruption occurs while running the Reconfiguration Wizard, you must restore the domain by copying the files and directories from the backup location to the original domain directory. This is the only way to ensure that the domain has been returned to its original state before reconfiguration.

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Backing Up the Domain

Before running the Reconfiguration Wizard, create a backup copy of the domain directory.

  1. Create a backup of the domain directory.
  2. Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
  3. Verify that the backed up versions of the domain are complete.
If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.

Parent topic: Reconfiguring the Domain

Starting the Reconfiguration Wizard

Note:

Shut down the administration server and all collocated managed servers before starting the reconfiguration process.

To start the Reconfiguration Wizard in graphical mode:

  1. Sign in to the system on which the domain resides.
  2. Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
  3. Go to the oracle_common/common/bin directory:
    • (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
    • (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
  4. Start the Reconfiguration Wizard with the following logging options:
    • (UNIX) ./reconfig.sh -log=log_file -log_priority=ALL
    • (Windows) reconfig.cmd -log=log_file -log_priority=ALL

    where log_file is the absolute path of the log file you'd like to create for the domain reconfiguration session. This can be helpful if you need to troubleshoot the reconfiguration process.

    The parameter -log_priority=ALL ensures that logs are logged in fine mode.

    Note:

    When you run this command, the following error message might appear to indicate that the default cache directory is not valid:

    *sys-package-mgr*: can't create package cache dir

    You can change the cache directory by setting the environment variable CONFIG_JVM_ARGS. For example:

    CONFIG_JVM_ARGS=-Dpython.cachedir=valid_directory

Parent topic: Reconfiguring the Domain

Reconfiguring the Oracle Directory Integration Platform Domain

Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only. Use the pack/unpack utility to apply the changes to other cluster members in the domain.
To reconfigure the domain with the Reconfiguration Wizard:
  1. On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
  2. On the Reconfiguration Setup Progress screen, view the progress of the setup process. When complete, click Next.
    During this process:

    • The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    • The domain upgrade is validated.

  3. On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. The supported JDK version for 14c (14.1.2.1.0) is 17.0.12 and later. Click Next.

    Note:

    You cannot change the Domain Mode at this stage.
    For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
  4. On the Database Configuration Type screen, select RCU Data to connect to the Server Table (_STB) schema. Enter the database connection details using the RCU service table (_STB) schema credentials and click Get RCU Configuration. The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

    Note:

    For any existing 11g datasource, the reconfiguration will preserve the existing values. For new datasources where the schema was created for 12c by the RCU, the default connection data will be retrieved from the _STB schema. If no connection data for a given schema is found in the _STB schema, then the default connection data is used.

    If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.

  5. On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
  6. On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.
    When the check is complete, click Next.
  7. On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

    Note:

    The categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain.
    For this upgrade, select none of the options and click Next.
  8. On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
    You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.
    To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

    Note:

    The location of the domain does not change when you reconfigure it.
  9. The Reconfiguration Progress screen displays the progress of the reconfiguration process.
    During this process:

    • Domain information is extracted, saved, and updated.

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    When the progress bar shows 100%, click Next.
  10. The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.
    If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.
    Note the Domain Location and the Admin Server URL for further operations.

Parent topic: Reconfiguring the Domain

Upgrading Domain Component Configurations

After reconfiguring the domain, use the Upgrade Assistant again to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 14c (14.1.2.1.0).

Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time. For information about creating a user for running Upgrade Assistant, see Creating a Non-SYSDBA User to Run the Upgrade Assistant.

To start the Upgrade Assistant:

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

Parent topic: Upgrading Domain Component Configurations

Upgrading Domain Component Configurations

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

After running the Reconfiguration Wizard to reconfigure the WebLogic domain to 14c (14.1.2.1.0), you must run the Upgrade Assistant to upgrade the domain component configurations to match the updated domain configuration.

To upgrade domain component configurations with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the next screen:

    • Select All Configurations Used By a Domain. The screen name changes to WebLogic Components.

    • In the Domain Directory field, enter the WebLogic domain directory path.

    Click Next.

  3. On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
    If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5. On the Examine screen, review the status of the Upgrade Assistant as it examines each component, verifying that the component configuration is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  6. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.

    Click Upgrade to start the upgrade process.

    In case of cluster upgrade, a pop-up message — Upgrade not necessary for Directory Integration Platform is displayed. Ignore this and proceed.

  7. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.
    Click Upgrade to start the upgrade process.
  8. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  9. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard. The Post-Upgrade Actions window describes the manual tasks you must perform to make components functional in the new installation. This window appears only if a component has post-upgrade steps.
    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at NEW_ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Parent topic: Upgrading Domain Component Configurations

Starting Servers and Processes

After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.

The components may be dependent on each other so they must be started in the correct order.

Note:

The procedures in this section describe how to start servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

As of release 14c (14.1.2.0.0), the WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

To start your Fusion Middleware environment, follow the steps below:

Note:

Depending on your existing security settings, you may need to perform additional configuration before you can manage a domain with secured production mode enabled. For more information, see Connecting to the Administration Server using WebLogic Remote Console

.

Step 1: Start the Administration Server

To start the Administration Server, use the startWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startWebLogic.sh

  • (Windows) NEW_DOMAIN_HOME\bin\startWebLogic.cmd

    Note:

    When using secured production mode, you must provide additional parameters to start the Administration Server. See Connecting to the Administration Server using WLST in Administering Security for Oracle WebLogic Server.

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startNodeManager.sh

  • (Windows) NEW_DOMAIN_HOME\bin\startNodeManager.cmd

Step 3: Start Any Managed Servers

To start a WebLogic Server Managed Server, use the startManagedWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

  • (Windows) NEW_DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

    Note:

    When using secured production mode, you must provide additional parameters to start the Managed Servers. See Starting Managed Servers using a Start Script in Administering Security for Oracle WebLogic Server.

Note:

The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Step 4: Start System Components

To start system components, such as Oracle HTTP Server, use the startComponent script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

  • (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.

Parent topic: Upgrading Domain Component Configurations

Verifying the Domain-Specific-Component Configurations Upgrade

To verify that the domain-specific-component configurations upgrade was successful, sign in to the Administration console and the Oracle Enterprise Manager Fusion Middleware Control and verify that the version numbers for each component is 14.1.2.1.0.

To verify that the domain component configurations upgrade was successful, log in to the Remote console and the Fusion Middleware Control using the following URLs, and verify the upgraded version numbers for each component:

Remote Console URL: http://administration_server_host:administration_server_port/console

Fusion Middleware Control URL: http://administration_server_host:administration_server_port/em

Note:

After the upgrade, you must run all of your administration tools from the new 14c (14.1.2.1.0) Oracle home and not from the existing 12c (12.2.1.4) Oracle home.

Parent topic: Upgrading Domain Component Configurations

Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

After you upgrade Oracle Directory Integration Platform to 14c (14.1.2.1.0), perform the necessary post-upgrade tasks.

Note:

After upgrade, Resource Usage Charts will not be displayed in Enterprise Manager Oracle Directory Integration Platform 14c (14.1.2.1.0).

Topics:

Parent topic: Upgrading Oracle Directory Integration Platform to 14c (14.1.2.1.0)

Starting Servers and Processes

After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.

The components may be dependent on each other so they must be started in the correct order.

Note:

The procedures in this section describe how to start servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

As of release 14c (14.1.2.0.0), the WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

To start your Fusion Middleware environment, follow the steps below:

Note:

Depending on your existing security settings, you may need to perform additional configuration before you can manage a domain with secured production mode enabled. For more information, see Connecting to the Administration Server using WebLogic Remote Console

.

Step 1: Start the Administration Server

To start the Administration Server, use the startWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startWebLogic.sh

  • (Windows) NEW_DOMAIN_HOME\bin\startWebLogic.cmd

    Note:

    When using secured production mode, you must provide additional parameters to start the Administration Server. See Connecting to the Administration Server using WLST in Administering Security for Oracle WebLogic Server.

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startNodeManager.sh

  • (Windows) NEW_DOMAIN_HOME\bin\startNodeManager.cmd

Step 3: Start Any Managed Servers

To start a WebLogic Server Managed Server, use the startManagedWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

  • (Windows) NEW_DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

    Note:

    When using secured production mode, you must provide additional parameters to start the Managed Servers. See Starting Managed Servers using a Start Script in Administering Security for Oracle WebLogic Server.

Note:

The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Step 4: Start System Components

To start system components, such as Oracle HTTP Server, use the startComponent script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startComponent.sh component_name

  • (Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.

Parent topic: Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

Updating ODIP Domain Configuration Details

After you upgrade Oracle Directory Integration Platform (ODIP) to 14c (14.1.2.1.0), you must update the ODIP domain configurations.

Prior to upgrade, if none of the Managed Servers had the name wls_ods1, then you must delete the new managed server wls_ods1 that is created after upgrade. To do this, complete the following steps:

  1. Start the WebLogic Administration Server. See Starting Servers and Processes.
  2. Log in to the WebLogic Administration console using the following URL:
    http://admin_host:admin_port/console
  3. Click Lock & Edit.
  4. Click Environments and then click Coherence Clusters.
  5. Select defaultCoherenceCluster and then click Members.
  6. Deselect wls_ods1.
  7. Click Save.
  8. Go back to Environments, and click Servers.
  9. Select wls_ods1.
  10. Click Delete.
  11. Save and Release the configuration once the changes are made.

Prior to upgrade, if any of the Managed Servers had the name wls_ods1, then you must update the Managed Server configuration settings to their original values which were present prior to upgrade. To do this, complete the following steps:

  1. Start the WebLogic Administration Server. See Starting Servers and Processes.

  2. Log in to the WebLogic Administration console using the following URL:

    http://admin_host:admin_port/console

  3. Click Lock & Edit.

  4. Click Environments, and then click Servers.

  5. Locate the server name wls_ods1 under <server> tag in the $DOMAIN_HOME_BACKUP/config/config.xml file. This file contains the server configuration details that were present prior to upgrade.

  6. Update the following sections on the Administration console with the values present in the backup config.xml file:

    • Go to the Keystores under SSL and Configuration , and update the SSL configuration information.

      Note:

      The step is mandatory if you configured SSL for wls_ods1 server prior to upgrade.

    • Go to the HTTP tab under Protocols, and update the value for Post Timeout.

    • Go to the Tuning tab under Configuration and click the Advanced link then update the values for Idle Periods Until Timeout, DGC Idle Periods Until Timeout.

    • Go to the General tab under Protocols and update the Complete Message Timeout, Idle Connection Timeout and so on, if they are present in the backup config.xml file.

    • Update any other details related to wls_ods1, that are present in the backup config.xml file.

  7. In case of a cluster (high availability) setup, target the Infrastructure Data Sources to ODIP Managed Server cluster. To do this, complete the following steps:

    1. Go to Services, and click Data Sources.

    2. Select a data source that is targeted to wls_ods1.

    3. Go to the Targets tab, and deselect wls_ods1.

    4. Select All Servers in the Cluster.

    5. Click Save.

    6. Repeat the steps for all of the data sources that are targeted to wls_ods1, such as opss-audit-DBDS, opss-audit-viewDS, opss-data-source and so on.

  8. In case of cluster (high availability) setup, do the following:

    1. Click Environments and then click Coherence Clusters.

    2. Select defaultCoherenceCluster and then click Members.

    3. Select Cluster.

    4. Select All Servers in the cluster.

    5. Release the configuration once the changes are made.

In a cluster (high availability) setup, copy the ODIP backened directory connection configuration file dip-config.xml to all of the Managed Server nodes, by doing the following:

  1. Go to the directory DOMAIN_HOME/config/fmwconfig/servers/managed_server_name/applications. For example, on Unix, use the command: 

    cd DOMAIN_HOME/config/fmwconfig/servers/wls_ods1/applications

  2. Create a named DIP_14.1.2.1.0/configuration using the following command: 

    mkdir -p DIP_14.1.2.1.0/configuration

  3. Copy the dip-config.xml to the new directory using the following command: 

    cp -f DIP_12.2.1.4.0/configuration/dip-config.xml DIP_14.1.2.1.0/configuration/dip-config.xml

  4. Restart the servers.

Parent topic: Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

Adding the Cipher Suites (Optional)

Review the Secure Sockets Layer (SSL) modes available for Oracle Directory Integration Platform (ODIP).

See Secure Sockets Layer and Oracle Directory Integration Platform in the Administrator's Guide for Oracle Directory Integration Platform.

If Oracle Directory Integration Platform was configured in SSL mode for backend directories or was communicating with connected directories in SSL mode pre-upgrade, and if any of the connected and backend directories do not have ciphers or security protocol available in 14c (14.1.2.1.0), then add to the new cipher suites to the list.

For example, if OID was the backend directory and configured in SSL no-auth mode prior to upgrade, then OID recognizes only anonymous ciphers during SSL negotiation. The anonymous ciphers in ODIP 14c (14.1.2.1.0) are not supported by default. Therefore, you have two options:

Note:

In case of a cluster setup, perform these steps for each of the Managed Servers where ODIP is deployed.

Parent topic: Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

Copying the Custom Mapping Plug-ins to the Upgraded Environment

After you upgrade Oracle Directory Integration Platform to 14c (14.1.2.1.0), you must copy the custom mapping plug-ins to the upgraded environment.

To do this, complete the following steps:
  1. Ensure that you have started the Oracle Directory Integration Platform Managed Servers.
  2. Copy the folder DOMAIN_NAME/servers/MANAGED_SERVER_NAME/tmp/_WL_user/DIP_VERSION_NUMBER/RANDOM_CHARACTERS/APP-INF/lib/ from the 12c (12.2.1.4.0) environment to the 14c (14.1.2.1.0) environment.
  3. Restart the Oracle Directory Integration Platform Managed Servers.

    Note:

    In case of a cluster setup, perform these steps for each of the Managed Servers where ODIP is deployed.

Parent topic: Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

Updating the Database Profiles With Service Names

If you had created any database profiles in 12c (12.2.1.4.0), ensure that manually update existing value of SID with the service names, after upgrade.

See Editing Synchronization Profiles in the Administering Oracle Directory Integration Platform.

Note:

It would continue to work even if you do not replace SID with service name, with connection exception in the log. However, it is recommended that you update the database profile with service name.

Parent topic: Performing Post-Upgrade Tasks for Oracle Directory Integration Platform

Importing Administration Server Certificate of Oracle Unified Directory to ODIP Trust Store

If you are using Oracle Unified Directory as the backend directory, ensure that you import the Administration Server certificate of Oracle Unified Directory to Oracle Directory Integration Platform (ODIP) trust store.

See Configuring Oracle Directory Integration Platform for Oracle Unified Directory in the Administering Oracle Directory Integration Platform.

Note:

If truststore was configured prior to upgrade, perform step 1 (exporting the certificate for the Oracle Unified Directory Administration Server instance) and step 2 (importing the trusted certificate) described in Configuring Oracle Directory Integration Platform for Oracle Unified Directory in the Administering Oracle Directory Integration Platform.

Parent topic: Performing Post-Upgrade Tasks for Oracle Directory Integration Platform