A Component Upgrade Process Reference

A.1.1 The Oracle Process Manager and Notification Server (OPMN) Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading the Oracle Process Manager and Notification Server:

1. Converts the <source_MT_OH>/opmn/conf/opmn.xml file to the 10g (9.0.4) format.

2. Merges the converted <source_MT_OH>/opmn/conf/opmn.xml file with the <destination_MT_OH>/opmn/conf/opmn.xml file. Inserts all custom nodes into <destination_MT_OH>/opmn/conf/opmn.xml except the node containing gid="dcm-daemon".

A.1.2 The Instance Configuration Data Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading instance configuration data:

1. Loads the <source_MT_OH>/config/iasschema.xml file from the source Oracle home.

2. Compares the <source_MT_OH>/config/iasschema.xml file with the <destination_MT_OH>/config/iasschema.xml file.

3. Writes any differences found in the source Oracle home file to the destination Oracle home file.

A.1.3 The Oracle Application Server Containers for J2EE (OC4J) Upgrade Process

The Oracle Application Server Containers for J2EE (OC4J) upgrade process consists of these steps:

1. The OracleAS Upgrade Assistant creates a separate process, which connects to the source Oracle home.

2. The process uses its Distributed Configuration Management version to examine the instances selected for upgrade.

3. Distributed Configuration Management creates a list of the instances in the source Oracle home in which the applications are deployed. It ignores Oracle-specific OC4J instances, such as OC4J_Portal, defined in the <source_MT_OH>/j2ee/deploy.ini* file. The instances are the OC4J upgrade candidates.

4. Distributed Configuration Management builds a list of EAR files for the applications listed.

5. The OracleAS Upgrade Assistant creates a backup of upgraded files, appending a preUpgrade suffix. If necessary, to create a unique file name, it appends an integer, for example, <file name>.preUpgrade.1.

6. The OracleAS Upgrade Assistant copies principals.xml, data-sources.xml, jazn-data.xml, and jazn.xml to the destination Oracle home.

7. Adds properties defined in the oc4j.properties file to the opmn.xml file, using the SMI API.

8. The OracleAS Upgrade Assistant rebuilds, and then redeploys the EAR files to the destination Oracle home. In this step, the OracleAS Upgrade Assistant searches for all orion-specific files in the application-deployments directory of the applications. It also searches for application-specific configuration files, such as principals.xml and jazn-data.xml.

9. Distributed Configuration Management updates mod_oc4j.conf with the mount points associated with each deployed application.

A.1.4 The Oracle HTTP Server Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle HTTP Server (OHS):

• Copies the httpd.conf file from the source Oracle home to the destination Oracle home, replacing the <source_MT_OH> path with <destination_MT_OH>, then applies 10g (9.0.4) file changes, and customizations made since Release 2 (9.0.2), to the corresponding file in the destination Oracle home.

• Searches the mod_oc4j.conf file in <source_MT_OH> for Oc4jMount directives and copies the Oc4jMount directives that contain the string ajp13://, cluster:// or instance:// to the mod_oc4j.conf file in <destination_MT_OH>.

• Copies the mod_osso.conf file from the source Oracle home to the destination Oracle home, replacing the source Oracle home path with the destination Oracle home path. The osso.conf file referenced by the OssoConfigFile directive will be copied and converted into 10g (9.0.4) obfuscated files.

• Copies the moddav.conf file from the source Oracle home to the destination Oracle home, replacing the source Oracle home path with the destination Oracle home path.

• Searches Include directives in the httpd.conf file recursively to locate user-defined configuration files; copies these files from the source Oracle home to the destination Oracle home. If the files were found in the source Oracle home, the OracleAS Upgrade Assistant replaces the source Oracle home path with the destination Oracle home path. If the files were found outside of the source Oracle home, the OracleAS Upgrade Assistant saves a copy of the original file with a .preUpgrade extension in the destination Oracle home, then replaces the source Oracle home file with the new file.

• Searches the LoadModule directives recursively to find related module dynamic libraries; copies the libraries from the source Oracle home to the destination Oracle home.

• Searches the SSLWallet directives recursively to find Oracle wallets; copies the wallets from the source Oracle home to the destination Oracle home.

