4 Upgrading Oracle Directory Integration Platform to 12c (12.2.1.4.0)
You can upgrade Oracle Directory Integration Platform from Oracle Fusion Middleware Release 12c (12.2.1.3.0) to 12c (12.2.1.4.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.
Caution:
Before upgrading to 12.2.1.4.0 release, ensure that the 12.2.1.3.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.3.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.3.0) in the existing Oracle home. |
|
Required Install Oracle Fusion Middleware Infrastructure and Oracle Internet Directory 12c (12.2.1.4.0) in the new Oracle home. |
|
Required Start the servers. |
When the upgrade process is complete, restart the 12c (12.2.1.4.0) instance. |
Note:
The Oracle Directory Integration Platform version label remains 12.2.1.3.0 post upgrade to 12c (12.2.1.4.0).
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.
Note:
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 and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager.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, such as Oracle HTTP Server, 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 WebLogic
Server 12.1.3.
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.
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.Installing Oracle Internet Directory
Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Internet Directory (OID) 12c (12.2.1.4.0) distributions on the target system and install them using Oracle Universal Installer.
Note:
Oracle Internet Directory 12c (12.2.1.4.0) should be installed in a new ORACLE_HOME
location that is separate from the previous OID 11.1.1.9.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.
To install the 12c (12.2.1.4.0) distributions:
Note:
For more information about installing Oracle Internet Directory, see Installing the Oracle Internet Directory Software in the Installing Oracle Internet Directory.
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 process using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.To start your Fusion Middleware environment, follow the steps below:
Step 1: Start the Administration Server
When you start the Administration Server, you also start the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.
To start the Administration Server, use the startWebLogic
script:
-
(UNIX)
NEW_DOMAIN_HOME/bin/startWebLogic.sh
-
(Windows)
NEW_DOMAIN_HOME\bin\startWebLogic.cmd
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 Oracle Identity Management Components
Start any Oracle Identity Management components, such as Oracle Internet Directory, that form part of your environment:-
(UNIX)
NEW_DOMAIN_HOME/bin/startComponent.sh component_name
-
(Windows)
NEW_DOMAIN_HOME\bin\startComponent.cmd component_name
Step 4: Start the 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
When prompted, enter your user name and password.
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 5: 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.