Skip navigation.
Downloads | Product Documentation | Support

Upgrade Planning Guide

# FAQ for Upgrading WebLogic Platform

This section provides answers to frequently asked questions (FAQ) about upgrading WebLogic Platform applications. Questions and answers are provided for the following product components:

- General SP6 Upgrade
- General SP5 Upgrade
- General SP4 Upgrade
- General SP3 Upgrade
- WebLogic Server
- WebLogic Workshop
- WebLogic Portal
- WebLogic Integration
- BEA JRockit

The questions and answers within this section apply to systems on which the latest service pack for WebLogic Platform 8.1 is installed. If you have not yet installed the latest service pack on your system, see Choosing an Upgrade Installation Method.

# General SP6 Upgrade

Q. Are there any database changes between SP5 and SP6?

A. Yes. Both WebLogic Integration and WebLogic Portal have updates to their respective databases. Both components provide upgrade scripts to implement these changes. See the following topics for more information:

- "Upgrading WebLogic Integration 8.1 SP4 and SP5 to WebLogic Integration 8.1 SP6" in the WebLogic Integration Upgrade Guide at the following URL:

http://e-docs.bea.com/wli/docs81/upgrade/upgradetosp6.html

- "Step 2: Upgrade Existing Database Schema" in "Upgrading to Service Pack 4" in the WebLogic Portal 8.1 Upgrade Guide at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack5to6.html

# General SP5 Upgrade

Q. Are there any database changes between SP4 and SP5?

A. Yes. Both WebLogic Integration and WebLogic Portal have updates to their respective databases. Both components provide upgrade scripts to implement these changes. See the following topics for more information:

- "Upgrading WebLogic Integration 8.1 SP3 or SP4 to WebLogic Integration 8.1 SP5" in the WebLogic Integration Upgrade Guide at the following URL:

http://e-docs.bea.com/wli/docs81/upgrade/roadmap.html

- "Step 2: Upgrade Existing Portal Framework Data" in "Upgrading to Service Pack 5" in the WebLogic Portal 8.1 Upgrade Guide at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack4to5.html

# General SP4 Upgrade

Q. Is there anything I need to do prior to installing SP4 on Red Hat Enterprise Linux 2.1 or 3.0 on Pentium?

A: If you are using JRockit, you need to make sure that you have the latest patches installed on your Linux operating system before you begin the upgrade process. For information, see the following topics:

- 8.1 Supported Configurations: Red Hat Enterprise Linux 3.0 AS, ES on x86 at the following URL:
  http://e-docs.bea.com/platform/suppconfigs/configs81/rhelinux30as_es_pentium/81sp4.html
- 8.1 Supported Configurations: Red Hat Enterprise Linux 2.1 AS, ES on x86 at the following URL:
  http://e-docs.bea.com/platform/suppconfigs/configs81/rhelinux21as_es_pentium/81sp4.html

Q. Are there any database schema changes between SP3 and SP4?

A. Yes. Both WebLogic Integration and WebLogic Portal have changes to their respective database schemas. Both components provide upgrade scripts to implement these changes. See the following topics for more information:

- "Upgrading WebLogic Integration 8.1 SP2 and SP3 to WebLogic Integration 8.1 SP4" in the WebLogic Integration Upgrade Guide at the following URL:

http://e-docs.bea.com/wli/docs81/upgrade/upgradetosp4.html

- "Step 2: Upgrade Existing Database Schema" in "Upgrading to Service Pack 4" in the WebLogic Portal 8.1 Upgrade Guide at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack3to4.html

# General SP3 Upgrade

Q. Are there any domain configuration template changes between SP2 and SP3?

A. Yes. There are changes in the default JDBC configuration settings in the following templates:

- Basic WebLogic Workshop Domain
- Basic WebLogic Integration Domain
- Basic WebLogic Portal Domain
- Basic WebLogic Platform Domain

For detailed information, see "JDBC Changes in Configuration Templates" in "What's New in SP3" at the following URL:

http://e-docs.bea.com/platform/docs81/interm/whatsnew.html

Q. Are there any database schema changes between SP2 and SP3?

A. Yes. Both WebLogic Integration and WebLogic Portal have changes to their respective database schemas. Both components provide upgrade scripts to implement these changes. See the following topics for more information:

- For WebLogic Integration, see "Upgrading Databases" in "Upgrading to WebLogic Integration 8.1 SP3" in the WebLogic Integration Release Notes for Version 8.1 SP3. This document is available in PDF format in a ZIP file. To obtain this document:

