Upgrade Guide

Upgrading to Service Pack 3

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

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

This section contains information on the following subjects:

The Service Pack Upgrade Process

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

Upgrade an existing SP2 domain o create a new SP3 domain

Upgrade existing DB schema

Upgrade existing applications

Redeploy upgraded application to production environment.

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

You will need to do one of the following

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

Upgrading an Existing SP2 domain

If you choose to upgrade your existing SP2 domain to use the new SP3 libraries, upgrade instructions will depend on how you installed SP3. Table 6 -3 explains the options.

Table 6 -3 SP2-to-SP3 Upgrade Options

If you used...

Then...

The upgrade installer to update your existing SP2 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 SP3 in a separate directory

You will need to manually update scripts in their SP2 domain. You must update the following environment variables for all scripts in your SP2 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 SP2 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 SP3 is installed in a different directory. If the SP3 upgrade installer is used, you don't need to update any domain files, as these should already point to the new SP3 libraries.

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

JAVA_HOME JAVA_VENDOR JDK_HOME JDK_TOOLS

These paths do not get picked up automatically after running the SP3 upgrade installer since they reside in a unique location.

Creating a New SP3 Domain

To create a new SP3 domain that mirrors your existing SP2 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

Step 2: Upgrade Existing Database Schema

Note: WebLogic Server should be shut down while performing steps to upgrade the existing database schema

Complete the following steps to make your WebLogic Platform 8.1 SP2 database schema 8.1 SP3-compliant:

Backup your existing database

Optionally, you can review the changes that will be made during the upgrade.

To see the schema additions for the new CMV, refer to Content Management Virtual Database Objects at:

http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/db/4Schemas.html#1090619

To see the schema for the new WSRP feature, refer to Web Services for Remote Portlets Objects at:

http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/db/4Schemas.html#1090619

To see which schema objects will be altered, review 81sp3_alter_table.sql for the DBMS in which you are interested. You can find this file in the specific version folder for that DBMS under the folder <WebLogic-Home>\portal\db\<dbms>\<version>; for example:

C:\bea813\weblogic81\portal\db\pointbase\44

Change directories to ..\weblogic81\portal\upgrade\SP3

Note: The following step is special instructions for upgrading a PointBase database schema

If you are using a PointBase database, upgrade PointBase schema by doing the following:

Backup the 8.1GA/SP2 domain's workshop.dbn, workshop$1.wal, and pointbase.ini files.

Copy these files to bea\weblogic81\portal\upgrade\SP3 to run the upgrade_db_schema_to_81SP3 scripts for PointBase.

Copy those files to the 8.1 SP3 domain you created in step 1.

Warning: SP3 Database upgrade scripts for PointBase cannot expand _LABEL column lengths. BOOK_LABEL, PAGE_LABEL, and LOOK_FEEL_LABEL columns will be expanded from Varchar(40) to Varchar(80) when running SP3 database upgrade scripts for all databases other than PointBase. New PointBase databases created with SP3 will properly defined the columns as Varchar(80).

Note: The following step is special instructions for upgrading a Sybase database schema. If you use Sybase and do not make the required database parameter changes before running the upgrade scripts, they will fail and could cause upgrade difficulties.

If you are using a Sybase database, set the Allow Select into Bulkcopy database option to true for the WEBLOGIC Portal database; see Listing 6-1 for an example:

Listing 6-1 Setting Allow Select into Bulkcopy Option in Sybase

use master
go
sp_dboption WEBLOGIC,"select into/bulkcopy",true
go
use WEBLOGIC
go
checkpoint
go

Once Sybase database upgrade is complete, you can reset Allow Select into Bulkcopy to false for the WEBLOGIC Portal database, as shown in Listing 6-2.

Listing 6-2 Resetting Allow Select into Bulkcopy Option in Sybase

use master
go
sp_dboption WEBLOGIC,"select into/bulkcopy",false
go
use WEBLOGIC
go
checkpoint
go

Update db_settings.properties with your 8.1 database settings

For all databases, run the upgrade_db_schema_to_81SP3 cmd or .sh script to upgrade your database schema. To verify the upgrade was successful, look in the upgrade_db_schema_to_81SP3.log file. You can find the scripts and log file in <WebLogic_Home>\portal\upgrade\SP3.

The database is now upgraded to WebLogic Portal 8.1 SP3.

Remove OLD_ Tables After Upgrade (Optional)

During the upgrade to WebLogic Platform 8.1SP3, some tables are renamed with an old_ prefix so that the upgrades can be performed successfully and data migrated to the newly created tables. Once you've successfully upgraded to SP3, you can manually drop tables with the old_ prefix from you schema. After a successful 8.1SP3 upgrade you can remove the following tables:

OLD_WLCS_SECURITY
OLD_WLCS_SAVED_ITEM_LIST

Step 3: Upgrade Existing Applications

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

Note: Before you begin, ensure that WebLogic Workshop 8.1 SP3 is running. If it isn't, you need to start it.

If your server is running, shut it down by selecting, In WebLogic Workshop, Tools > WebLogic Server > Stop WebLogic Server.

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

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

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 update a Web project's libraries with the dialog box, 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 the service pack includes Commerce or Pipeline updates, right-click the application directory and choose Install > Commerce Services and Install > Pipeline Services.

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.

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 Deploying Portal Applications at http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/deploy/index.html
for deployment instructions.

Restart the server.

Step 4: Redeploy the Upgraded Application

The final upgrade step is to redeploy the application on your server.