Skip navigation.
Downloads | Product Documentation | Support

Upgrade Guide

# Upgrading to Service Pack 2

This topic provides instructions for applying service pack changes to your portal applications after you install the service packs. For instructions on installing service packs, see Installing Service Packs and Rolling Patches in the WebLogic Platform documentation at:

>     http://e-docs.bea.com/platform/docs81/install/update.html.

Regardless of the release—GA or service pack—from which you are upgrading, you will follow the same basic process to complete the upgrade

- Step 1: Upgrade an Existing Domain or Create A New SP2 Domain
- Step 2: Upgrade Existing Applications and Projects
- Step 3: Redeploy the Upgraded Application

# Step 1: Upgrade an Existing Domain or Create A New SP2 Domain

You will need to 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 will depend on how you installed SP2. Table 5 -2 explains the options.

Table 5 -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 will need to manually update scripts in your domain. You must 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 that you need to updated: `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 only for the Out-of-the-Box domains. A domain created with the Configuration Wizard will not include these files.

If you use WebLogic Integration's Smart Update, it should take care of modifying environment variables when SP2 is installed in a different directory. If the SP2 upgrade installer is used, 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 do not get picked up automatically after running the SP2 upgrade installer since 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://edocs.bea.com/platform/docs81/confgwiz/newdom.html

1. 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. See Deploying Portal Applications for deployment instructions.

# 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. To update your application libraries:

1. Shut down your server if it is running. In WebLogic Workshop, choose Tools > WebLogic Server > Stop WebLogic Server.
2. In WebLogic Workshop, open the portal application you want to update.
3. In the Application window, right-click the application directory and choose Install > Update Portal Libraries.
4. If the service pack includes Commerce or Pipeline updates, right-click the application directory and choose Install > Commerce Services and Install > Pipeline Services.
5. 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.

6. If the service pack includes updates to 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.
7. 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 already deployed in production, redeploy those applications after you have updated them in WebLogic Workshop. See Step 3: Redeploy the Upgraded Application.

8. Restart your server.

# Step 3: Redeploy the Upgraded Application

The final upgrade step is to redeploy the application on your server. See Deploying Portal Applications at

>     http://edocs.bea.com/wlp/docs81/deploy/index.html

for deployment instructions.