Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle WebLogic Server
11g Release 1 (10.3.6)

Part Number E13754-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Upgrading a WebLogic Domain

You can use the 10.3.6 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server Version 8.1.

You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.0 to 10.3.6, but this is optional. This type of domain runs under WebLogic Server 10.3.6 without modification. See Appendix A, "Upgrading WebLogic Server 9.x or 10.x Application Environments to 10.3.6."

The following sections describe how to use the WebLogic Upgrade Wizard for this purpose:

What Happens During a WebLogic Domain Upgrade?

During a WebLogic domain upgrade, you specify the domain to upgrade and respond to a set of prompts. The WebLogic Upgrade Wizard performs the following tasks:

  1. Optionally, the wizard backs up the original domain directory.

    If a backup is requested, the wizard backs up the domain directory only, and it does not preserve file permissions. Oracle recommends that you back up the domain, any external applications, and application database resources in a separate process, as described in Step 3: Back Up the Application Environment.

    Note:

    Backup files created by the wizard must be protected by the user because they might contain confidential information.

  2. Recreates scripts, such as startup and shutdown scripts, and renames any original scripts as orig-scriptname.bak, where orig-scriptname specifies the original script name and extension.

    Note:

    The wizard does not copy any customizations in the original startup scripts to the new scripts. For example, if you specified a nondefault value for the JAVA_OPTIONS environment variable in the original script, the specified value is not preserved in the new script.

  3. Restructures the original domain, creating a new directory structure and moving domain components to new locations.

    During the restructuring, if a required directory already exists, the wizard simply keeps that directory and maintains the files and subdirectories that reside in it.

    Existing server log files are copied to the servers/server_name/logs/pre-9.0-logs directory in the domain, where server_name specifies the name of the server.

    To review changes to the domain directory structure, see Appendix C, "WebLogic Domain Directory Structure Enhancements."

  4. Upgrades the persisted configuration information stored in the configuration file (config.xml) to the config directory.

    If the wizard encounters duplicate resources when upgrading the configuration file (config.xml), a message is logged in the progress window. In this case, the last resource definition encountered is used during the conversion.

  5. Upgrades persisted data, such as JMS file stores, JMS JDBC stores, and transaction stores.

    Note:

    If JMS JDBC stores are used in the domain, see Step 6: Set Up the Environment.

    After the JMS JDBC stores are upgraded, the original JMS JDBC stores are not deleted. You should take this fact into account when performing capacity planning. You can delete the original JMS JDBC store tables after the upgrade is successfully complete. Original JMS JDBC store tables are named PrefixNameJMSSTORE and PrefixNameJMSSTATE, where PrefixName is the value of the Prefix Name attribute for the JMS JDBC store.

    If you do not want to upgrade persisted JMS messages, you can delete the JMS file store or JMS JDBC store tables before running the upgrade. When you do so, only JMS messages are lost; the configuration is not changed. For information about managing JDBC store tables, see "Managing JDBC Store Tables" in Configuring Server Environments for Oracle WebLogic Server.

    The wizard does not upgrade a JMS JDBC or file store if it detects that an upgrade has already been performed. If you must perform multiple upgrades of a domain in which the same persistent stores are use (for example, in a test scenario), revert the data in the JMS store each time you repeat the upgrade process, as follows:

    • For a JMS JDBC store, the upgrade process creates a new table named PrefixNameWLSTORE, where PrefixName is the value of the Prefix Name attribute for the JMS JDBC store. Before re-running the upgrade process on a domain that uses the JMS JDBC store is used, to drop this table.

    • If you must re-run the upgrade, make sure you first restore the backed up version of the JMS file store.

  6. Saves the configuration.

    Note:

    When upgrading remote Managed Servers, the wizard does not persist the configuration information.

  7. Reports any issues with the domain upgrade that require further consideration.

Important Notes About the Domain Upgrade Process

Please note the following important notes about the upgrade process:

Upgrading a Domain

The wizard supports the following upgrade modes:

You must upgrade the domains on every computer in the domain. For information about preparing remote Managed Server domain directories, see Step 5: Prepare the Remote Managed Server Domain Directories.

Note:

Before proceeding, make sure you have:

The following sections provide instructions for:

Upgrading a Domain in Graphical Mode

The following sections describe how to upgrade a WebLogic domain using the WebLogic Upgrade Wizard in graphical mode:

Starting the WebLogic Upgrade Wizard in Graphical Mode to Upgrade a Domain

To start the WebLogic Upgrade Wizard in graphical mode and upgrade a WebLogic domain on a Windows platform, choose the Domain Upgrade Wizard option from the Oracle program group in the Windows Start Menu by clicking Programs > Oracle WebLogic > WebLogic Server 11gR1 > Tools > Domain Upgrade Wizard.

Note:

You can only use this option if you do not have to customize the environment to specify JDBC driver classes, as described in step 3 of Step 6: Set Up the Environment.

To start the WebLogic Upgrade Wizard in graphical mode and upgrade a WebLogic domain from a Windows command prompt or on a UNIX platform:

  1. Verify that the WebLogic domain is not running.

  2. Backup the JMS Store, if applicable.

  3. Open a command prompt window (on Windows) or a command shell (on UNIX) and set up the environment as described in Step 6: Set Up the Environment.

  4. Execute the following script to upgrade your domains.

    • On Windows: WL_HOME\common\bin\upgrade.cmd

    • On Unix: WL_HOME/common/bin/upgrade.sh

    The log file is available in the MW_HOME/user_projects/upgrade_logs directory.

    The following command can also be used to upgrade a WebLogic domain.

    java weblogic.Upgrade [-type domain] [-out file]
    

    Two arguments are optional: -type and -out. Include these arguments to override the default values for the following:

    • The type of upgrade to be performed. If you do not specify a type with the -type option, a domain upgrade is performed.

    • The output file in which all standard output (stdout) and error messages are written. If you do not specify a file with the -out option, such messages are written to the command window, and a summary of messages is displayed when the upgrade process is complete.

    The -out argument is optional. It allows you to designate a file in which you want all standard output (stdout) and error messages to be written. By default, these messages are written to the command window and a summary of them is displayed when the upgrade process is complete.

    After you run the command, the WebLogic Upgrade Wizard opens, as shown in Figure 5-1.

    Figure 5-1 WebLogic Upgrade Wizard

    Description of Figure 5-1 follows
    Description of "Figure 5-1 WebLogic Upgrade Wizard"

  5. If JMS JDBC stores are used, ensure the corresponding database is running.

  6. Click Next to proceed to the next window.

Procedure for Upgrading a WebLogic Domain

Table 5-1 summarizes the steps in the procedure to upgrade a domain using the WebLogic Upgrade Wizard.

Note:

The screens provided in this section are only indicative of what you might see. The actual screens you see depend on the combination of resources used in your domain.

Table 5-1 Procedure for Upgrading a WebLogic Domain

In this step ... You ...

Select WebLogic Version

Select the WebLogic version of the domain that you are upgrading.

Click Next to proceed to the next window.

Select a Domain to Upgrade

Select the directory that contains the WebLogic domain to be upgraded by navigating the local directory hierarchy.

Click Next to proceed to the next window.

Inspect Domain

Review progress of the wizard as it inspects the domain. Progress messages are displayed in the window.

If you attempt to upgrade a domain in which custom security providers are used, without first upgrading those security providers, an error message is displayed and the wizard exits.

If you receive this error message, upgrade the custom security providers, as described in Chapter 3, "Upgrading a Security Provider," and start the domain upgrade procedure again.

After the inspection is complete (and if no error is encountered), the wizard advances to the next window automatically.

Select Administration Server

Select a server to function as the Administration Server in the new domain.