• Locates CGI and fastcgi scripts by searching all configuration files for directories and files named in ScriptAlias or ScriptAliasMatch directives, and the ExecCGI option in Options directives (defined in Directory or File containers). Copies the directories and files from the source Oracle home to the destination Oracle home.

• Copies static document directories found in the (non-default) location specified by the DocumentRoot directive from the source Oracle home to the destination Oracle home. If the DocumentRoot directive is the default, static documents are not upgraded.

A.1.5 The Oracle Application Server Web Cache Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle Application Server Web Cache:

1. Locates webcache.xml and internal.xml in the source Oracle home.

2. Moves configuration data from <source_MT_OH>/webcache/ webcache.xml to <destination_MT_OH>/webcache/webcache.xml.

3. Copies error pages and wallet files from the source Oracle home to the destination Oracle home.

   
   

   Note: If you customized the directory location of the event log (specified by ACCESSLOG LOGDIR property in the webcache.xml file) in Oracle9iAS Release 2 (9.0.2), be aware that this customization will not be upgraded.

   
   

<LISTEN IPADDR="ANY" PORT="4445" PORTTYPE="NORM" SSLENABLED="SSLV3_V2H">
      <WALLET><destination_MT_OH>/webcache/wallets/subdir1</WALLET>
</LISTEN>
 <LISTEN IPADDR="ANY" PORT="4447" PORTTYPE="NORM" SSLENABLED="SSLV3_V2H">
        <WALLET>/some/other/path/wallets/default</WALLET>
 </LISTEN>
    ......
    ......
        <OSWALLET><destination_MT_OH>/webcache/wallets/default</OSWALLET>

A.1.6 The mod_plsql Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading mod_plsql:

1. Locates dads.conf and cache.conf in the source Oracle home.

2. Parses each source item, keeping results in memory.

3. Applies the parsing results to the destination Oracle home.

4. If necessary, uses the default value (<destination_MT_OH>/Apache/ modplsql/cache/) for the PlsqlCacheDirectory property in the cache.conf file.

5. Copies the oradav.conf file from the source Oracle home to the destination Oracle home.

A.1.7 The Oracle Enterprise Manager Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle Enterprise Manager:

1. Examines the <source_MT_OH>sysman/emd/targets.xml file for port entries related to the targets in the file.

2. Replaces the corresponding port entries in the <destination_MT_OH>sysman/emd/targets.xml file.

A.1.8 The Oracle Application Server Web Services UDDI Registry Upgrade Process

The Oracle Universal Installer and the OracleAS Upgrade Assistant perform these steps during installation of the Portal and Wireless installation type:

1. The OracleAS Upgrade Assistant extracts the <source_MT_OH>/ds/uddi/config/uddiserver.config file for later use.

2. The OracleAS Upgrade Assistant extracts properties from the <source_MT_OH>/ds/uddi/config/uddiserver.config file and applies them to the <destination_MT_OH>/uddi/config/uddiserver.config file.

A.1.9 The Oracle Ultra Search Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle Ultra Search:

1. Discover the data-sources.xml file in the source Oracle home.

2. Copy the data-sources.xml file from <source_MT_OH> to <destination_MT_OH>.

A.1.10 The OracleAS Portal Middle Tier Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading the OracleAS Portal middle tier:

1. Retrieves the source Oracle home Web Cache listener, administration and invalidation ports.

2. Applies these ports to the destination Oracle home.

3. Retrieves Oracle Enterprise Manager target data from the source Oracle home.

4. Applies these details to the destination Oracle home.

A.1.11 The Oracle Application Server Wireless Upgrade Process

The Oracle Application Server Wireless upgrade process consists of the steps below.

1. The Oracle Application Server Wireless Configuration Assistant upgrades the Oracle Application Server Wireless schema in the Oracle Application Server Metadata Repository during installation of the first Oracle Application Server Wireless middle tier. (See Section A.1.11.2, "Oracle Application Server Wireless Upgrade Items (List A)").

2. The OracleAS Upgrade Assistant copies runtime customization classes such as listener hooks and customized folder renderers from the source Oracle home to the destination Oracle home. (See Section A.1.11.2, "Oracle Application Server Wireless Upgrade Items (List A)").

