8 Upgrading Standalone and Separately Installed Components

8.1 Upgrading a Standalone OC4J Instance

Upgrading a standalone OC4J instance (for example, an instance created with the OC4J that is available for download from Oracle Technology Network in zip format) is a manual process. The OracleAS Upgrade Assistant does not upgrade such instances. You must re-deploy the applications in the Oracle Application Server 10g Release 2 (10.1.2) Oracle home:

1. Create an OC4J instance to host the applications in the 10g Release 2 (10.1.2) Oracle home, using the Oracle Enterprise Manager 10g Application Server Control Console.

2. Configure the OC4J instance with any system properties or environment variables that are unique to the standalone instance.

3. Identify all command-line arguments from the java -jar command line in the standalone instance.

   In Oracle Application Server, the Oracle Process Manager and Notification Server (OPMN) subsystem is responsible for starting and stopping OC4J.

4. Move all command-line arguments to the following configuration file:

   DESTINATION_ORACLE_HOME/opmn/conf/opmn.xml
   
   

5. Move any properties specified in properties files in the standalone instance to the opmn.xml file.

6. Re-deploy the standalone applications (EAR files) in the Oracle Application Server 10g Release 2 (10.1.2) Oracle home.

7. You can use the Application Server Control Console to deploy the applications.

   
   

   See Also: "Introduction to Administration Tools" in the Oracle Application Server Administrator's Guide for information about using Application Server Control " Deploying a New OC4J Application" in the Enterprise Manager online help

   
   

8.2 Upgrading a Standalone OracleAS Web Cache Instance

To upgrade a standalone instance of OracleAS Web Cache Release 2 (9.0.2 or 9.0.3) to Oracle Application Server 10g (9.0.4), do not use the OracleAS Upgrade Assistant. Instead, use the procedure described in this section. (A standalone instance is one installed from a kit that included only this product; it was not installed as part of an Oracle Application Server installation.)

You use the OracleAS Web Cache Upgrade Tool (WebcacheMigtool), which performs the following functions to provide a way to audit the upgrade process:

• Creates a backup copy of the webcache.xml file from the source Oracle home. The backup file is named webcache.xml.preUpgrade.

  Note that if you run the Upgrade Tool more than once, your original settings will be lost. To prevent this, create another backup copy before you begin.

• Logs all upgrade activity in the file wxupgrade.log in the directory in which you run the Upgrade Tool.

To upgrade OracleAS Web Cache, take the following steps:

1. Stop the previous, standalone version of OracleAS Web Cache, using the webcachectl executable:

   ORACLE_HOME/bin/webcachectl stop
   
   

2. Stop the newly installed version, using the opmnctl command:

   opmnctl stopproc ias-component=WebCache
   
   

3. Set the ORACLE_HOME environment variable to the 10g Release 2 (10.1.2) Oracle home.

4. Run the following command. (Note that it is a single line.)

   $ORACLE_HOME/jdk/bin/java -classpath "lib/webcacheua.jar:lib/ua.jar:
       $ORACLE_HOME/lib/xmlparserv2.jar:$ORACLE_HOME/lib/dms.jar"
       oracle/ias/upgrade/config/webcache/WebcacheMigtool
       -s source_OH 
       -d destination_OH
   
   

   In this example, you must supply the following two arguments:

   • source_OH, which refers to the full path to the Release 2 (9.0.2) or (9.0.3) Oracle home.

   • destination_OH, which refers to the full path to the 10g Release 2 (10.1.2) Oracle home.

   The command provides optional arguments that allow you to upgrade from the same version or upgrade between different hosts. These arguments are necessary only when the source cache is part of a cache cluster. In that case, the configuration file contains entries for more than one cache and you must use one or more of these arguments to specify which cache is the source cache.

   • -o sourcefile_OH: Specifies the Oracle home for the particular cache in the source configuration file. Usually, this value is equal to <source_OH> specified by -s. However, to "upgrade" to the same version, such as when you want to migrate the configuration from a test cache to a production cache, you use this option.

     To migrate, you must copy the source configuration file and DTD files, and optionally the error files and wallet files, to a temporary directory. Then, you run the Upgrade Tool using the temporary directory as <source_OH>, and this option to specify the Oracle home value used in the source configuration file.

   • -h sourcefile_HOSTNAME: Specifies the HOSTNAME for the particular cache in the source configuration file. Usually, this value is equal to the localhost. However, if the source and the destination installations are on different hosts, you must use both the -o and -h options.

     To migrate to a different host, copy the source configuration file and DTD files and optionally the error files and wallet files, to a temporary directory on the destination host. Then, you execute the Upgrade Tool using the temporary directory as <source_OH>, and using the -o and -h options.