Note: If there is only one server defined in the domain, this window is skipped. This window is displayed only if the domain you are upgrading has multiple servers.

Click Next to proceed to the next window.

Enter Node Manager Credentials

Enter the username and password (and password confirmation) for Node Manager authorization.

For WebLogic Server 10.3.6, Node Manager requires user and password credentials to be specified for each domain. By default, the username and password are set to weblogic. If you do not use Node Manager, leave the default values unchanged.

Click Next to proceed to the next window.

Select Upgrade Options

  • Back up current domain (recommended) — If selected, the wizard backs up the original domain directory and stores it in a zip file. This option is selected by default.

    Note: The wizard backs up the domain directory only and does not preserve file permissions. Oracle recommends that you back up the domain and any external application and application database resources in a separate process, as described in Step 3: Back Up the Application Environment.

  • Add log files to backup zip — If selected, log files are included in the backup zip file. The number and size of log files can be large and you may want to disable this option to exclude them from the backup file. By default, log files are included in the backup file.

  • Do not set backward compatibility flags — As of WebLogic Server 9.0, some previously supported behavior has changed to comply with J2EE 1.4. By default, the wizard sets flags to enable the previous behavior in the new domain. If you select this option, these flags are not set for backward compatibility. For more information about the backward compatibility flags, see Backward Compatibility Flags.

Directory Selection Analysis and Optional Tasks

Review progress as the wizard processes the domain information and options provided. Progress messages are displayed in the window.

After processing is complete, the wizard advances automatically to the next window.

Domain Backup

Review progress of the wizard as it prepares to back up the domain. Progress messages are displayed in the window.

After processing is complete, the wizard advances automatically to the next window.

Select Directory for Domain Backup

Note: If you did not select Back up current domain upgrade option, as described in the "Select Upgrade Options" step, skip to the "Restructure Domain Directory" step.

In this window, set values for the following:

  • Backup directory — Navigate the local hierarchy and select the directory in which you want to save the backup zip file. By default, the original domain directory is used.

  • Backup filename — Enter the name of the backup file in the text box. The default filename is weblogic-domain-backup-domain.zip, where domain specifies the name of the domain.

Click Next to proceed to the next window.

Backup Domain

Review progress as the wizard backs-up the domain. A progress bar displays the percentage of the backup process that is complete, and progress messages are displayed in the window.

Note: Backup files created by the wizard must be protected by the user because they might contain confidential information.

When the backup process is complete, the wizard advances automatically to the next window.

Restructure Domain Directory

Review progress as the wizard restructures the domain directory. Progress messages are displayed in the window.

When the process is complete, the wizard automatically advances to the next window.

Upgrade Configuration Settings

Review progress as the wizard upgrades the configuration settings. Progress messages are displayed in the window.

The configuration information is not persisted until a later step.

After the configuration upgrade is complete, the wizard advances automatically to the next window.

Upgrade Persisted Messages and Transaction Log Formats

Review progress as the wizard upgrades the persisted messages (JMS file and JDBC stores) and transaction (JTA) logs that exist in the domain. A progress bar displays the percentage complete and progress messages are displayed in the window.

After the persisted message and transaction log upgrade process is complete, the wizard advances to the next window automatically.

Upgrade RDBMS Authenticator Security Provider

Specify whether the deprecated RDBMSAuthenticator should be replaced by the SQLAuthenticator.

Note: This window appears only when an RDBMSAuthenticator Security Provider exists in the domain you are upgrading.

Click Next to proceed to the next window.

Persist Upgraded Configuration

Review progress of the wizard as it saves the upgraded configuration and deletes any temporary files that were created during the upgrade process. Progress messages are displayed in the window.

Note: When upgrading remote Managed Servers, the wizard does not persist the configuration information.

After this process is complete, click Next to proceed to the next window.

Upgrade Complete

Review the results of the upgrade, including any important messages that require further consideration.

Click Done to close the WebLogic Upgrade Wizard.