3. The OracleAS Upgrade Assistant copies the process configuration information for the Oracle Application Server Wireless standalone processes from the Oracle Application Server Wireless Release 2 (9.0.2) middle tier to the Oracle Application Server Wireless 10g (9.0.4) middle tier, and configures the 10g (9.0.4) middle tier accordingly. (See Section A.1.11.3, "Oracle Application Server Wireless Upgrade Items (List B)").

   The configuration information for the Oracle Application Server Wireless Java processes is stored in the Oracle Application Server Wireless schema in the metadata repository. During upgrade from Release 2 (9.0.2) to 10g (9.0.4), the OracleAS Upgrade Assistant copies the process configuration information from the Release 2 (9.0.2) middle tier to the 10g (9.0.4) middle tier by creating additional entries in the Oracle Application Server Wireless schema. Because these processes are managed by Oracle Process Management and Notification in 10g (9.0.4), the Oracle Process Management and Notification configuration for the Oracle Application Server Wireless middle tier is also upgraded.

   
   

   Notes: Regarding upgrade of Oracle Application Server Wireless Java processes: In Release 2 (9.0.2), process information was node-specific. In 10g (9.0.4), it is Oracle home-specific. Thus, if you have multiple Release 2 (9.0.2) middle tiers on one node, you will notice that the upgrade process copies the information for all Release 2 (9.0.2) to the 10g (9.0.4) instance being upgraded, Instance names within a web site must be unique. During upgrade, the names of copied processes are made unique by appending a number to the name. In addition to the Release 2 (9.0.2) processes, the upgraded 10g (9.0.4) will contain new process types introduced in 10g (9.0.4). The process type "Alert Engine" has been renamed to "Notification Engine". The "Industrial Device Portal (Release 2 (9.0.2)) and "PIM Notification Dispatcher" (Oracle Collaboration Suite v. 1) processes are obsolete and therefore not upgraded.

   
   

A.1.12 The Oracle Application Server Forms Services Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle Application Server Forms Services:

1. Locates the files described in Oracle Application Server Forms Services Upgrade Items (List A, List B, and List C) below.

2. Makes a backup of the files described in Section A.1.12.1, "Oracle Application Server Forms Services Upgrade Items (List A)" with a preUpgrade suffix, and copies the files from the source Oracle home to the destination Oracle home without modification.

3. Copies the files described in Section A.1.12.2, "Oracle Application Server Forms Services Upgrade Items (List B)" with a 902 suffix, and copies the files from the source Oracle home to the destination Oracle home.

4. Makes a backup of the files described in Section A.1.12.3, "Oracle Application Server Forms Services Upgrade Items (List C)" with a preUpgrade suffix, and extracts customizations from the file in the source Oracle home and merges it into the file in the destination Oracle home.

A.1.13 The Oracle Application Server Discoverer Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle Application Server Discoverer:

• Merges the changes made to the Pref.txt and .reg_key.dc files in the Release 2 (9.0.2) instance to the equivalent files in the 10g (9.0.4) instance.

• Merges the changes made to the *.xml files in the Release 2 (9.0.2) instance to the equivalent files in the 10g (9.0.4) instance.

• Creates a backup copy of each configuration file, named as follows:

  <file name>_upgrade_backup.<file suffix>

A.1.14 The Oracle Application Server Reports Services Upgrade Process

The OracleAS Upgrade Assistant performs these steps when upgrading Oracle Application Server Reports Services:

• Copies all configuration files except jdbcpds.conf from the source Oracle home to the destination Oracle home.

• Copies all resource files from the source Oracle home to the destination Oracle home.

• Copies <source_MT_OH>/bin/reports.sh to the destination Oracle home, and adds the NLS_LANG environment variable, if it is not in the script.

• Copies reports server persistent files from the source Oracle home to the destination Oracle home.

A.2.1 The Identity Management Upgrade Process

The Identity Management components Oracle Application Server Single Sign-On and Oracle Internet Directory are upgraded by the Oracle Universal Installer. There are two possible configurations upgraded: distributed, in which Oracle Application Server Single Sign-On and Oracle Internet Directory reside on different computers, each with its own metadata repository, and non-distributed, in which they share a metadata repository on one computer.

