This chapter describes how to upgrade EDQ running on Tomcat 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:
Note:
If upgrading EDQ on Oracle WebLogic Server, see Section 8, "Upgrading Enterprise Data Quality On WebLogic Servers."
Before performing the upgrade, perform these pre-upgrade steps.
You can perform a direct upgrade to version 12c of EDQ on Tomcat only from Tomcat version 7. If you are running Tomcat 6, you must upgrade Tomcat to version 7 before proceeding with the EDQ upgrade. See the Apache Tomcat documentation at
Before you begin, Oracle recommends that you make a complete backup of your 11g environment.
These steps perform the upgrade of EDQ. They assume that you have Tomcat 7 installed. See Section 9.1, "Preparing for your Oracle Enterprise Data Quality Upgrade" if this is not the case.
The steps in the upgrade are as follows:
This task installs the product files for EDQ Release 12c (12.1.3).
Stop EDQ 11.1.1.7 server.
Install the EDQ 12c files. See Chapter 3, "Installing Enterprise Data Quality."
This task verifies whether the 11g configuration schema can be migrated to the 12c version.
Navigate to the EDQ 12.1.3 directory.
Ensure that the path to your JDK executable is set correctly to the JDK you installed for EDQ.
Run the pre-migration report by running the following command.
java -jar migration.jar premigrate dbtype:dbid@host:port/user/password
where:
dbtype is pgsql for PostgreSQL or oracle for Oracle.
dbid is the database name for PostgreSQL or the SID for Oracle.
host is the name of the database host machine.
port is optional and should be used if the database is running on a port number other than the default port number. If no value is specified, the default port for the database type is assumed.
user is the user ID that EDQ uses to connect to the Director database.
password is the password of the database user.
Examine the pre-migration report. If any issues are reported, you must resolve them before proceeding with Task 3.
This task migrates the EDQ Release 11g (11.1.1.7) configuration schema to the EDQ Release 12c (12.1.3) configuration schema. EDQ automatically migrates the results schema on startup, and it is not touched in this procedure.
From the EDQ version 12.1.3 installation directory (EDQ_HOME), run the migration.jar file. Use one of the following commands (all on one command line), depending on the database you are using:
PostgreSQL database:
$FMW_HOME\edq\oracle.edq -jar migration.jar migrate postgres:databaseName@machinename:port/user/password
Oracle database:
$FMW_HOME\edq\oracle.edq -jar migration.jar migrate oracle:sid@machinename:port/user/password
For a description of the input variables of this command, see Task 2.
This task migrates the EDQ Release 11g (11.1.1.7) Case Management schema to the EDQ Release 12c (12.1.3) Case Management schema.
From the EDQ version 12.1.3 installation directory (EDQ_HOME), run the migration.jar file with the cm parameter. Use one of the following commands (all on one command line), depending on the database you are using:
PostgreSQL database:
$FMW_HOME\edq\oracle.edq -jar migration.jar cm postgres:databaseName@machinename:port/user/password
Oracle database:
$FMW_HOME\edq\oracle.edq -jar migration.jar cm oracle:sid@machinename:port/user/password
For a description of the input variables of this command, see Task 2.
This task updates the base and local configuration directories, updates the EDQ connections to the repository databases, and modifies the functional packs that you are using in your EDQ configuration.
Run the configapp.jar file from the version 12.1.3 EDQ installation directory (EDQ_HOME).
$FMW_HOME\edq\oracle.edq -jar configapp.jar
The EDQ Configuration Application starts.
On the first screen, click Begin to start the upgrade steps.
On the Configuration Directory screen, select Update an existing configuration directory. Either accept the default EDQ base and local configuration directory locations, or browse to the correct ones.
On the Functional Packs screen, select the functional packs that you want to use in this installation of EDQ. Make certain to select a pack if you plan to use any configuration packages that use the processors in that pack.
On the Configure Config repository database screen, specify the connection details for the configuration schema or accept the defaults shown.
On the Configure Results repository database screen, specify the connection details for the results schema or accept the defaults shown.
On the Selected options screen, review the configuration that you specified. Click Back to make changes to your specifications, or click Finish to accept the upgrade selections.
On the EDQ Configuration Application screen, wait until the configuration details are applied, and then click Close. If you want to do the configuration over again, click Restart to launch the configuration application again.
This task performs the steps that complete the upgrade.
Deploy the ADF library that supports EDQ Release 12c (12.1.3). For more information, see Section 5.3, "Configuring Tomcat Application Server."
Update the library path for Tomcat.
Redeploy the edq.war file from the EDQ 12c installation directory (EDQ_HOME). For more information, see Section 5.7, "Deploying the EDQ Application on a Tomcat Application Server."
Start the Tomcat application server.
Make certain that the version is correct by checking the EDQ logs, the launch pad, and the EDQ clients.