This section describes how to prepare for and perform an upgrade of your WebLogic application environments. Topics include:
Planning how you will upgrade an application environment is an important step in the process. To ensure that your plan addresses all of the aspects of upgrading that are necessary for your environment, complete the following steps:
Generate an inventory of the application environment, and identify the components defined in the following table. You can view a sample application environment in Overview of the Upgrade Process.
Verify support for all the hardware and software components in the application environment. The following table lists the key components for which you need to verify support.
"List of Supported Operating System Configurations" in Supported Configurations for BEA WebLogic Platform - Version 9.2 at
"Supported Database Configurations" in Supported Configurations for BEA WebLogic Platform - Version 9.2.
2. Before starting the pre-5.1 PointBase server, add the following information to the
The WebLogic Type 4 JDBC Driver for Oracle and the Oracle Thin Driver are installed with WebLogic Server and are ready for use. For more information about using these drivers, see "The Oracle Driver" in WebLogic Type 4 JDBC Drivers at
"Supported Web Servers, Browsers, and Firewalls" in Supported Configurations for BEA WebLogic Platform - Version 9.2.
Most existing WebLogic Server applications can be run without modification in the new WebLogic Server 9.2 application environment. However, you should review WebLogic Server 9.2 Compatibility with Previous Releases to determine whether any feature changes affect the applications in your environment.
WebLogic Workshop, WebLogic Portal and WebLogic Integration applications developed in 8.1 must be upgraded first before they can be run in WebLogic 9.2.
Using the information gathered in the preceding steps, create a plan for upgrading your application environment. Identify the scope and timing of the upgrade process, based on your business needs. Please note the following:
Before you upgrade the application environment, you must perform the following steps:
When upgrading your domain, undeploy all 8.1 WebLogic Portal, WebLogic Workshop and WebLogic Integration user applications before you start the upgrade. You will need to upgrade these applications using BEA Workshop for WebLogic before they can be deployed to an upgraded domain (or a new WebLogic 9.2 domain). For information on upgrading WebLogic Workshop application environments, see Upgrading from WebLogic Workshop 8.1. For information on upgrading Portal applications, see the WebLogic Portal Upgrade Guide and thechapter of the Portal Development Guide. For information on upgrading WebLogic Integration application environments, see WebLogic Integration Upgrade Guide.
WebLogic Server applications do not need to be undeployed before upgrading the domain. In most cases, WebLogic Server applications can be run without modifications in the new WebLogic Server 9.2 application environment. Review the compatibility information in WebLogic Server 9.2 Compatibility with Previous Releases to determine whether any features changes affect the applications in your environment. Note that if you use deprecated or removed APIs in the application, you might encounter warnings or exceptions at run time.
Before you upgrade, you must shut down all servers in the application environment.
You have the option of backing up the domain during the upgrade process, as described in Backup Domain. However, the wizard archives the domain directory only; it does not preserve file permissions.
BEA recommends that before upgrading your application environment, you manually back up the components defined in the following table. You should back up the relevant information on all machines in the domain.
Back up the Administration Server and any remote Managed Server domain directories that are defined in the application environment.
Back up any Node Manager directories and scripts that you are using to manage your servers in a clustered environment.
Before upgrading your application environment, you must install the 9.2 BEA Products that you require on each machine in the domain. For more information about installing BEA Products 9.2, see Installation Guide at
|Note:||If you are using Node Manager in your pre-9.2 installation, when installing the 9.2 product, you should set the Node Manager listen port to match the port number used in the pre-9.2 installation, if possible. The default value for the listen port for Node Manager is 5556.|
|Note:||When upgrading a domain, ensure that the corresponding 9.2 BEA product is installed. For example, to upgrade a WebLogic Workshop 8.1 domain to 9.2, you need BEA Workshop for WebLogic Platform installed.|
Some configurations include Managed Servers running on one or more machines that are remote from the Administration Server for the domain. If you have this type of configuration, you must upgrade the domain directories on each of the machines that host the remote Managed Servers.
To prepare the remote domain directories, you must copy the following files from the root directory of the pre-upgraded domain directory on the host machine for the Administration Server to the root directory of the host domain(s) of the remote Managed Servers:
|Note:||If the database in your configuration is not compatible with WebLogic Server 9.2, the data must be upgraded to a database that is supported before it can be used in the new application environment. For more information, see Step 4: Create an Upgrade Plan.|
To set up the environment for an upgrade:
CLASSPATHenvironment variable and
PATHenvironment variable, where
WL_HOMErefers to the top-level installation directory for WebLogic Server.
|Note:||When upgrading WebLogic Workshop, WebLogic Portal or WebLogic Integration domains, PointBase is automatically started and upgraded to PointBase v5.1.|
The following provides a roadmap that identifies the steps required to upgrade your application environment.
The following table summarizes the steps for updating an application environment. Some steps are mandatory, others are optional. Each step that is performed must be done on every machine in the domain.
If are using custom security providers in your current application environment and you wish to continue using them in the new environment, upgrade them:
If you are currently using a customized version of Node Manager to provide high availability to Managed Servers and you wish to continue doing so in the new application environment, upgrade Node Manager:
Upgrade the WebLogic domain on every machine that hosts any Managed Servers. Be sure to copy the appropriate files to the Managed Servers before performing the upgrade, as described in Step 5: Prepare the Remote Managed Server Domain Directories.
Once you have used the WebLogic Upgrade Wizard to upgrade the application environment, you may need to perform the following steps:
Not all of these steps are required for all situations. Review the sections to determine which, if any, of these steps are appropriate for your environment.
Due to recent changes in the MBean hierarchy, BEA does not guarantee that existing configuration and administration scripts (such as WLST,
weblogic.Admin, Ant, and so on) will run in all 9.2 environments. BEA recommends that you update your scripts to take advantage of the new features provided with WebLogic Server 9.2. For more information about new WebLogic Server features and changes in the MBean hierarchy, see "What's New in WebLogic Server 9.2" in the WebLogic Server and WebLogic Express Release Notes at
More information is provided in the following sections about scripting tools, custom configuration templates, and SNMP:
The following configuration and administration tools are deprecated as of WebLogic Server 9.0:
weblogic.Adminutility. For more information, see
If you are currently using one of these utilities, BEA recommends that you use the BEA WebLogic Scripting Tool, as described in the next section.
The WebLogic Scripting Tool (WLST) is a command-line scripting interface (built with Jython) that you can use to configure WebLogic domains. Using WLST, WebLogic Server administrators can perform administrative tasks and initiate WebLogic Server configuration changes interactively or by running an executable script.
With the release of WebLogic Platform 8.1, WLST was made available for evaluation from BEA's dev2dev site, but it was not formally included in the WebLogic Platform 8.1 product. It was offered in two formats: WLST online and WLST offline.
In WebLogic Server 9.2, the online and offline versions of WLST are delivered as a single tool. WLST fully supports the administrative and configuration features offered by 9.2. For more information about WLST, see WebLogic Scripting Tool at
|Note:||WLST online can be run on WebLogic Platform 7.0 and 8.1, and WebLogic Server 9.0, 9.1, and 9.2. WLST offline can be run on WebLogic Platform 8.1 SP5 and WebLogic Server 9.0, 9.1 and 9.2.|
As with the other pre-9.2 tools, BEA does not guarantee that existing WLST scripts will run in 9.2 due to recent changes in the MBean hierarchy. BEA recommends that you update your scripts to take advantage of the new features provided with WebLogic Server 9.2.
For more information about new WebLogic Server features and changes in the MBean hierarchy, see "What's New in WebLogic Server 9.2" in the WebLogic Server and WebLogic Express Release Notes at
The following table summarizes the steps required to upgrade custom configuration templates created with the WebLogic Platform 8.1 Template Builder.
Follow the steps described in Upgrade Your Application Environment.
See "What's New in WebLogic Server 9.2" in the WebLogic Server and WebLogic Express Release Notes at
If you use an SNMP manager to monitor WebLogic Server:
The MIB is located at
/weblogic92/server/lib/BEA-WEBLOGIC-MIB.asn1. WebLogic Server does not change object identifiers (OIDs) for existing managed objects; it only adds new OIDs for new managed objects.
For a list of deprecated managed objects, see "Deprecated MBeans" in WebLogic Server MBean Reference at
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/wlsmbeanref/core/index.html. The description of each deprecated MBean includes a pointer to the replacement MBean. (Each SNMP managed object corresponds to an MBean attribute.)
|Note:||A number of runtime MBeans that are internal to BEA have been removed from the MIB. These MBeans are not included in the deprecated MBeans list. For more information, see WebLogic Server Known and Resolved Issues at
To complete the upgrade of your application environment to 9.2, you may need to re-apply any customizations to startup scripts. The following sections describe how to customize the default startup scripts as well as any custom startup scripts.
The Upgrade Wizard does not carry forward any customizations that have been made to the default startup scripts, such as the setting of the
JAVA_OPTIONS environment variable. After the upgrade process is complete, you will need to customize the default scripts again.
If you are upgrading your domain to 9.2 and you want to continue using a pre-5.1 version of PointBase, you must add the JAR files for the pre-5.1 version of the PointBase database to the beginning of the
CLASSPATH environment variable definition. To do so, update the
CLASSPATH statement in your
|Note:||You can use the pre-5.1 version of PointBase only for WebLogic Server domains. For WebLogic Workshop, WebLogic Portal and WebLogic Integration domains that are configured to use PointBase, the PointBase database is automatically upgraded to PointBase v5.1.|
If you have created custom startup scripts, you will need to update them manually, as follows:
CLASSPATHvariable, as follows:
CLASSPATHenvironment variable definition.
|Note:||For WebLogic Workshop, WebLogic Portal and WebLogic Integration domains, the PointBase database is automatically upgraded to PointBase 5.1.|
Verify the file permissions, as follows:
If you upgrade Node Manager during the upgrade process, enroll the machine that is hosting the WebLogic domain with Node Manager. This can be accomplished using the
|Note:||This file is located in
|Note:||For more information, see "Configuring nodemanager.domains File" in "Additional Configuration Information" in Managing Server Startup and Shutdown at
nmEnroll command updates the
nodemanager.domains file under the
/common/nodemanager directory with information about the domain, where
WL_HOME refers to the top-level installation directory for WebLogic Server. The
nodemanager.domains file specifies the domains that a Node Manager instance controls. This file is necessary so that standalone clients do not need to specify the domain directory explicitly.
This command also downloads the following files from the Administration Server:
To enroll the machine with Node Manager using the
nmEnrollcommand to enroll the machine on which WLST is running with Node Manager.
SerializedSystemIni.datfile. By default, these files are saved in the directory in which WLST was started.
nodemanager.domainsfile, containing the information about the domain, is written to this directory. By default, the directory used for this purpose is
WL_HOMErefers to the top-level installation directory for WebLogic Server.
For example, if the domain directory is specified as
c:/bea/mydomain/common/nodemanager, and the default home directory for Node Manager,
/common/nodemanager, is used, then you enroll the machine on which WLST is running with Node Manager by entering the following command:
nmEnroll('c:/bea/mydomain/common/nodemanager')Enrolling this machine with the domain directory at
Successfully enrolled this machine with the domain directory at C:\bea\mydomain\common\nodemanager
For more information, see
nmEnroll in WebLogic Scripting Tool at
Once you start the Administration Server, verify the remote server start options, such as
CLASSPATH, reference the WebLogic Server 9.2 installation on the target managed server. This can be accomplished using the Administration Console, as described in "Configure startup arguments for Managed Servers" in Administration Console Online Help at
WARNING: If the remote server startup options are not set correctly, when attempting to start a Managed Server using Node Manager, messages similar to the following may be written to the log file. Because these messages may be sent recursively, they may eventually consume all space available on the drive.
No config.xml was found.
Would you like the server to create a default configuration and boot? (y/n):
java.io.IOException: The handle is invalid
at COM.jrockit.io.FileNativeIO.read(III)I(Native Method)
at COM.jrockit.io.NativeIO.read(Ljava.io.FileDescriptor;II)I(Unknown Source)
at COM.jrockit.io.NativeIOInputStream.read(II)I(Unknown Source)
at COM.jrockit.io.NativeIOInputStream.read(I[BI)I(Unknown Source)
at COM.jrockit.io.NativeIOInputStream.read([BII)I(Unknown Source)
at java.io.FileInputStream.read([BII)I(Unknown Source)
Execute standard procedures for quality assurance and performance tuning before promoting an application environment to production. You should test the execution of your applications (including external client applications) in your test application environment. If your applications use APIs that have been deprecated or removed, then you may encounter warnings or exceptions at run time. If you do, you can make any required modifications before promoting your applications to production.
Once all test criteria have been met, you can promote the application environment to production, as outlined in your upgrade plan (defined previously in Step 4: Create an Upgrade Plan).
Once the new 9.2 application environment is deployed into production, you can start redirecting requests to the new environment from the existing environment. Gradually, you can quiesce the existing environment. This might be accomplished using a load balancer, for example.
If any step in the upgrade process fails, the WebLogic Upgrade Wizard displays a message indicating the reason for the failure and terminates. To proceed, perform the following steps: