Upgrade Guide

Upgrading 8.1 to Service Pack 2

This section provides instructions for applying service pack changes to your portal applications after you install Service Pack 2. For instructions on installing service packs, see "Installing Service Packs and Rolling Patches" documentation at:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/update.html

You will follow this process to complete the upgrade

Note: Upgrading to Service Pack 2 does not require a database schema update.

Step 1: Upgrade an Existing Domain or Create a New SP2 Domain

You must do one of the following

Upgrade your existing domain to use the new SP2 libraries.
Create a new domain with the SP2 Configuration Wizard that mirrors your existing domain.

Upgrading an Existing Domain

If you choose to upgrade your existing domain to use the new SP2 libraries, upgrade instructions vary according to the method you used to install SP2. Table 4 -2 explains the options.

Table 4 -2 GA-to-SP2 Upgrade Options

If you used...

Then...

The upgrade installer to update your existing install

You do not need to make any changes to your SP2 domain. All scripts should pick up the appropriate libraries in /weblogic81.

The full installer and installed SP2 in a separate directory

You must manually update scripts in your domain. Update the following environment variables for all scripts in your domain:

BEA_HOME DOMAIN_HOME POINTBASE_HOME PORTAL_HOME JAVA_HOME JAVA_VENDOR JDK_HOME JDK_TOOLS WEBLOGIC_HOME WL_HOME

Below is a list of files in your domain to update:

create_db installService.cmd set-dbenv setDomainEnv setDomainEnvQS startManagedWebLogic startManagedWebLogicQS startPointBaseConsole startPointBaseConsoleQS startWebLogic startWebLogicQS stopManagedWebLogic stopManagedWebLogicQS stopWebLogic stopWebLogicQS uninstallService.cmd webappCompile webappCompileQS

Note: *QS scripts are for only the out-of-the-box domains. A domain created with the Configuration Wizard does not include these files.

If you use WebLogic Integration's Smart Update, it automatically modifies environment variables when SP2 is installed in a different directory. If you use the SP2 upgrade installer, you don't need to update any domain files, as these should already point to the new SP2 libraries.

You might need to update paths to point to the new JDK for SP2. These are:

JAVA_HOME JAVA_VENDOR JDK_HOME JDK_TOOLS

These paths are not picked up automatically after running the SP2 upgrade installer because they reside in a unique location.

Creating a New SP2 Domain

To create a new SP2 domain that mirrors your existing domain, use the Configuration Wizard. See "Creating a New WebLogic Domain" at: http://download.oracle.com/docs/cd/E13196_01/platform/docs81/confgwiz/newdom.html.

To apply the service pack library updates to portal applications already deployed in production, redeploy those applications after you have updated them in WebLogic Workshop. For deployment instructions, see "Preparing and Deploying the EAR File" at:

http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/prodOps/deployment.html.

Step 2: Upgrade Existing Applications and Projects

After you install a new service pack that includes portal library updates, you must update the libraries in the applications you have developed. Updating overwrites the existing libraries.

Before You Begin - About UUP

If you have developed your own Unified User Profile (UUP) to access user profile properties stored in an external user store, you have most likely modified and re-created the p13n_ejb.jar file in your application root directory. Because p13n_ejb.jar is one of the files overwritten in the following procedure, you should back up your existing file. After the upgrade procedure, you must re-create the updated p13n_ejb.jar with your UUP implementation. For more information, see "Setting up Unified User Profiles" in the User Management Guide at http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/users/uup.html#999527.

Update the Portal Libraries

To update your application libraries:

Shut down your server if it is running; in WebLogic Workshop, choose Tools—>WebLogic Server—>Stop WebLogic Server.

In WebLogic Workshop, open the portal application that you want to update.

In the Application window, right-click the application directory and choose Install—>Update Portal Libraries.

If your application uses Commerce or Pipeline components, right-click the application directory and choose Install—>Commerce Services and Install—>Pipeline Services.

After the portal application libraries are updated, a dialog box appears that lets you select Web projects in the application to update. Select the Web projects whose libraries you want to update, and click OK.

If you choose not to use the dialog box to update a Web project's libraries, you can update the Web project later by right-clicking the Web project directory in the Application window and choosing Install—>Update Portal Libraries.

If your application uses Commerce or Webflow JSP tag libraries, right-click the Web project directory in the Application window and choose Install—>Commerce Taglibs and Install—>Webflow Taglibs.

If you have hidden any Web applications in the WebLogic Workshop interface, those Web applications will not be updated. Either un-hide them and perform the update as described in the previous steps, or manually replace the updated libraries in the hidden Web application(s).

To apply the service pack library updates to portal applications that are already deployed in production, redeploy those applications after you have updated them in WebLogic Workshop. See Step 3: Redeploy the Upgraded Application.

If you developed your own Unified User Profile (UUP) by modifying p13n_ejb.jar in your application root directory, re-implement your UUP in the new p13n_ejb.jar file. See Before You Begin - About UUP.

Restart your server.

Step 3: Redeploy the Upgraded Application

The final upgrade step is to redeploy the application on your server. For deployment instructions, see "Deploying Portal Applications" at

http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/prodOps/deployment/index.html.