1. Locate the "Download PDF Documentation for Previous Releases of WebLogic Integration 8.1" page, available at http://e-docs.bea.com/wli/docs81/interm/prevreleases.html.
2. Click "All WebLogic Integration 8.1 SP3 Documents."

This downloads a ZIP file containing PDF files for all the WebLogic Integration 8.1 SP3 documentation. Open the file `relnotes.pdf`.

- For WebLogic Portal, see "Step 2: Upgrade Existing Database Schema" in "Upgrading to Service Pack 3" in the WebLogic Portal 8.1 Upgrade Guide at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack2to3.html

Q. Are there any limitations on upgrading from SP2 to SP3 on AIX?

A. Yes. Before you can upgrade your WebLogic Platform system from 8.1 SP2 to 8.1 SP3 on AIX, you must clean out any unused libraries manually. For instructions, see the Release Notes for WebLogic Platform 8.1 at the following URL:

http://e-docs.bea.com/platform/docs81/relnotes/relnotes.html#cr206782

# WebLogic Server

Q. What issues and tasks are commonly encountered during an upgrade to WebLogic Server 8.1?

A. For a summary of such issues and tasks, see "Common Upgrade Issues" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/quickupgrade.html.

Q. How do I upgrade WebLogic Server applications to 8.1 from a previous version?

A. The procedure varies, based on the version of WebLogic Server from which you are upgrading. The following table provides links to version-specific upgrade procedures.

Table 3-1 Upgrading WebLogic Server 8.1 from a Previous Version

If you are upgrading from... | See...
--- | ---
Version 7.0 | "Upgrading WebLogic Server 7.0 to Version 8.1" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade70to81.html
Version 6.x | "Upgrading WebLogic Server 6.x to Version 8.1" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade6xto81.html
Version 5.1 | "Upgrading WebLogic Server 5.1 to Version 8.1" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html

For more information about upgrading your applications to WebLogic Server 8.1, see:

- BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/index.html
- "FAQs: Upgrading" in BEA WebLogic Server Frequently Asked Questions at http://e-docs.bea.com/wls/docs81/faq/upgrade.html

Q. What changes have been made to the security features in WebLogic Server 8.1?

A. Changes to the set of available security features vary, based on the version of WebLogic Server from which you are upgrading. The following table provides references to version-specific security documentation.

Table 3-2 Changes to Security Features in WebLogic Server 8.1

If you are upgrading from... | See...
--- | ---
Version 7.0 | "Security" in "Additional Upgrade Procedures and Information" in "Upgrading WebLogic Server 7.0 to Version 8.1" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade70to81.html
Version 6.x | See "Upgrading WebLogic Server 6.x Security to Version 8.1" in "Upgrading WebLogic Server 6.x to Version 8.1" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade6xto81.html "Using Compatibility Security" in Managing WebLogic Security at http://e-docs.bea.com/wls/docs81/secmanage/security6.html
Version 5.1 | "Security" in "Additional Upgrade and Deployment Considerations" in "Upgrading WebLogic Server 5.1 to Version 8.1" in the BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html

# WebLogic Workshop

Q. How do I upgrade my Workshop applications to use one of the new Java 2 SDKs that are installed with the latest service pack?

A. You have a choice of two methods.

Note: To ensure that your Workshop applications have access to the latest updates and bug fixes for the basic Workshop domain, we recommend the second approach.

1. If you want to continue working in an existing Workshop domain—that is, a domain created with a pre-SP5 version of WebLogic Platform 8.1—update the definition of the `JAVA_HOME` environment variable in your domain's `setDomainEnv` script (`setDomainEnv.cmd` or `setDomainEnv.sh`) so it points to the root directory of the SDK installed with the current service pack. For example:

`set JAVA_HOME=C:\bea\jrockit81sp4_142_08`

2. You can create a new Workshop domain for your application using the Configuration Wizard, configuring all the resources required for your application as appropriate, such as JDBC connection pools, data sources, JMS queues, and so on.

After you have created the domain, complete the following steps:

1. Start Workshop and open your application.
2. Choose Tools—> Application Properties... to display the Application Properties dialog box.
3. Select WebLogic Server in the left pane, and modify the path for the Server Home Directory to specify the directory containing the `config.xml` file that was created in the new domain.

Q. Which feature changes in WebLogic Workshop 8.1 affect the upgrade process?

A. For a list of feature changes that affect the upgrade process, see "New Features in WebLogic Workshop" in "Upgrading Workshop Applications" in the WebLogic Workshop Help at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/migration/
conMigratingWorkshopApplications.html.

Q. How do I upgrade WebLogic Workshop applications to 8.1 from 7.0?

A. To upgrade your applications to WebLogic Workshop 8.1:

1. Make a backup copy of the full application.
2. Run the `jwsUpgrade` command to launch the following tasks:

- Back up the original files.
- Verify that each Web service (JWS) class definition ensures that the service implements the `com.bea.jws.WebService` interface.
- Verify that all static inner classes implement the `java.io.Serializable` interface.
- If there are any external XML map files, display the following: a warning that external XML map files are no longer supported, and a recommendation to incorporate the map information directly into the JWS file.
- If there are JAR files in the `WEB-INF/lib` directory for your project, consider moving them to the `APP-INF/lib` directory in your upgraded application.
- If there are `.java` files or Java classes in the `WEB-INF/classes` directory for your project, consider moving them to the `APP-INF/classes` directory in your upgraded application.

For more information about using the `jwsUpgrade` command, see "jwsUpgrade Command" in the WebLogic Workshop Help at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/reference/commands/cmdJwsUpgrade.html.

3. Create a new Workshop application and import your project files.
4. Import EJBs or deployable modules into the Modules folder.
5. Import local library JAR files into the Libraries folder.
6. Manually upgrade all control files.
7. Move inner classes into separate class files.
8. Incorporate external map files into JWS files.
9. Build the project.

For more detailed instructions on upgrading to WebLogic Workshop 8.1, see "Upgrading Workshop Applications" in the WebLogic Workshop Help at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/migration/conMigratingWorkshopApplications.html.

Q. How has the control model changed for WebLogic Workshop 8.1?

A. WebLogic Workshop 8.1 introduces a new, extensible model for controls. As in WebLogic Workshop 7.0, you can connect to enterprise resources using the built-in controls provided. In addition, with WebLogic Workshop 8.1, you can create your own reusable custom controls, making it easy to encapsulate business logic within your application.

When you create a control in WebLogic Workshop 8.1, the filename for your new control includes a JCX extension. The filename for a control created in WebLogic Workshop 7.0 includes a CTRL extension.

Q. What is the upgrade method for controls for WebLogic Workshop 8.1?

A. WebLogic Workshop 8.1 continues to support controls built using WebLogic Workshop 7.0. However, we recommend that you upgrade your existing controls to the new control model to take advantage of its greater flexibility.

Please note the following:

- Control files must be included in the package for a project. That is, a control file can no longer reside in the root directory for a project within your application; it must reside within a folder.
- A control file must extend the `com.bea.Control.ControlExtension` interface. You may need to modify the control file in Source View in WebLogic Workshop to extend the interface.
- If you upgrade your existing controls to the new model, you may need to manually edit some annotations in both the control file and the JWS file that calls it. For example:

- Some annotations within a control file begin with the `@jc` prefix, rather than `@jws`, which is supported for 7.0.
- The annotation used to designate a control variable is `@common:control`, rather than `@jws:control`, which is supported for 7.0.

The following table summarizes the differences between the annotation style used in version 7.0 and that used in version 8.1 of WebLogic Workshop.

Table 3-3 Differences Between Annotation Styles in WebLogic Workshop 7.0 and 8.1

Version 7.0 | Version 8.1
--- | ---
`@jws:av-identity` | `@jc:av-identity`
`@jws:av-service` | `@jc:av-service`
`@jws:connection` | `@jc:connection`
`@jws:ejb` | `@jc:ejb`
`@jws:jms` | `@jc:jms`
`@jws:jms-header` | `@jc:jms-header`
`@jws:jms-message` | `@jc:jms-message`
`@jws:jms-property` | `@jc:jms-property`
`@jws:sql` | `@jc:sql`
`@jws:timer` | `@jc:timer`
`@jws:control` | `@common:control`
`@jws:context` | `@common:context`
`@jws_message-buffer` | `@common:message-buffer`
`@jws:define` | `@common:define`
`@jws:operation` | `@common:operation`
`@jws:schema` | `@common:schema`
`@jws:target-namespace` | `@common:target-namespace`
`@jws:xmlns` | `@common:xmlns`

To find out more about specific annotation changes, open WebLogic Workshop, put the cursor on the annotation currently displayed in Source view, and press F1. Context-sensitive help for the designated annotation will be displayed.

For more information about upgrading databases, Web services, and JMS controls, see "Upgrade Controls" in "Migrating Your Existing Application" in "Upgrading Workshop Applications" in the WebLogic Workshop Help at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/migration/conMigratingWorkshopApplications.html#migrating.

# WebLogic Portal

Q. How do I upgrade WebLogic Portal applications to 8.1 SP5 from pre-SP5 releases of 8.1?

