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:
- 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. - 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. - Uninstalling the Software
Follow the instructions in this section to start the Uninstall Wizard and remove the software. - 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. - 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. - Reconfiguring the Domain
Run the Reconfiguration Wizard to reconfigure your domain component configurations to 14c (14.1.2.1.0). - 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. - 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.
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. |
Required Uninstall Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 12c (12.2.1.4.0) in the existing Oracle home. |
|
Required Install Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 14c (14.1.2.1.0) in the new Oracle home. |
|
Required Start the servers. |
When the upgrade process is complete, restart the 14c (14.1.2.1.0) instance. |
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.
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.
Uninstalling the Software
Follow the instructions in this section to start the Uninstall Wizard and remove the software.
If you want to uninstall the product in a silent (command-line) mode, see Running the Oracle Universal Installer for Silent Uninstallation in Installing Software with the Oracle Universal Installer.
Selecting the Product to Uninstall
Because multiple products exist in the Oracle home, ensure that you are uninstalling the correct product.
After you run the Uninstall Wizard, the Distribution to Uninstall screen opens. From the dropdown menu, select the Oracle Internet Directory 12.2.1.3.0 product and click Uninstall. The uninstallation program shows the screens listed in Navigating the Uninstall Wizard Screens.
Run the Uninstall Wizard again to uninstall the Oracle Fusion Middleware Infrastructure. For instructions see, Uninstalling Oracle Fusion Middleware Infrastructure in Installing and Configuring the Oracle Fusion Middleware Infrastructure.
Parent topic: Uninstalling the Software
Navigating the Uninstall Wizard Screens
The Uninstall Wizard shows a series of screens to confirm the removal of the software.
If you need help on screen listed in Table 4-2, click Help on the screen.
Table 4-2 Uninstall Wizard Screens and Descriptions
Screen | Description |
---|---|
Welcome |
Introduces you to the product Uninstall Wizard. |
Uninstall Summary |
Shows the Oracle home directory and its contents that are uninstalled. Verify that this is the correct directory. If you want to save these options to a response file, click Save Response File and enter the response file location and name. You can use the response file later to uninstall the product in silent (command-line) mode. See Running the Oracle Universal Installer for Silent Uninstall in Installing Software with the Oracle Universal Installer. Click Deinstall, to begin removing the software. |
Uninstall Progress |
Shows the uninstallation progress. |
Uninstall Complete |
Appears when the uninstallation is complete. Review the information on this screen, then click Finish to close the Uninstall Wizard. |
Note:
After the product is uninstalled, ensure that the ORACLE_HOME folder exists and it does not contain any files or folders. If there are any remaining files or folders in the ORACLE_HOME folder, delete them.Parent topic: Uninstalling the Software
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:
Oracle Internet Directory
14c (14.1.2.1.0) should be installed in a new
ORACLE_HOME
location that is separate from the
previous OID 12c (12.2.1.4.0)
ORACLE_HOME
.
In case of a standalone Oracle Internet Directory upgrade, you do not have to install Oracle Fusion Middleware Infrastructure. You can install Oracle Internet Directory directly selecting the Standalone option.
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:
Note:
For more information about installing Oracle Internet Directory, see Installing the Oracle Internet Directory Software in the Installing Oracle Internet Directory.
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:
-
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.
-
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.
- 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). - Upgrading Oracle Directory Integration Platform Schemas
Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.
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:
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
ORACLE_HOME/oracle_common/upgrade/bin
- (Windows)
ORACLE_HOME\oracle_common\upgrade\bin
- (UNIX)
- 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.
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.
-
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.- Backing Up the Domain
- Starting the Reconfiguration Wizard
- Reconfiguring the Oracle Directory Integration Platform Domain
Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.
Backing Up the Domain
Before running the Reconfiguration Wizard, create a backup copy of the domain directory.
- Create a backup of the domain directory.
- Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
- Verify that the backed up versions of the domain are complete.
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:
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.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.
- 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). - Upgrading Domain Component Configurations
Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain. - Starting Servers and Processes
After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers. - 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.
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:
- Go to the
oracle_common/upgrade/bin
directory:- (UNIX)
ORACLE_HOME/oracle_common/upgrade/bin
- (Windows)
ORACLE_HOME\oracle_common\upgrade\bin
- (UNIX)
- 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.
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:
- Starting Servers and Processes
After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers. - 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. - Adding the Cipher Suites (Optional)
Review the Secure Sockets Layer (SSL) modes available for Oracle Directory Integration Platform (ODIP). - 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. - 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. - 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.
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.
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:
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:
-
Start the WebLogic Administration Server. See Starting Servers and Processes.
-
Log in to the WebLogic Administration console using the following URL:
http://admin_host:admin_port/console
-
Click Lock & Edit.
-
Click Environments, and then click Servers.
-
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. -
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 forwls_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.
-
-
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:
-
Go to Services, and click Data Sources.
-
Select a data source that is targeted to
wls_ods1
. -
Go to the Targets tab, and deselect wls_ods1.
-
Select All Servers in the Cluster.
-
Click Save.
-
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.
-
-
In case of cluster (high availability) setup, do the following:
-
Click Environments and then click Coherence Clusters.
-
Select defaultCoherenceCluster and then click Members.
-
Select Cluster.
-
Select All Servers in the cluster.
-
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:
-
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
-
Create a named
DIP_14.1.2.1.0/configuration
using the following command:mkdir -p DIP_14.1.2.1.0/configuration
-
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
-
Restart the servers.
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:
-
Configure OID and ODIP in server auth mode. This is a recommended approach. Refer to the following sections for more information:
-
Configuring Secure Sockets Layer (SSL) in Administering Oracle Internet Directory
-
Configuring Oracle Directory Integration Platform for Oracle Internet Directory SSL Authentication in Administering Oracle Directory Integration Platform
-
-
Configure these additional anonymous ciphers along with the default additional ciphers supported by ODIP 14c (14.1.2.1.0). See, Adding Cipher Suites Configured for Oracle Internet Directory into Oracle Directory Integration Platform in the Administrator's Guide for Oracle Directory Integration Platform.
Note:
In case of a cluster setup, perform these steps for each of the Managed Servers where ODIP is deployed.
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.
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.
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.
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.
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.