Skip navigation.
Downloads | Product Documentation | Support

Upgrading WebLogic Application Environments

# Introduction

This document describes how to upgrade your application environment to WebLogic Server 9.1 from: WebLogic Server 6.1, 7.0, or 8.1.

Note: If you are upgrading from WebLogic Server 9.0 to WebLogic Server 9.1, see Roadmap for Upgrading WebLogic and AquaLogic Application Environments at `http://e-docs.bea.com/common/docs91/interm/upgrade.html`.

The following sections provide an overview of the topics discussed in this document:

- Overview of the Upgrade Process
- How the Upgrade Wizard Simplifies the Upgrade Process
- View a Demo: Upgrading an 8.1 WebLogic Application Environment to 9.1
- Interoperability and Compatibility with Previous Releases

#### Important Terminology

We recommend that, before proceeding, you familiarize yourself with the following terminology:

- Upgrade—To update BEA WebLogic Server from a previous release or service pack to a more recent one. This process may include updating an existing application or domain configuration to run in a more recent version of WebLogic Server.
- Migrate—To move an application or domain configuration from a third-party product to a BEA product.
- Interoperability—(1) The ability of an application deployed in one release or service pack to communicate with another application that is deployed in a different release or service pack. (2) The ability of WebLogic Server components to communicate with third-party software via standard protocols.
- Compatibility—The capability of an application built using one release or service pack to run in another release or service pack, regardless of whether the application was rebuilt.

# Overview of the Upgrade Process

The process required to upgrade an application environment depends on the scope of the application. An application environment includes a WebLogic domain and any applications and application data associated with the domain. It may also include external resources, such as firewalls, load balancers, and LDAP servers.

Figure 1-1 shows an example of a WebLogic application environment.

Figure 1-1 Example WebLogic Application Environment

The following table lists the components of the WebLogic application environment shown in Figure 1-1, and the upgrade requirements for each.

Table 1-1 Upgrade Requirements for Components in Example WebLogic Application Environment

Component | Description | Upgrade Requirements
--- | --- | ---
WebLogic domain | Includes the Administration Server (AS) and optionally one or more Managed Servers (for example, MS1, MS2, MS3, and MS4). The servers in a domain may span multiple machines. Furthermore, you can group Managed Servers into clusters to support load balancing and failover protection for critical applications. For more information about WebLogic domains, see "Understanding WebLogic Server Domains" in Understanding Domain Configuration at `http://e-docs.bea.com/wls/docs91/domain_config/understand_domains.html`. | Upgrade the domain directory on each machine in the domain.
Custom security provider | Supports custom security requirements. For information about developing custom security providers, see Developing Security Providers for WebLogic Server at `http://e-docs.bea.com/wls/docs91/dvspisec/index.html`. | Upgrade the custom security providers on each machine in the domain.
Node Manager | Provides high availability to Managed Servers. For more information about Node Manager, see "Using Node Manager to Control Servers" in Managing Server Startup and Shutdown at `http://e-docs.bea.com/wls/docs91/server_start/nodemgr.html`. | Upgrade custom Node Manager on each machine in the domain.
Applications | Any J2EE applications, including Web applications, EJBs, and so on. Typically, applications are deployed to one or more Managed Servers in a domain. Depending on the deployment strategy, applications may reside locally on a machine or be accessible via a shared directory. In addition, external client applications may access the application environment from outside a firewall. | Most WebLogic Server applications can be run without modifications in the new WebLogic Server 9.1 application environment. For more information, see Interoperability and Compatibility with Previous Releases.
External resources | Software components, such as databases for storing domain and application data, load balancers, and firewalls. | Verify that all external resources are compatible with WebLogic Server 9.1.

Each step in the upgrade process is described in more detail in this document.

# How the Upgrade Wizard Simplifies the Upgrade Process

The WebLogic Upgrade Wizard guides you through the steps required to upgrade a WebLogic domain that is compatible with WebLogic Server 6.1, 7.0, or 8.1 such that it runs in a WebLogic Server 9.1 application environment. As part of the upgrade process, you must upgrade any custom security providers and Node Managers used in the domain.

You can step through the upgrade process interactively, using the graphical user interface (GUI), or "silently," by creating an upgrade script and running it.

# View a Demo: Upgrading an 8.1 WebLogic Application Environment to 9.1

View an interactive demo, Upgrading an 8.1 WebLogic Application Environment to 9.1, that shows you how to upgrade a WebLogic Server application environment, built using WebLogic Server 8.1, so that it runs on WebLogic Server 9.1.

The 8.1 Avitek Medical Records sample application is used in this demo to illustrate the upgrade process. For more information about this sample application, see the Avitek Medical Records Development Tutorials at `http://e-docs.bea.com/wls/docs81/medrec_tutorials/index.html`.

# Interoperability and Compatibility with Previous Releases

Application environments that run with WebLogic Server 9.1 can interact with application environments built on WebLogic Server 7.0 or 8.1.

Most existing WebLogic Server applications can be run without modification in the new WebLogic Server 9.1 application environment. You should review the compatibility information described in Compatibility with Previous Releases to determine whether any feature changes affect the applications in your environment. If your application uses APIs that have been deprecated or removed, then you may encounter warnings or exceptions at run time.