Upgrading Enterprise Data Quality

8 Upgrading Enterprise Data Quality

To upgrade EDQ running on WebLogic Servers or Tomcat Servers from Release 11g or Release 12c (12.1.3) or Release 12c (12.2.1) to 12c (12.2.1.3.0) of EDQ, see Oracle Enterprise Data Quality Upgrade Guide.

Note:

You must review Oracle Fusion Middleware upgrade documentation before referring to the Oracle Fusion Middleware Oracle Enterprise Data Quality Upgrade Guide.

Read Planning an Upgrade of Oracle Fusion Middleware for additional guidelines for preparing to upgrade to Oracle Fusion Middleware 12c (12.2.1.3.0). This documentation also includes descriptions of terminology changes that you must understand to move forward to a 12c environment.

Upgrading from previous 12c releases to 12.2.1.3.0

Upgrading from an installation of EDQ 12c that uses the Oracle database and the WebLogic application server as its platform to EDQ 12.2.1.3.0 using the Oracle Database and Oracle WebLogic as its platform is essentially a two-part process:

Part 1: Perform a Partial Installation of EDQ 12.2.1.3.0

To perform a partial installation:

Ensure that your environment satisfies all EDQ 12.2.1.3.0 System Requirements, as outlined in Satisfying EDQ System Requirements, and upgrade your environment, if necessary.
Download EDQ 12.2.1.3.0, as described in Downloading EDQ.
Download the Fusion Middleware Infrastructure release 12.2.1.3.0.
If your environment's current Java Development Kit does not support EDQ 12.2.1, install a Java Development Kit to support EDQ 12.2.1, as described in Installing a Java Development Kit to Support EDQ.
If your environment's current Oracle Fusion Middleware Infrastructure does not support EDQ 12.2.1, install Oracle Fusion Middleware Infrastructure to support EDQ 12.2.1, as described in Installing Oracle Fusion Middleware Infrastructure (includes Oracle WebLogic Server).

Note:

The Oracle Fusion Middleware Infrastructure that you used to support your old release of EDQ will not support your new release of EDQ. Therefore, unless, you have already installed the new release of the Oracle Fusion Middleware Infrastructure for some other purpose, you will have to install it now.

The new release of the Fusion Middleware Infrastructure will have to be installed in a different Fusion Middleware Home to your old release.
If your environment's current Oracle Database does not support EDQ 12.2.1, upgrade the Oracle Database to a release that will support EDQ 12.2.1.
Install Enterprise Data Quality 12.2.1.3.0 assets, as described in Installing Enterprise Data Quality, ensuring that you install EDQ in your new Fusion Middleware Infrastructure's Fusion Middleware Home. This step entails installing the Oracle Fusion Middleware EDQ distribution. This is usually downloaded as a .zip file that contains a single file with a name similar to fmw_12.2.1.3.0_edq.jar. Running this .jar file invokes the Oracle Universal Installer. You do not need to configure or extend a WebLogic domain now, since you will upgrade the WebLogic domain using the Reconfiguration Wizard at a later stage.

Note:
This step places elements of Enterprise Data Quality in your environment's Fusion Middleware Home location. Some of these will be used later in the installation process. However, you will not have a working EDQ environment at this stage.

Part 2: Upgrade your Old EDQ Environment

Before you upgrade to the latest EDQ Environment, here are a few considerations:

When upgrading EDQ instances that are configured for high availability:

Enterprise Data Quality 11g and higher can be enabled for high availability by configuring several WebLogic Managed Servers within the same WebLogic Cluster. In releases of EDQ 11, and also in EDQ 12.1.3, it was necessary for each of these Managed Servers to have its own dedicated database repository (in other words, its own pair of Config and Results datasources), and its own dedicated config directory.

