|
|
The 9.2 WebLogic Upgrade Wizard allows you to upgrade domains created in:
The following sections describe how to use the WebLogic Upgrade Wizard for this purpose:
During a WebLogic domain upgrade, you specify the domain that you wish to upgrade and respond to a set of prompts. The WebLogic Upgrade Wizard performs the following tasks:
If a backup is requested, the wizard backs up the domain directory only, and it does not preserve file permissions. BEA 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 need to be protected by the user as they may contain confidential information. |
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 non-default value for the JAVA_OPTIONS environment variable in the original script, the specified value will not be preserved in the new script. |
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-92-logs directory in the domain, where server_name specifies the name of the server.
To review changes to the domain directory structure, see WebLogic Domain Directory Structure Enhancements.
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.
| 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 once the upgrade is successful. 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 WebLogic Server Environments at
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_wls/store.html#managing_jdbc_store_tables.
The wizard does not upgrade a JMS JDBC or file store if it detects that an upgrade has already been performed. If you need to perform multiple upgrades of a domain in which the same persistent stores are use (for example, in a test scenario), you must revert the data in the JMS store each time you repeat the upgrade process, as follows:
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. | Note: | When upgrading remote Managed Servers, the wizard does not persist the configuration information. |
Please note the following important notes about the upgrade process:
WebLogic Server applications do not need to be undeployed. 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 APIs that have been deprecated or removed are used in the application, then you may encounter warnings or exceptions at run time.
config.xml SerializedSystemIni.dat, DefaultAuthenticatorInit.ldift, DefaultAuthorizerInit.ldift, and DefaultRoleMapperInit.ldift If the security-related files are not available, the server fails to start and an authentication error message is logged.
.tlog) files that reside in the domain. For more information, see "Transaction Log Files" in Programming WebLogic JTA at
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jta/trxcon.html#tlog.WL_HOME\config directory must contain only one domain. If it contains more than one domain, the upgrade will fail..war, .jar) and an application.xml file is not defined for the domain, make sure that the pathname for the application does not include URL for the module. For example, if the path is specified as c:\bea\wlserver6.1\config\petstore\applications\tour.war, the tour.war filename must be removed before you start the upgrade. Otherwise, the upgrade process returns an error indicating that the path is invalid. If an error is encountered during the upgrade process and the application module is not deployed, the module is autodeployed as long as the server is running in development mode. Otherwise, you need to deploy the application module using the WebLogic administration tools.
.wlnotdelete directory is no longer used in the WebLogic Server environment.system, and you were required to specify a password only.WL_HOME\samples\server\config), you may notice a change in behavior when starting the Administration Server in the upgraded 9.2 domain. With 9.2, you are prompted for a username and password. With 7.0, the username and password are passed as a command-line argument to the startServer command, as follows: -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic
<Aug 1, 2005 6:42:06 PM EDT> <INFO> <Upgrade> <BEA-800000> <An invalid
path, 'C:\bea\weblogic81\user_projects\mydomain\medrecEar.ear', was
specified for application, 'medrecEar'.>
setDomainEnv.sh file to remove -Xverify:none from the start command by setting JAVA_OPTIONS="" after the following line:
The wizard supports the following upgrade modes:
| Note: | You can also use implicit mode to upgrade a WebLogic Server domain automatically when the Administration Server is started. For more information, see Upgrading a Domain at Administration Server Startup (Implicit Mode). |
You must upgrade the domains on every machine 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:
The following sections describe how to upgrade a WebLogic domain using the WebLogic Upgrade Wizard in graphical mode:
| Note: | The console from which you are running the Upgrade Wizard in graphical mode must support a Java-based GUI. If you attempt to start the Upgrade Wizard in graphical mode on a system that cannot support a graphical display, the invocation fails and an error message is displayed. |
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 BEA program group in the Windows Start Menu:
Start 
Programs BEA Products 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:
\common\bin\upgrade.cmd/common/bin/upgrade.sh
The log file will be available in the BEA_HOME/user_projects/upgrade_logs directory.
The following command can also be used to upgrade a WebLogic Server domain. This command cannot be used to upgrade a domain that contains resources for WebLogic Workshop, WebLogic Portal or WebLogic Integration.
java weblogic.upgrade [-type domain] [-out file]
Two arguments are optional: -type and -out. Include these arguments if you want to override the default values for the following:
-type option, a domain upgrade is performed. 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 at the end of the upgrade process.
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 at the end of the upgrade process.
After you run the command, the WebLogic Upgrade Wizard opens, as shown in the following figure.
The following table 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 depend on the combination of resources used in your domain. |
Select the WebLogic version of the domain that you are upgrading, as shown in the following example.
|
|||||
Select the directory that contains the WebLogic domain to be upgraded by navigating the local directory hierarchy, as shown in the following example.
|
|||||
Review progress of the wizard as it inspects the domain. Progress messages are displayed in the window, as shown in the following example.
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. The error message appears as follows.
If you receive this error message, upgrade the customer security providers, as described in Upgrading a Security Provider, and start the domain upgrade procedure again.
|
|||||
Select a server to function as the Administration Server in the new domain, as shown in the following example.
|
|||||
Enter the username and password (and password confirmation) for Node Manager authorization, as shown in the following example.
|
|||||
|
|||||
Review progress as the wizard processes the domain information and options provided. Progress messages are displayed in the window, as shown in the following example.
|
|||||
Review progress of the wizard as it prepares to back up the domain. Progress messages are displayed in the window, as shown in the following example.
|
|||||
|
|||||
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, as shown in the following example.
|
|||||
Review progress as the wizard restructures the domain directory. Progress messages are displayed in the window, as shown in the following example.
|
|||||
Review progress as the wizard upgrades the configuration settings. Progress messages are displayed in the window, as shown in the following example.
|
|||||
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, as shown in the following example.
|
|||||
|
|||||
Specify whether or not the deprecated RDBMSAuthenticator should be replaced by the SQLAuthenticator.
|
|||||
Review progress as the Wizard upgrades the domain with the security provider for WebLogic Personalization.
|
|||||
Review progress as the Wizard prepares to upgrade the database schema objects used by Personalization. You have the option to upgrade the database in a subsequent step.
|
|||||
|
|||||
|
|||||
|
|||||
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.
|
|||||
|
The Wizard does not back up the domain database. You will need to back up your domain database before beginning a domain upgrade.
|
|||||
The table displays the database categories and their associated datasources. The categories are used with their associated datasource to initialize the domain database. If a datasource appears as undefined, you can update the category with the correct datasource. If the datasource remains undefined, it will be skipped and not upgraded. In most of the cases, the association is correct and no further changes are required.
|
|||||
|
|||||
|
|||||
Review the results of the upgrade, including any important messages that require further consideration, as shown in the following example.
|
| Note: | Only WebLogic Server domains can be upgraded in the Silent mode. This mode is not supported when upgrading the WebLogic Portal, WebLogic Workshop or WebLogic Integration domains. |
In some circumstances, for example, when the domain resides on a remote machine, 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:
cd c:\bea\user_projects\domains\domain
where domain specifies the name of the domain.
java weblogic.Upgrade -mode silent -type domain [-responsesxmlfile] [-outfile]
The following arguments are optional: -responses and -out. Include these arguments if you want to override the default values for the following:
-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 Silent Upgrade XML Script Reference.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.
|