Upgrading a Domain in Silent Mode

Note:

Only WebLogic domains can be upgraded in the Silent mode.

In some circumstances, for example, when the domain resides on a remote computer, it is not practical to use the WebLogic Upgrade Wizard in graphical mode. In such situations, you can use the wizard in silent mode to upgrade the WebLogic domain.

Note:

Before proceeding, make sure you have performed the prerequisite steps described in Prepare to Upgrade.

To start the WebLogic Upgrade Wizard in silent mode and upgrade a WebLogic domain:

  1. Verify that the WebLogic domain is not running.

  2. Open an MS-DOS command prompt window (on Windows) or a command shell (on UNIX) and set up the environment as described in Step 6: Set Up the Environment.

  3. (Optional) Create an XML script to define the upgrade requirements. For more information, see Appendix E, "Silent Upgrade XML Script Reference."

  4. Navigate to the directory that contains WebLogic domain to upgrade. For example:

    cd c:\bea\user_projects\domains\domain 
    

    where domain specifies the name of the domain.

  5. At a command prompt, enter the following command:

    java weblogic.Upgrade -mode silent -type domain [-responses xmlfile] [-out file]
    

    The following arguments are optional: -responses and -out. Include these arguments to override the default values for the following:

    • The location of an XML file that defines the upgrade requirements. If you do not specify a file with the -responses option, the wizard uses the default values during the upgrade process. For more information about the format of the XML file and the default values, see Appendix E, "Silent Upgrade XML Script Reference."

    • The output file in which all standard output (stdout) and error messages are written. If you do not specify a file with the -out argument, these messages are written to the command window.

Upgrading a Domain that Uses an Evaluation Database

As of WebLogic 10.3.3, the evaluation database that is available from the installation program is changed from PointBase to Apache Derby. The evaluation database is provided for use by the sample applications and code examples and may be used as a demonstration database. If you are upgrading an examples or demonstration domain that was originally based on PointBase, you have two choices:

The following sections explain how to implement each of these choices.

Using PointBase in an Upgraded Domain

To continue using PointBase as the database for a domain being upgraded to WebLogic 10.3.6, complete the following steps:

  1. When installing WebLogic Server 10.3.6, as described in Prepare to Upgrade, use the upgrade installer instead of the full installer. The upgrade installer preserves the PointBase installation from the previous WebLogic Server installation.

    Note:

    You must have an active My Oracle Support account to download the upgrade installer. For more information, see "Downloading an Upgrade Installer From My Oracle Support" in the Oracle WebLogic Server Installation Guide.

  2. Complete the steps described in Upgrade Your Application Environment, and Complete Post-Upgrade Procedure.

    The domain's configuration settings for PointBase are preserved.

  3. Obtain a PointBase license, available from http://www.pointbase.com.

If you use the full installer to install WebLogic Server 10.3.6, domains that use PointBase can be upgraded to WebLogic Server 10.3.6, but PointBase is unable to start from them. For a workaround:

  1. Restore your PointBase installation.

  2. Add the PointBase database JARs at the beginning of the CLASSPATH environment variable definition.

Migrating an Upgraded Domain Database to Derby

If you are upgrading an examples domain to WebLogic 10.3.6 and you want to migrate the domain database from PointBase to Derby, complete the following steps:

  1. Install WebLogic Server 10.3.6 using either the upgrade or full installer, as described in Prepare to Upgrade.

  2. Complete the steps described in Upgrade Your Application Environment, and Complete Post-Upgrade Procedure.

  3. Import the PointBase database schema and tables to Derby. The Apache Derby Web site has tips and resources that you might find useful, at http://db.apache.org/derby/integrate/index.html.

  4. Add the following Derby database JARs at the beginning of the CLASSPATH environment variable definition:

    • WL_HOME\common\derby\lib\derbynet.jar

    • WL_HOME\common\derby\lib\derbyclient.jar