The upgrade processing is interactive, and performed by the Oracle Universal Installer in each scenario. The Oracle Universal Installer is aware of the configuration being upgraded, and prompts for the necessary information and launches the appropriate configuration tools.

The source and destination configurations are depicted in:

• Figure 5-1, "Non-Distributed Identity Management in Release 2 (9.0.2) and 10g (9.0.4)"

• Figure 5-2, "Distributed Identity Management in Release 2 (9.0.2)"

• Figure 5-3, "Distributed Identity Management in 10g (9.0.4)"

A.2.2 The Metadata Repository Container Schema Upgrade Process

The Metadata Repository Container schema upgrade adds support for new schemas in the metadata repository, and updates the Oracle Internet Directory entry. The script performs one or both functions, depending on the credentials supplied when it is executed.

The Metadata Repository Container schema creation upgrade process (the mrc.pl script) performs these steps:

1. Checks to determine whether the ORACLE_HOME environment variable is set; if not, the process reports an error and exits.

2. Checks to determine whether the Oracle home is a Release 2 (9.0.2) Infrastructure; if it is not, the process reports an error and exits.

3. Connects to the metadata repository database; if unable to connect, the process exits.

4. Checks to determine whether the database version is 9.0.1.5; if not, the process reports an error and exits.

5. Creates these schemas: wcrsys, oca, oraoca_public, ip, wk_test and internet_appserver_registry (with the same password as the user name and corresponding tablespace) and these tablespaces: ias_meta, wcrsys_ts, ocats, ip_dt, ip_rt, ip_idx, ip_lob OLTS_SVRMGSTORE, oltsbattrstore. If the creation of any tablespace or user fails, the process reports an error and continues.

6. Writes message to standard output "Creation of new schemas successful" if all schemas were created successfully.

The Metadata Repository Container Oracle Internet Directory entry upgrade process (the mrc.pl script) performs these steps:

1. Checks to determine whether the ORACLE_HOME environment variable is set; if not, the process reports an error and exits.

2. Checks to determine whether the Oracle home is a Release 2 (9.0.2) Infrastructure; if it is not, the process reports an error and exits.

3. Connects to the metadata repository database using the following user names and passwords: oca/oca, oraoca_public, and wcrsys/wcrsys. (These should have been created by the mrc.pl schema creation process that preceded the Oracle Internet Directory entry update.) If unable to connect to all of these users, the process reports an error and exits.

4. Randomizes the password for the users.

5. Creates all required security entries in Oracle Internet Directory and new schema entry, using randomized password.

6. Changes the password of users in metadata repository.

7. Writes message to standard output "Update of new OID entries successful" if creation of OID entries and update of randomized passwords was successful.

A.2.3 The Process Connect Upgrade Process

The Process Connect upgrade process creates Process Connect schema.

A.2.4 The Oracle Application Server Certificate Authority Upgrade Process

The Oracle Application Server Certificate Authority schema upgrade process performs these steps:

• Creates OCA and ORAOCA_PUBLIC database users

• Tables and views

A.2.5 The Oracle Ultra Search Schema Upgrade Process

The Oracle Ultra Search schema upgrade process performs these steps:

• Copies the Oracle Ultra Search 10g (9.0.4) binaries to the Infrastructure database directories.

• Connects to repository database as SYS.

• Performs existence check for the WKSYS schema. Gets version number stored in the schema. If the version number is not 9.0.2 (or its patch release version), an error occurs and the process stops.

• Runs the SQL*Plus script wkdbmig.sql to upgrade the schema and data in WKSYS.

• Executes a loadjava command to load Java stored packages into the WKSYS schema.

• Runs the SQL*Plus script to create the demo schema and create an Ultra Search instance based on the demo schema.

• Updates the version number in the component registry.

• Configures the Oracle Ultra Search schema information stored in the Oracle Internet Directory.

A.2.6 The OracleAS Portal Schema Upgrade Process

The OracleAS Portal schema upgrade process (the upgrade.pl script) performs these steps:

1. Exports a subset of the Oracle9iAS Portal 9.0.2 tables to a dump file.

2. Applies an Oracle9iAS patch to the existing schema, if necessary.