5. If the user under which the previous version of OracleAS Web Cache was installed is different than the user under which the current version of OracleAS Web Cache was installed, the upgraded OracleAS Web Cache will not start. The upgrade process modifies the webcache.xml, modifying the IDENTITY element to be the user from the previous version.

   You must edit the webcache.xml file to correct this. In the IDENTITY element, modify the USERID, and if necessary, the GROUPID, to reflect the user and group under which the current version of OracleAS Web Cache was installed.

6. Enable the webcached executable to run as the root user, if necessary. For example, if you configure OracleAS Web Cache to listen on a port less than 1024, such as on port 80, you must take this step. See Chapter 8 of the Oracle Application Server Web Cache Administrator's Guide for information.

7. Restart the upgraded OracleAS Web Cache, using the following command:

   opmnctl startproc ias-component=WebCache
   
   

   This command starts the admin server, cache server process, and, if enabled, the auto-restart process.

8.3 Upgrading Oracle Application Server InterConnect

This section explains how to upgrade Oracle9iAS InterConnect.

Since Oracle Application Server InterConnect is not distributed on the Oracle Application Server CD-ROM, and thus may not yet be installed, this section includes installation as a first step to upgrading. Installation instructions for each adapter are provided in the Oracle Application Server InterConnect documentation in the Oracle Application Server documentation library.

For the purposes of Oracle Application Server InterConnect, you can upgrade from Release 2 (9.0.2), 10g (9.0.4), or 10g Release 2 (10.1.2.0.0). Oracle Application Server InterConnect 10g Release 2 (10.1.2.0.2) provides several new features and improvements, such as the ability to manage InterConnect from the 10g Release 2 (10.1.2.0.2) Application Server Control Console.

The upgrade process consists of the following tasks:

• Installing and Upgrading Hub Components, Adapters, and Development Kit

• Upgrading Metadata

• Upgrading Management

• Upgrading the Oracle Workflow Schema in a Customer Database

http://www.oracle.com/technology/documentation/

CREATE TABLE emdcomments (emdid NUMBER(10)
                          CONSTRAINT fk_emdcomments_emdid REFERENCES 
                          emd(id) ON DELETE CASCADE
                          CONSTRAINT nn_emdcomments_emdid NOT NULL,
                          name VARCHAR2(4000)
                          CONSTRAINT nn_emdcomments_name NOT NULL,
                          comments LONG);
DROP TABLE ComponentInfoValue;
CREATE TABLE ComponentInfoValue (seqnum NUMBER
                                 CONSTRAINT fk_seqnum REFERENCES
                                 ComponentInfo(seqnum) ON DELETE CASCADE,
                                 value RAW(1024);

DROP TABLE ComponentInfoValue;
CREATE TABLE ComponentInfoValue (seqnum NUMBER
                                 CONSTRAINT fkseqnum REFERENCES
                                 ComponentInfo(seqnum) ON DELETE CASCADE,
                                 value RAW(1024);

DESTINATION_ORACLE_HOME/integration/interconnect/bin/ICManager

8.4 About Upgrading Oracle Application Server ProcessConnect

For 10g Release 2 (10.1.2), Oracle Application Server ProcessConnect is not being shipped and cannot be upgraded from 10g (9.0.4) to 10g Release 2 (10.1.2). In addition, you cannot migrate Oracle Application Server ProcessConnect 9.0.4 to Oracle Application Server Integration B2B 10.1.2.

8.5 Upgrading Schemas in a Customer Database

This section details the steps for upgrading OracleAS repositories that are stored outside of the OracleAS Metadata Repository.

• Upgrading the Oracle Business Intelligence Discoverer End User Layer Schema

• Upgrading the OracleAS Portal Repository in a Customer Database

• Upgrading the Oracle Workflow Schema in a Customer Database

• Upgrading a Standalone PL/SQL Web Toolkit Installations

http://portalcenter.oracle.com/upgrades