This chapter describes how to upgrade EDQ running on WebLogic Servers from Release 11g to Release 12c (12.1.3) of EDQ.
Note:
The topics in this document must be followed in the order presented.
This chapter includes the following sections, presented in order of their intended execution:
Section 8.1, "Preparing for an Enterprise Data Quality Upgrade"
Section 8.2, "Migrating a File-Based Keystore to an OPSS Security Store"
Section 8.6, "Applying the Upgrade Changes to the Base Domain"
Note:
If upgrading EDQ on Apache Tomcat, see Chapter 9, "Upgrading Enterprise Data Quality On Tomcat Servers."
These instructions provide an overview of the preparatory work you must do before running any upgrade programs.
Table 8-1 Steps to Prepare for an EDQ Upgrade (in their required order)
| Step | Action to Perform |
|---|---|
|
Review Oracle Fusion Middleware upgrade documentation. |
Read Planning an Upgrade of Oracle Fusion Middleware for additional guidelines for preparing to upgrade to Oracle Fusion Middleware Release 12c (12.1.3). This documentation also includes descriptions of terminology changes that you must understand to move forward to a 12c environment. |
|
Determine whether your current EDQ version is a valid upgrade starting point. |
An upgrade starting point is a specific version of EDQ that you must be running in order to upgrade directly to Release 12c (12.1.3) with the Oracle Fusion Middleware Upgrade Assistant. Valid starting point: EDQ version 11.1.1.7 or later that was installed with Oracle Universal Installer (OUI). If your current version satisfies this requirement, you can use the Upgrade Assistant to upgrade your installation directly to Release 12c (12.1.3). OUI was first available to EDQ in that release. Action: Proceed with the steps in this documentation. Invalid starting point: Any version of EDQ earlier than Release 11g (11.1.1.7). Action: First upgrade your software to at least version 11.1.1.7, and then return to this documentation to upgrade that environment to Release 12c (12.1.3). To upgrade to version 11.1.1.7, see Oracle Enterprise Data Quality Installation and Upgrade Guide Release 11g R1 (11.1.1.7) at
|
|
Back up your 11g Fusion Middleware environment. |
Before you begin, Oracle recommends that you make a complete backup of your 11g environment, including your EDQ domain. For instructions, see ”Backup and Recovery Strategies for Upgrade” in the Planning an Upgrade of Oracle Fusion Middleware. |
|
Stop all EDQ servers and components in the current EDQ domain. |
See ”Starting and Stopping Oracle Fusion Middleware” in Administering Oracle Fusion Middleware. All EDQ components must remain shut down until you are prompted to start them at the end of these upgrade instructions. |
|
Run the WebLogic Server Administration Server |
Keep the WebLogic Server Administration Server running until you are prompted to shut it down. You will be performing tasks from the Administration Server. |
|
Download EDQ Release 12c (12.1.3) |
Follow the instructions in Section 1.5, "Downloading EDQ." |
|
Install EDQ Release 12c (12.1.3) |
Install the 12c software. See Section 3, "Installing Enterprise Data Quality." |
|
Upgrade EDQ version 12.1.3. |
After satisfying all of the steps in this checklist, you may upgrade to Release 12c (12.1.3) by following these instructions in the order shown: Section 8.2, "Migrating a File-Based Keystore to an OPSS Security Store" Section 8.3, "Upgrading the EDQ and OPSS Schemas" Section 8.5, "Reconfiguring the EDQ Domain" Section 8.6, "Applying the Upgrade Changes to the Base Domain" |
All Oracle Fusion Middleware products must now store their security credentials within an Oracle Platform Security Services (OPSS) schema in an Oracle database. The Oracle term for this is security store. If you were using a file-based keystore in the configuration directories, you must now use an OPSS DB-based security store.
To convert to an OPSS DB-based security store, you create the OPSS, Audit Services, and Audit Services Viewer schemas. The Audit Services and Audit Services Viewer schemas are required by the Oracle Platform Security Services schema. After creating these schemas, you then create a WebLogic Server data source for the OPSS schema, and then reassociate the EDQ keystore to the OPSS schema.
Run the Fusion Middleware 11g Repository Creation Utility (RCU) to create the OPSS schema. For assistance or more information on any screen, click Help.
Download the 11g Repository Creation Utility (RCU) from Oracle. For instructions, see
http://docs.oracle.com/cd/E23104_01/download_readme_ps6/download_readme_ps6.htm#BABHDBJC
Extract the contents to a directory of your choice; this directory will be referred to as the RCU_HOME directory. On Windows operating systems, make sure that you do not unzip the RCU file to a directory name that contains spaces.
Start the WebLogic Server Administration Server.
Run the command shell or console of the operating system.
Start RCU from the bin directory inside the RCU_HOME directory.
Note:
If you are running RCU using a non-English database, set the following environment variables:
setenv LANG en_US.UTF8
setenv LC_ALL $LANG
setenv NLS_LANG american_america
On Linux:
./rcu
On Windows:
rcu.bat
Click OK to pass through the Welcome screen.
On the Create Repository screen, select Create, then click Next.
On the Database Connection Details screen, enter the connection details for the EDQ repository database and the login credentials of the EDQ database user.
On the Select Components screen, choose to use an existing schema prefix or create a new prefix. Under Oracle AS Repository Components, expand AS Common Schemas and then select Oracle Platform Security Services.
On the Schema Passwords screen, supply passwords for the schema owner.
On the Map Tablespaces screen, use one default tablespace and one temporary tablespace. The default tablespace names are displayed.
On the Summary screen, click OK to complete the creation of the schema.
Use the WebLogic Server Administration Console to create a generic JDBC data source for the OPSS schema. For assistance or more information on any screen, click Help.
In the Domain Structure tree, expand Services, then select Data Sources.
On the Summary of Data Sources screen, click New and select Generic Data Source.
On the JDBC Data Sources Properties screen, enter the data source name and the JNDI name of the OPSS schema that you created with the 11g RCU in Task 1. The OPSS DataSources name is opss-data-source and the JNDI name is similar to this example: jdbc/OpssDataSource. Select the database type as Oracle, and then press Next.
On the Create a New JDBC Data Source screen, the default JDBC driver that is required for the Oracle database is displayed and selected. Click Next.
Note:
Note: You must install JDBC drivers before you can use them to create database connections. Some JDBC drivers are installed with WebLogic Server, but many are not installed.
On the Transaction Options screen, keep the Supports Global Transactions box selected, and then click Next.
On the Connection Properties screen, enter the connection details and credentials to connect to the OPSS schema that you created with the 11g RCU in Task 1.
On the Test Database Connection screen, review the connection parameters and click Test Configuration. Results from the connection test are displayed at the top of the page. If the test is unsuccessful, correct any configuration errors and retry the test. If the JDBC driver you selected is not installed on the WebLogic Server Administration Server, click Next to skip this step. Install the driver after finishing this procedure.
On the Select Targets page, select the WebLogic Server servers or clusters on which you want to deploy the data source.
Click Finish to save the JDBC data source configuration and deploy the data source to the targets that you selected.
To activate these changes, click Activate Changes in the Change Center of the Administration Console. Not all changes take effect immediately, but all will take effect when you restart the server at the end of the EDQ upgrade process.
Use the WebLogic Server Scripting Tool (WLST) to reassociate the file-based keystore to the OPSS data source that you created with the WebLogic Server Administration Console.
From the 11g $EDQ_HOME/oracle_common/common/bin directory, issue the following command to run the WebLogic Server Scripting Tool (WLST).
UNIX/Linux:
./wlst.sh
Windows:
wlst.cmd
In WLST, connect to the Oracle database where you want to create the security store.
connect('username', 'password', 'host:port')
Where:
username is the name of the admin user.
password is the admin user's password.
host is the name of the database host.
port is the connection port to the database.
Reassociate the OPSS schema from the file-based format to the database format.
reassociateSecurityStore(domain="upgradeDomain",
servertype="DB_ORACLE", jpsroot="cn=jpsroot",
datasourcename="jdbc/OpssDataSource", join="false");
Where:
datasourcename is the name of the new OPSS JNDI data source that you created in the WebLogic Server Administration Console in Task 2. For more information about this script, see
http://docs.oracle.com/cd/E29542_01/core.1111/e10043/cfgauthr.htm#JISEC2675
Note:
Do not restart the EDQ server or managed servers yet. Complete the rest of the upgrade steps. The changes you made are stored on the server and will propagate to the rest of the servers when you restart the servers after upgrade.
Follow the instructions in this section to upgrade your EDQCONFIG (configuration), EDQRESULTS (results), and OPSS schemas in the EDQ database repository.
Note:
The Upgrade Assistant requires that you shut down all servers in the domain for the duration of the schema upgrade.
Go to the following directory, where 12c_FMW_HOME is the version 12c Oracle home directory.
On UNIX operating systems:
12_FMW_HOME/oracle_common/upgrade/bin
On Windows operating systems:
12_FMW_HOME\oracle_common\upgrade\bin
Run the following program:
On Linux or UNIX operating systems:
./ua
On Windows operating systems:
ua.bat
The Welcome screen contains important 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.
Note:
For more information about the following screens, see ”Upgrading Schemas with the Upgrade Assistant” in Upgrading with the Upgrade Assistant.
Select Schemas. The Upgrade Assistant will list the schemas available for upgrade on the next screen.
The title of the screen changes to ”Schemas” when you select Schemas.
The Available Components screen lists the schemas that are available for upgrade.
Select Oracle Fusion Middleware and then make certain that all of the following schemas are selected:
Oracle Enterprise Data Quality Configuration Schema
Oracle Enterprise Data Quality Results Schema
Oracle Platform Security Services Schema
On the Domain Directory screen, enter the directory for your version 11g EDQ domain. For example, C:\Oracle\Middleware\FMW_HOME\user_projects\domains\edq_domain.
You must check the boxes before you can continue. The Upgrade Assistant will not verify that the prerequisites have been met.
On the Prerequisites screen, check and verify the items. The Upgrade Assistant does not verify that the prerequisites have been met.
The EDQ Results schema, OPSS, and EDQ Configuration schema screens are displayed in succession.
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.
These 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 either schema, change the entries and ensure that a database connection is made.
On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded.
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.
Oracle Fusion Middleware Release 12c (12.1.3) introduces new schemas and tables that must be created with the Release 12c (12.1.3) 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 12c schemas, see Section 4.2, "Creating an EDQ Database Repository" and follow all of those instructions, but only select the following schemas on the Select Components screen:
Audit Services
Audit Services Viewer
Audit Service Append
Common Infrastructure Services Schema
Note:
Do not select the OPSS schema on the Select Components screen. You already created this schema with the 11g RCU in Section 8.2, "Migrating a File-Based Keystore to an OPSS Security Store" and updated it with the Upgrade Assistant (UA) utility in Section 8.3, "Upgrading the EDQ and OPSS Schemas."
Run the Oracle Fusion Middleware reconfiguration wizard to complete the upgrade of your WebLogic Server domain environment.
For assistance with any screen, click Help.
This task sets the staging mode to the required setting of nostage.
Log in to the WebLogic Server Administration Server console from any web browser.
In the left pane, expand Environment.
Under Servers, select edq_server1.
Select the Configuration tab, then the Deployment tab.
From the Staging Mode menu, select nostage. Do not change any other server settings.
Click Save.
This task ensures that Node Manager has been started at least once since it was installed. Starting Node Manager creates a set of script files that must be moved from the old domain to the version 12c domain. Performing this task eliminates the need for extra steps when upgrading your domain.
From the EDQ 11g domain, run the following command to start Node Manager. For hostname, specify the name of the system where Node Manager is installed, and for port specify the port number on which it runs.
Windows:
startNodeManager.cmd hostname port
UNIX:
sh startNodeManager.sh hostname port
Stop Node Manager by closing the command shell from which it is running.
This task upgrades the EDQ domain.
Stop the WebLogic Server Administration Server and all managed servers.
Go to the following directory, where 12c_FMW_HOME is the version 12c Fusion Middleware home directory.
On UNIX operating systems:
12c_FMW_HOME/oracle_common/common/bin
On Windows operating systems:
12c_FMW_HOME\oracle_common\common\bin
Start the domain reconfiguration wizard.
On UNIX operating systems:
./reconfig.sh -log=log_file
On Windows operating systems:
reconfig.cmd -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
On the Select Domain screen, specify the full path to the location of the 11g EDQ domain (FMW_HOME/user_projects/domains/base_domain or FMW_HOME\user_projects\domains\base_domain). You can also click Browse and use the file manager window to help you select the domain location.
The Reconfiguration Setup Progress displays the reconfiguration progress and verifies whether the base domain that you selected can be reconfigured to the 12c domain. The message ”Core WLS Infrastructure Reconfigured Successfully!” indicates that the domain can be reconfigured to the 12c 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 12c 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 12c. See Section 8.1, "Preparing for an Enterprise Data Quality Upgrade."
Domain Mode cannot be changed.
On the Domain Mode and JDK screen, specify the location of the Java Development Kit (JDK) to use in the domain. This must be the JDK that you installed in Section 2.2, "Installing a Java Development Kit to Support EDQ."
On the JDBC Data Sources screen, the JDBC data sources associated with the 11g EDQ domain are listed in the lower half of the screen. These data sources should be the EDQ configuration and results schemas. If you need to make changes, select the check box next to the data source name and then make the changes.
On the JDBC Data Sources 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.
On the Database Configuration Type screen, select the RCU Data option to get the database connection information for the schemas that you created when you ran the 12.1.3 RCU. The domain configuration wizard will use the connection information to configure the data sources for these components.
On the JDBC Component Schema screen, select the OPSS schema and specify the 11g data source settings for that schema at the top of the screen.
On the JDBC Component Schema Test screen, select all of the schemas, and then click Test Selected Connections.
Note:
To test a connection, the database to which you are connecting must be running.
On the Node Manager screen, you will migrate the Node Manager configuration and, optionally, modify advanced options. Select Per Domain Default Location under Node Manager Type and Migrate Existing Configuration under Node Manager Configuration. Provide Node Manager login credentials, and then click Next.
On the Advanced Configuration Screen, you can select additional domain options.
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.
To skip making these changes, click Next.
On the Configuration Summary screen, review the configuration and then click Reconfig to start the reconfiguration process, or click Back to make changes.
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. View the results, and then click Finish to dismiss the reconfiguration wizard.
These steps apply the changes that you made during the upgrade of the EDQ domain to the base domain.
Start the WebLogic Server Administration Server from the upgraded EDQ domain. If it is running, stop and then restart it.
(UNIX) DOMAIN_HOME/bin/startWebLogic.sh
(Windows) DOMAIN_HOME\bin\startWebLogic.cmd
Log in to the WebLogic Server Administration Server console from any web browser.
Navigate to Deployments.
Under Deployments, select EDQ and then click Update.
Click Next.
Click Finish.
Start the EDQ managed server. This is required to complete the upgrade.
If the upgrade process fails while running the Upgrade Assistant, close the Upgrade Assistant, correct the issue if you can, and then restart the Upgrade Assistant.
If you migrated a file-based keystore to an OPSS security store, one problem that can occur is if the WebLogic Server Administration Server is restarted after the migration and reassignment (see Section 8.2, "Migrating a File-Based Keystore to an OPSS Security Store" for the steps). This causes an error because the EDQ secret key is not copied to the database security store. If this may be the cause of the failure, run the WebLogic Scripting Tool (wlst) and issue the following commands:
connect("user", "password", "localhost:7001")
getOpssService("KeyStoreService").deleteKeyStore("edq", "default", "")
Where: user is the EDQ database user and password is the password for that user.
Upon successful completion, a message of ”Keystore deleted” is returned.
If the cause of a problem is not immediately apparent, or if the upgrade fails after running the Upgrade Assistant, see ”Troubleshooting Your Upgrade” in Upgrading with the Upgrade Assistant.