3. Displays all invalid objects before the upgrade starts. (All Oracle9iAS Portal packages must be valid at this stage.)

4. Disables the DBMS jobs in the Oracle9iAS Portal schema. These will be re-enabled at the end of the upgrade.

5. Drops statistics gathered on all tables in the Oracle9iAS Portal schema. The statistics supported by the Oracle9iAS Portal will be gathered near the end of the upgrade.

6. Installs OWA packages, if necessary.

   
   

   Note: This step is executed only the current version of the OWA packages is not the latest expected version. This step causes invalidation of all packages in the instance that depend on the OWA packages. In particular, most Oracle9iAS Portal packages in all Oracle9iAS Portal schemas on the instance will become invalid. For this reason, after upgrade, you may need to recompile packages on other affected schemas after the upgrade. The upgrade script only recompiles packages in the Portal schema being upgraded.

   
   

7. Drops all existing Java objects from the Portal schema.

   
   

   Note: If there are any Java objects in the Portal schema that do not belong to Oracle9iAS Portal, you must reinstall them manually after the upgrade.

   
   

8. Deletes all product messages in all languages.

9. Loads all of the latest product messages in all languages that were previously installed.

   
   

   Note: If any product messages were altered before the upgrade, you must manually re-apply the changes.

   
   

10. Changes the schema and compiles all OracleAS Portal packages.

11. Exports temporary tables created during the upgrade.

12. Recompiles any invalid non-Oracle9iAS Portal objects. Warnings are issued if any invalid non-Oracle9iAS Portal objects remain after this step.

13. Updates the OracleAS Portal version if there are no fatal compilation errors.

14. Searches for errors and warnings in the upgrade log file and displays those encountered; if there were no errors, the process displays a success message.

A.2.7 The Oracle Application Server Syndication Server Schema Upgrade Process

The Oracle Application Server Syndication Server upgrade script ossupg902.sql performs these steps:

• Connects to the database as SYSDBA.

• Performs pre-upgrade validations (such as proper DSGATEWAY version) to determine whether the upgrade can proceed. If any of the checks fail, the upgrade stops.

• Destroys all schema contents, such as tables, PL/SQL packages, etc., in the DSGATEWAY schema.

• Invokes the 10g (9.0.4) installation script to install the 10g (9.0.4) database schema.

A.2.8 The Oracle Application Server Web Services UDDI Registry Schema Upgrade Process

The Oracle Application Server Web Services schema upgrade script wuru9023.sql (used for Oracle Application Server Release 2 (9.0.2) with the UDDI 9.0.2.3 patch) performs these steps:

• Connects to repository database.

• Performs pre-upgrade validations (such as proper UDDI version) to determine whether the upgrade can proceed. If any of the checks fail, the upgrade stops.

• Performs initial structural changes, such as creating and dropping tables, columns, and indexes.

• Performs upgrades to the UDDI server properties and configuration, inserting new rows and updating existing rows in the configuration tables.

The Oracle Application Server Web Services schema upgrade helper script wuru9020.sql (used for Oracle Application Server Release 2 (9.0.2)) performs these steps:

• Performs pre-upgrade validations (such as proper UDDI version) to determine whether the upgrade can proceed. If any of the checks fail, the upgrade stops.

• Destroys all schema contents, such as tables, PL/SQL packages, etc., in the UDDI database schema.

• Invokes the 9.0.4 installation script to install the 10g (9.0.4) database schema.

A.2.9 The Web Clipping Upgrade Process

Web Clipping is a new component, so there are no dependencies on other upgrade processes in the middle tier or Infrastructure. The upgrade process creates new tables and constraints, defines a package with functions and procedures, and seeds the tables with randomized data.

A.2.10 The Oracle Application Server Wireless Schema Upgrade Process

The Oracle Application Server Wireless schema in the Oracle9iAS Metadata Repository is automatically upgraded during installation of the first Oracle Application Server Wireless 10g (9.0.4) middle tier. You do not have to perform any additional upgrade steps on the Oracle9iAS Infrastructure. See Section A.1.11.1, "Upgrade of Oracle Application Server Wireless Middle Tiers and Wireless Schema" for details.