In EDQ 12.2.1, configuration for High Availability was simplified. From release 12.2.1.0.0 and above, all the WebLogic managed servers in a cluster can share the same database repository. In other words, only one pair of Config and Results datasources is required and all the WebLogic managed servers in a cluster can share the same base and local config directories.
Oracle recommends that when you upgrade an instance of EDQ 11g or 12.1.3 that is configured for high availability, you change its configuration to take advantage of the simplified approach to High Availability introduced in EDQ 12.2.1. To do this, perform the following tasks:
- Upgrade only one database repository (in other words, only one pair of Config and Results schemas) using the Upgrade Assistant.
- Run the Oracle Fusion Middleware Reconfiguration Wizard a single time, supplying the connection details of the database repository that you upgraded. As you run the Wizard, on the Advanced Options screen, ensure that you select the Managed Servers, Clusters and Coherence option, and then, referring to the EDQ High Availability Guide for release 12.2.1, configure your upgraded EDQ instance for High Availability using the new, simplified architecture.
- Ensure that all your WebLogic Managed Server's server parameters, including, its 'startup arguments' or 'Java options', are configured to point towards the same base and local config directories.
It is also possible to maintain the existing high availability configuration after an upgrade, by continuing to use multiple schemas and config areas. To do this:
- Run the Upgrade Assistant separately against each pair of Config and Results schemas.
- Disable coherence by setting coherence.clustering = false in the director.properties file.

To start upgrading your old environment:

Back up your old EDQ environment.

Before you begin, Oracle recommends that you make a complete backup of your old EDQ environment, including your EDQ domain. For instructions, see Backup and Recovery Strategies for Upgrade in the Planning an Upgrade of Oracle Fusion Middleware documentation.
Stop the WebLogic Server Administration Server and all managed servers.
Start the Upgrade Assistant, to upgrade your EDQCONFIG (configuration), EDQRESULTS (results), EDQSTAGING (only if upgrading from 12.2.1.x. This will not be present if upgrading from 12.1.3) and OPSS, IAU and STB schemas in the EDQ repository database.
1. Go to the following directory, where 12.2.1_FMW_HOME is the version 12.2.1.3.0 Oracle home directory:
  
  UNIX:
  
  12.2.1_FMW_HOME/oracle_common/upgrade/bin
  
  Windows:
  
  12.2.1_FMW_HOME\oracle_common\upgrade\bin
2. Run the following program:
  
  Linux or UNIX:
  
  ./ua
  
  Windows:
  
  ua.bat
At the Welcome screen, Review Important Reminders before Proceeding. The Welcome screen contains reminders to consider before proceeding with your upgrade. Make sure you read these and verify that you are ready to proceed. For assistance or more information on any screen, click Help. Otherwise, click Next.
Select the type of upgrade and then select All Schemas Used by a Domain option. In the Domain Directory field, select your old EDQ environment's domain directory (this is likely to be similar to /OLD_FMW_HOME/user_projects/domains/edq_domain). Click Next.
The Component List screen will display a list of the components (or in other words, schemas) to be upgraded in your old EDQ environment's domain. The following components will be listed:
- Oracle Enterprise Data Quality Results
- Oracle Audit Services
- Oracle Platform Security Services
- Common Infrastructure Services
- Oracle Enterprise Data Quality Configuration
Select the components and click Next.
In the Prerequisites screen, verify that you have met the prerequisites, and provided that you have, check the relevant boxes. Note that the Upgrade Assistant will not verify that the prerequisites have been met. Click Next.
Specify Database and Schema Credentials:
1. The EDQ Results schema, IAU, OPSS, STB, and EDQ Configuration schema screens are displayed in succession.
2. On the first screen, specify connection details for the database that contains the EDQ Results (EDQRESULTS) schema, and then click Connect. You are then prompted for the password for the schema user.
3. The remaining screens are automatically populated with the database connection and schema credentials that you supplied on the EDQ Results Schema screen. If these entries are not correct for any schema, change the entries and ensure that a database connection is made.
Complete the upgrade validation. On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded.
Initiate the Upgrade. Click Upgrade on the Upgrade Summary screen to initiate the upgrade. The Upgrade Progress screens shows information about the progress of the upgrade, and the Upgrade Success screen summarizes the upgrade.
Create the Required 12c Schemas.

Note:
You only need to create the staging schema if upgrading from 12.1.3. If upgrading from a previous version of 12.2.1 this step can be skipped.

