This chapter describes how to upgrade EDQ from previous releases to the 11g (11.1.1.9) release using the includes the following sections:
Use the following sections to prepare to upgrade EDQ on your server:
The EDQ 11g Release 1 (11.1.1.9) has fully refactored results tables so all process tasks in jobs that have previous results (upgraded from an earlier version of EDQ) must be run with Intelligent Execution turned off to generate new results tables in the correct format. Process tasks that run with Intelligent Execution turned on will generate an error. This does not affect any processes that do not have results generated from previous versions.
After upgrading to EDQ 11g Release 1 (11.1.1.9), make sure that all jobs that have existing results (in the upgraded EDQ results database) are run with Intelligent Execution turned off on all process tasks, in order to generate new results tables.
Process tasks that run with Intelligent Execution turned on will generate an error if results tables already exist.
You must ensure that your EDQ installation is one of the supported configurations, see Section 2.2.1, "Hardware and Software Requirements."
If you are not upgrading from EDQ Release 11g R1 (11.1.1.7.#), you must gather and note the following information:
The location of your existing config directory is in the configdir.txt file in the WEB-INF directory of the deployed application. Any custom configuration in this directory will later be copied into new directories supporting EDQ 11g.
The connection details to the EDQ 11g Release 1 (11.1.1.9) repository database schemas (DIRECTOR and RESULTS); this information is located in your director.properties file. These schemas will be upgraded to support EDQ.
Use one of the following sections to upgrade EDQ:
Section 7.2.1, "Upgrading From EDQ Release 11g R1 (11.1.1.7.4)"
Section 7.2.2, "Upgrading EDQ From Releases Prior to the Release 11g R1 (11.1.1.7.3)"
All of the files in the new EDQ 11g Release 1 (11.1.1.9) must be installed on your system before attempting an upgrade so you must run the EDQ Release 11g R1 (11.1.1.9) OUI installer, specifying the current EDQ home directory where you installed the files for EDQ 11.1.1.7.4 so that these files are overwritten with the EDQ 11.1.1.9 files, as described in Chapter 4, "Running the EDQ Installer."
Then you use the following steps to upgrade your server from EDQ Release 11g R1 (11.1.1.7.4) to the EDQ Release 11g R1 (11.1.1.9).
Stop your EDQ Application Server (Tomcat, WebLogic Server, or WebSphere).
Remove the previous application deployment:
Delete the existing EDQ WAR file and expanded directory of the same name in the Tomcat webapps directory. Copy the new EDQ Release 11g R1 (11.1.1.9) WAR file to the Tomcat webapps directory.
Update your EDQ deployment to use the new EDQ Release 11g R1 (11.1.1.9) edq.ear file. The new file replaced the old file in the same location when you installed the new EDQ files so you can updating your deployment using the WebLogic Server Administration Console. For more information, see Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server 11g Release 1 (10.3.6).
Undeploy the existing EDQ WAR file then deploy the new EDQ Release 11g R1 (11.1.1.9) WAR file using the WebSphere Administration Console.
Start your EDQ Application Server.
You begin the upgrade process by running the EDQ Release 11g R1 (11.1.1.9) OUI installer as described in Chapter 4, "Running the EDQ Installer."
All of the files in the new EDQ 11g Release 1 (11.1.1.9) must be installed on your system before attempting an upgrade so you must run the EDQ Release 11g R1 (11.1.1.9) OUI installer as described in Chapter 4, "Running the EDQ Installer."
Next, you use the pre-migration and migration scripts that are Java Archive (JAR) files and part of the EDQ distribution installed by the EDQ Release 11g R1 (11.1.1.9) OUI installer. These scripts are packaged into and executed using the migration.jar file. If any migration issues exist, a report is produced detailing the problems so that you can correct them.
Navigate to the directory containing migration.jar that you installed in the preceding section.
Stop your application server.
Ensure that your PATH variable includes the location of your JDK/JRE executable.
If you are using Case Management, run the pre-migration report by running the following command with db_connection specifying how to connect to your Director database schema:
java -jar migration.jar premigrate db_connection
For example, your database connection might be similar to the following:
dbtype:dbid@host:port/user/password
The previous example syntax is explained as follows:
dbtype should be set to pgsql for PostgreSQL databases or oracle for Oracle Databases.
dbid should be set to the database name for PostgreSQL databases or the SID for Oracle Databases.
host should be set to the name of the RDBMS host machine.
port is optional. If no value is specified, the default port for the database type is assumed. If the database is running on a non-default port number, the value of the database port number should be specified.
user should be set to the user ID that EDQ uses to connect to the Director data base.
password should be set to the database user's password and defaults to the user name if no password is provided.
Examine the pre-migration report. If any issues are noted in the output from the pre-migration report, they should be addressed before proceeding to the next step.
Upgrade your Case Management schema by running the following command with db_connection specifying how to connect to your Case Management schema:
java -jar migration.jar cm db_connection
The syntax for the database connection, db_connection, is explained in step 4.
For example, to upgrade an Oracle instance on a locally deployed Oracle Database with the SID of orcl and a user name of director, then the command is as follows with password specifying the password for the director user:
java -jar migration.jar cm oracle:orcl@localhost:1521/director/password
Note:
RCU should not be used to create the EDQ schemas.
Upgrade your Director database schema by running the following command with db_connection specifying how to connect to your Director database schema:
java -jar migration.jar migrate db_connection
The syntax for the database connection, db_connection, is explained in step 4.
For example, to upgrade an Oracle instance on a locally deployed Oracle Database with the SID of orcl and a user name of director, then the command is as follows with password specifying the password for the director user:
java -jar migration.jar migrate oracle:orcl@localhost:1521/director/password
Note:
RCU should not be used to create the EDQ schemas.
Finally, you use one of the following sections to upgrade your server from all EDQ releases prior to Release 11g R1 (11.1.1.7.3) as appropriate for your application server:
Use the following steps to upgrade EDQ in a WebLogic Server environment.
Run the WebLogic Server Configuration Wizard and provide your existing EDQ domain information. The new EDQ configuration directories, oedq.home and oedq.local.home are created in the edq directory of your EDQ domain.
Copy the contents of your existing (pre-upgrade) EDQ config directory, that you previously noted, to the new oedq.local.home directory, with the exception of:
logs subdirectorydirector.properties fileCopy in any override settings from your existing director.properties file to the new director.properties file in your new oedq.local.home directory, taking care to retain the database connections settings in the new file.
For example, you may have modified director.properties file to set a custom path to a file landing area, set the number of processing threads for your server to use, or adjusted the path to the server that is sent in email notifications.
Ensure that startscriptenabled parameter is set to true in your nodemanager.properties file.
Start your WebLogic Servers.
Use the following sections to upgrade EDQ in a Tomcat or WebSphere Server environment.
Remove the previous application deployment.
Delete the existing EDQ WAR file and expanded directory of the same name in the Tomcat webapps directory.
Undeploy EDQ using the WebSphere Administration Console.
Follow the instructions in Section 5.3.1, "Creating the Necessary Shared Library" to create the ADF shared library necessary to EDQ.
Create two new configuration directories named oedq.home and oedq.local.home, because they are necessary to the EDQ 11g Release 1 (11.1.1.9).
Run the EDQ Configuration Application to configure the EDQ 11g Release 1 (11.1.1.9) product specifying the connections to your database and to the oedq.home and oedq.local.home configuration directories, see Section 5.3.2, "Configuring EDQ."
Copy the contents of your existing (pre-upgrade) EDQ config directory, that you previously noted, to the new oedq.local.home directory, with the exception of:
logs subdirectorydirector.properties fileTo link EDQ to your new configuration directories, use a new Java property named, edq.config.path that specifies the paths to the new directories that you created in Section 5.3.2, "Configuring EDQ" (for example, edq.home and edq.local.home.) This path should be separated by a colon on Linux and UNIX and a semi-colon on Windows.
Alternatively, you can link EDQ to the configuration directories using an environment variable by appending an environment variable named, EDQ_CONFIG_PATH, to your JAVA_OPTS environment variable as follows replacing Path to base EDQ config directory (EDQ Home) and Path to local EDQ config directory (EDQ Local Home) with the paths to the new directories that you created in Part , "Configuring EDQ":
| Operating System | Tomcat | WebSphere |
|---|---|---|
|
Linux and UNIX |
Set Java options for the EDQ server as follows: -Dedq.config.path=[Path to base EDQ config directory (EDQ Home)]:[Path to local EDQ config directory (EDQ Local Home)] -Doracle.mds.cache=simple |
Set Java options for the EDQ server as follows: -Dedq.config.path=[Path to base EDQ config directory (EDQ Home)]:[Path to local EDQ config directory (EDQ Local Home)] -Doracle.mds.cache=simple |
|
Windows |
Append Or Set Java options for the EDQ application service as follows: -Dedq.config.path=[Path to base EDQ config directory (EDQ Home)];[Path to local EDQ config directory (EDQ Local Home)] -Doracle.mds.cache=simple For more information about setting Java parameters, see the Apache Tomcat Documentation web site at |
Set Java options for the EDQ server as follows: -Dedq.config.path=[Path to base EDQ config directory (EDQ Home)];[Path to local EDQ config directory (EDQ Local Home)] -Doracle.mds.cache=simple For more information about setting generic JVM parameters, see the IBM WebSphere Documentation web site at
|
Deploy the ADF libraries using the steps in Section 2.2.5.2, "Configuring Tomcat" or Section 2.2.5.3, "Configuring WebSphere."
Deploy the edq.war file.
Copy the WAR file to the Tomcat webapps directory.
Deploy the EDQ application using the WebSphere Administration Console.
Start your EDQ Application Server.