Upgrade Guide
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.
You must do one of the following
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.
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.
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.
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.
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.
To update your application libraries:
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
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.
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.
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.