A. For complete details about upgrading your WebLogic Portal applications, see the following topics in the WebLogic Portal 8.1 Upgrade Guide:

- "Upgrading 8.1 to Service Pack 2" at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepacks.html

- "Upgrading to Service Pack 3" at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack2to3.html

- "Upgrading to Service Pack 4" at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack3to4.html

- "Upgrading to Service Pack 5" at the following URL:

http://e-docs.bea.com/wlp/docs81/upgrade/servicepack4to5.html

- ""Upgrading to Service Pack 6" at the following URL:
  http://e-docs.bea.com/wlp/docs81/upgrade/servicepack5to6.html

Q. How do I upgrade WebLogic Portal applications to 8.1 from 7.0 SP2?

A. Choose either of the following methods to upgrade your portal Web application created with WebLogic Portal from 7.0 SP2 to 8.1:

- Compatibility: Allows you to configure an existing portal Web application created with WebLogic Portal 7.0 SP2 to run on versions of WebLogic Portal 8.1 through SP2.
- Upgrade: Allows you to upgrade portal applications and resources created with WebLogic Portal 7.0 SP2 to 8.1.

For details, see the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/index.html.

Q. Which WebLogic Portal 7.0 SP2 features work in the new 8.1 framework?

A. Which features work in the 8.1 framework depends on which method you choose for your upgrade.

- Compatibility: Support for all WebLogic Portal 7.0 SP2 run-time features is provided except Payment Management in the Portal Administration Tools. In addition, several system-level security restrictions have been introduced. For details, see "Runtime and Administrative Issues" in "Version 8.1 Compatibility Domain" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter2.html.
- Upgrade: The WebLogic Portal platform now provides next-generation services, while maintaining backward compatibility where possible. With certain limitations, most core WebLogic Portal features are supported. The new platform introduces changes to the Look and Feel architecture, group portals, portal WebFlows, security, interaction management, and certain JSP tags and classes. For details, see "Overview of the Upgrade Process from WebLogic Portal 7.0 SP2 to 8.1" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter1.html.

Q. How do I use the Compatibility method to upgrade WebLogic Portal applications to 8.1 from 7.0 SP2?

A. WebLogic Portal 8.1 supports a Compatibility Domain to enable you to host upgraded WebLogic Portal 7.0 SP2 portal applications on versions of WebLogic Portal 8.1 through SP2. For more information about creating a Compatibility Domain and the steps required to upgrade an existing portal application to run in the domain, see "Version 8.1 Compatibility Domain" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter2.html.

Q. How do I use the Upgrade method to upgrade WebLogic Portal applications to 8.1 from 7.0 SP2?

A. To run a portal Web application developed on WebLogic Portal 7.0 SP2 in a WebLogic Portal 8.1 domain, perform the following steps:

1. Follow the instructions for hosting a portal application in the Compatibility Domain. For more information, see "Version 8.1 Compatibility Domain" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter2.html.
2. Follow the instructions for upgrading a portal application to run in an out-of-the-box WebLogic Portal 8.1 domain. For more information, see "Upgrading to WebLogic Portal 8.1" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter3.html.

Q. How do I upgrade portal and portal XML definitions from WebLogic Portal 7.0 SP2 to 8.1?

A. For instructions, see "Upgrading Database and Metadata Files from 7.0 to 8.1" in "Upgrading to WebLogic Portal 8.1" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter3.html.

See the following sections:

- Upgrade Application-Sync Files
- Upgrade Portal and Portlet Files

Q. How do I upgrade portlets created in WebLogic Portal 7.0 SP2 to 8.1?

A. Depending on the complexity of the portlet, you may decide to copy the portlet resources (content JSPs and backing files) into the new application and re-create the `.portlet` file. Review the following topics for information on upgrading JSP, WebFlow, and Web Service portlets:

- How do I upgrade a simple JSP portlet?

Drag the JSP file into a placeholder in a portal; the portlet is generated automatically. WebLogic Workshop identifies the JSP tags defined in the file that need to be replaced. For a summary of changes to the JSP tags, see "Framework Reference for Portal Upgrades from 7.0 to 8.1" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/appendix.html.

- How do I upgrade a WebFlow portlet?

Perform one of the following steps:

- Add WebFlow functionality to a WebLogic Portal 8.1 portal by right-clicking the name of the appropriate project and selecting Add WebFlow Jars.
- Recreate the WebFlow using page flows, replacing the Input Processors and Pipeline Components with controls.

- How do I upgrade a Web Service portlet?

For the 8.1 release, Web services are accessed using a Web Service control that you create using WebLogic Workshop. Once you create a page flow containing a control of this type, drag the `.jpf` file into a placeholder in a portal. Your Web service portlet will be created automatically.