Oracle Fusion Middleware Release 12.2.1 introduced schemas and tables that must be created with the 12.2.1 version of the Oracle Repository Creation Utility (RCU). This step of the upgrade must be performed before Reconfiguring the EDQ Domain.
To create the required 12.2.1 schemas, see Creating an EDQ Database Repository for release 12.2.1. Follow all of those instructions, but only select the following schema on the Select Components screen:
- EDQ Staging Repository (note that you will find this under the Oracle EDQ option).
Reconfigure the EDQ Domain. In this step you will run the Oracle Fusion Middleware Reconfiguration wizard to complete the upgrade of your WebLogic Server domain environment.
Check that the Staging Mode is set to Nostage, by performing the following steps:
1. Log in to the WebLogic Server Administration Server console from any web browser.
2. In the left pane, expand Environment and then click Servers. The Summary of Servers screen will be displayed.
3. In the Summary of Servers screen, click your EDQ Managed WebLogic Server (for example: edq_server1).
4. Select the Configuration tab, then the Deployment tab.
5. From the Staging Mode menu, ensure that select Nostage is selected, and, if it is not, select it. Do not change any other server settings.
6. Click Save.
Stop Node Manager:
1. If the Node Manager was not already running, and you started it using the command above, then stop it by closing the command shell from which it is running.
2. If Node Manager was already running (for example, because it was already running as a service in your environment), then stop it using the appropriate means (for example, stop the Node Manager service).
Start the Reconfiguration Wizard to upgrade the EDQ domain:
1. Go to the following directory, where 12.2.1_FMW_HOME is the version 12.2.1 Oracle home directory:
  
  Windows:
  
  12.2.1_FMW_HOME\oracle_common\common\bin
  
  UNIX:
  
  12.2.1_FMW_HOME/oracle_common/common/bin
2. Start the domain reconfiguration wizard.
  
  Windows:
  
  reconfig.cmd -log=log_file
  
  UNIX:
  
  ./reconfig.sh -log=log_file
Specify the full path and file name in place of log_file. Creating a log file can be helpful if you need to troubleshoot the reconfiguration process.

Note:

If the following error message is displayed, it indicates 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
Specify the domain. On the Select Domain screen, specify the full path to the location of your old EDQ domain (it is likely to be similar to FMW_HOME/user_projects/domains/edq_domain or FMW_HOME\user_projects\domains\edq_domain). You can also click Browse and use the file manager window to help you select the domain location.
View the Reconfiguration Setup Progress.

The Reconfiguration Setup Progress displays the reconfiguration progress and verifies whether the base domain that you selected can be reconfigured to the 12.2.1 domain. The message Core WLS Infrastructure Reconfigured Successfully! indicates that the domain can be reconfigured to the 12.2.1 domain, and you can click Next to go to the next step. If this message is not returned, the domain cannot be reconfigured to the 12.2.1 domain. If this happens, check to see if the EDQ version is earlier than version 11g. If so, then you must first upgrade to EDQ 11g and then upgrade to version 12.2.1.
Select the Domain Mode and JDK. It is not possible to change the Domain Mode from development to production or vice versa.

On the Domain Mode and JDK screen, specify the location of the Java Development Kit (JDK) to use in the new EDQ domain. This must be a JDK that conforms to the system requirements of your new EDQ environment.
Select the Database Configuration Type:
1. In the Database Configuration Type screen, the RCU Data option should be selected by default. The connection details for your EDQ repository database should be automatically populated, and the schema owner and password for the Common Infrastructure schema (STB) should be displayed. If this information is not automatically populated, or is not correct, make any necessary amendments.
2. Click Get RCU Configuration. The Reconfiguration Wizard should report that it can connect to the Database Server and that it can retrieve schema data and bind local schema components with the retrieved data. If these steps fail, amend the connection data and click Get RCU Configuration again. Otherwise, click Next.
Check the JDBC Component Schema. On the JDBC Component Schema screen, the schemas associated with your old EDQ domain are listed in the lower half of the screen. If you need to make changes, select the check box next to the data source name and then make the changes.

Note:
The correct connection details for the EDQ Staging schema that you created using the Repository Creation Utility in step 5, above, may not be displayed. If they are not, amend them so that they are correct.
Test the JDBC Component Schema. On the JDBC Component Schema Test screen, test the data source connections that were detected. Select the schemas that you want to test and then click Test Selected Connections.

Note:
To test a connection, the database to which you are connecting must be running.
Select Optional Advanced Configuration Options to select additional domain options:
1. To make changes to the Managed Server configuration, select Managed Servers, Clusters and Coherence. For help with any of the options, click the Help button.
2. To skip making these changes, click Next.
Initiate the Domain Reconfiguration. On the Configuration Summary screen, review the configuration and then click Reconfig to start the reconfiguration process, or click Back to make changes.
Finish the Reconfiguration. Wait for the message that states, Domain Reconfiguration Applied Successfully and then click Next.

A check mark and the message Oracle WebLogic Server Reconfiguration Succeeded indicate that the reconfiguration was successful. Click Next, and then click Finish to dismiss the Reconfiguration wizard.
Follow the instructions below to start the Upgrade Assistant and upgrade EDQ's domain configuration.
1. Go to the following directory, where 12.2.1_FMW_HOME is the version 12.2.1 Oracle home directory.
  
  Windows:
  
  12.2.1_FMW_HOME\oracle_common\upgrade\bin
  
  UNIX:
  
  12.2.1_FMW_HOME/oracle_common/upgrade/bin
2. Run the following program:
  
  Linux or UNIX:
  
  ./ua
  
  Windows:
  
  ua.bat
3. At the Welcome screen, Review Important Reminders before Proceeding. The Welcome screen contains reminders to consider before proceeding with your upgrade. Make sure you read these and verify that you are ready to proceed. For assistance or more information on any screen, click Help. Otherwise, click Next.
  
  Note:
  For more information about the following screens, see "Upgrading Oracle WebLogic Component Configurations" in Upgrading with the Upgrade Assistant.
4. At the Selected Schemas screen, select the All Configurations Used By a Domain option. At this point the name of the screen will change to All Configurations. In the Domain Directory field, select your old EDQ environment's domain directory (this is likely to be similar to /OLD_FMW_HOME/user_projects/domains/edq_domain), and click Next.
5. At the Component List screen, review the list of components to be upgraded (it should consist of Oracle JRF, System Components Infrastructure, and Oracle Enterprise Data Quality Configuration), and click Next.
6. At the Prerequisites screen, verify that you have met the prerequisites, and, provided that you have, check the relevant boxes (note that The Upgrade Assistant will not verify that the prerequisites have been met.). Then click Next.
7. At the Examine screen, the Upgrade Assistant will validate that the components can be upgraded, returning statuses for either upgrade not necessary or succeeded for each of them. When the examination has finished, click Next.
8. At the Upgrade Summary screen, click Upgrade.
9. At the Upgrade Progress screen, wait until the upgrade has finished, and then click Next.
10. At the Upgrade Success screen, click Close.
Apply the Upgrade Changes to the Base Domain, using the following steps:
1. Start the WebLogic Node Manager for the upgraded EDQ domain.
2. Start the WebLogic Server Administration Server from the upgraded EDQ domain. If it is running, stop and then restart it.
  
  Windows:
  
  DOMAIN_HOME\bin\startWebLogic.cmd
  
  UNIX:
  
  DOMAIN_HOME/bin/startWebLogic.sh
3. Log in to the WebLogic Server Administration Server console from any web browser.
4. In the Domain Structure list, click Deployments.
5. Under Deployments, select edq and then click Update.
6. Click Next.
7. Click Finish.
8. To complete the upgrade, start the EDQ managed server.
  
  Note:
  
  The startManagedWebLogic.sh script is located in your EDQ WebLogic domain's bin directory. Running this script is one method of starting the EDQ WebLogic Managed Server. The startManagedWebLogic.sh script may be overwritten when the EDQ WebLogic Domain is reconfigured. Therefore, if you customized the script, any customization may have been lost during the upgrade process. This is a particularly important point to note if you embedded EDQ's Server Parameters (in other words, its 'startup arguments' or 'Java options') within this script. Without these, the EDQ Managed Server may not function correctly.
  
  See Setting Server Parameters to Support Enterprise Data Quality, for more information about EDQ's server parameters.
Open a Web Browser, and navigate to your upgraded EDQ environment's Launchpad. Unless you changed any of the default options when installing EDQ, its address would be http://<your-server-name>:8001/edq.
From the Launchpad, open the Director user interface and check to see the version of EDQ to confirm that the version is upgraded. From the menu in Director, click the Help > About option to check the version.
Verify that all your projects have been successfully migrated.

Note:
On a correctly upgraded system, you do not need to specify the passwords for any data stores such as Oracle. No additional settings are required to ensure that you do not specify the passwords again.
If any of your processes use Match Review, you will need to run these (or jobs of which they are a part) with intelligent execution turned off before you can access Match Review. You can turn off Intelligent Execution in a job or process's Run Preferences.