Note: The Portlet Wizard no longer automates the creation of portlets that call Web services directly.

Q: How do I upgrade portal data from a WebLogic Portal 7.0 SP2 application to an 8.1 application?

A: For instructions, see "Upgrading Database and Metadata Files from 7.0 to 8.1" in "Upgrading to WebLogic Portal 8.1" in the WebLogic Portal 8.1 Upgrade Guide at http://e-docs.bea.com/wlp/docs81/upgrade/chapter3.html.

See the following sections:

- Upgrade PointBase Triggers
- Upgrade WebLogic Portal 7.0 Schema
- Upgrade ENTITLEMENT_RULESET Records
- Upgrade Existing Behavior Tracking Data

Q: How do I upgrade WebLogic Portal 7.0 SP2 skins to Look and Feels?

A: WebLogic Portal 7.0 SP2 skins and user interface (UI) components can be re-hosted to Look and Feels and the appropriate components in the 8.1 release. To find out how the presentation framework is used, and how you can create skins, layouts, and look and feels for use in the new framework, see "Creating Look & Feels" in the WebLogic Workshop Help at the following URL:

http://e-docs.bea.com/workshop/docs81/doc/en/portal/buildportals/ifLF.html

Q: How has anonymous user tracking changed?

A: When you create anonymous user profiles with WebLogic Portal 7.0 SP2, the data about an unregistered user that is collected during a single session is persisted only if the user registers. With WebLogic Portal 8.1, you can track unregistered users over multiple visits, which means you can present personalized content to anonymous users.

# WebLogic Integration

Q. How do I upgrade WebLogic Integration applications to 8.1 SP5 from an earlier release of 8.1?

A. Before you start upgrading your WebLogic Integration applications to SP5, make sure you have already upgraded them to SP4. For information, see "Upgrading from WebLogic Integration 8.1 SP2 and SP3 to WebLogic Integration 8.1 SP4" in the WebLogic Integration Upgrade Guide, available at the following URL:

http://e-docs.bea.com/wli/docs81/upgrade/upgradetosp4.html

Q. Which feature changes in WebLogic Integration 8.1 affect the upgrade process?

A. See the WebLogic Integration 8.1 Upgrade Guide at http://e-docs.bea.com/wli/docs81/upgrade/index.html.

Q. How do I upgrade WebLogic Integration applications to 8.1 from a previous version?

A. For information about upgrading your WebLogic Integration applications from pre-8.1 versions, see "Upgrading WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 to WebLogic Integration 8.1 SP2" in the WebLogic Integration Upgrade Guide, available at the following URL:

http://e-docs.bea.com/wli/docs81/upgrade/install.html

The Upgrade Utility for WebLogic Integration 8.1 is available on dev2dev at http://dev2dev.bea.com/resourcelibrary/utilitiestools/upgrade.jsp#wliupgrade.

# BEA JRockit

Q. Which feature changes in BEA JRockit 1.4.2 affect the upgrade process?

A. None.

Q. How do I upgrade BEA JRockit applications to 1.4.2 from a previous version?

A. There are no steps required to upgrade your BEA JRockit applications.

You should, however, make sure that you are using valid command-line options when starting JRockit. If you use an invalid option, JRockit exits. (In previous versions, invalid options were ignored.) For a list of valid command-line options, see "BEA JRockit 1.4.2 SDK Command Line Options by Name" at the following URL:

http://e-docs.bea.com/wljrockit/docs142/options.html.

Q. What are the advantages of migrating from a third-party JVM to JRockit?

A. BEA JRockit is a JVM designed for running server-side applications on Windows and Linux platforms that are running on Intel architectures. For server-side applications, JRockit has the following advantages over other Java virtual machines:

- JRockit employs adaptive optimization, a feature that detects and removes bottlenecks in a deployed application.
- JRockit is designed specifically to meet the special requirements of server-side applications, many of which are parallel and thread-intensive, run for longer than usual periods of time, and do not employ graphical interfaces.
- You can monitor JRockit using the WebLogic Server Administration Console.

For detailed information about migrating to BEA JRockit 1.4.2, see:

- "Migrating to BEA JRockit" in Developing Applications at http://e-docs.bea.com/wljrockit/docs142/devapp/migrate.html.
- "Upgrading Your JVM to JRockit" in "Additional Upgrade Procedures and Information" in "Upgrading WebLogic Server 7.0 to Version 8.1" in BEA WebLogic Server 8.1 Upgrade Guide at http://e-docs.bea.com/wls/docs81/upgrade/upgrade70to81.html.