|
|
This chapter provides information about the domain upgrade tool, when to run the tool, how to run it, and finally how to test the results after running the tool to verify that the upgrade to a maintenance pack (MP) has been successful.
Starting with Version 9.2 GA, shared J2EE libraries, known as library modules, are in use with WebLogic Integration (WLI), WebLogic Portal (WLP), and BEA Workshop for WebLogic Platform (WLW). Library modules are defined for inclusion in an enterprise or web application in a WebLogic Server config.xml.
The following is an example of a library module entry:
<library>
<name>p13n-app-lib#9.2.0@9.2.0</name>
<target>AdminServer</target>
<source-path>[root]/common/deployable-libraries/p13n-app-lib.ear
</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
The <name> element includes the following components:
<name of the application or web library>
The procedure for upgrading domains from WebLogic Portal 9.2 to the available maintenance packs (9.2 MP1 and 9.2MP2) is the same. However, for each maintenance pack, the implementation version will be modified to reflect the new version of the library module. Thus, the <name> entry in the <library> element in a newly created domain in 9.2 MP2 will be: <name>p13n-app-lib@9.2.0@9.2.2</name>.
The implementation version for WebLogic Portal 9.2 MP2 is 9.2.2, and the implementation version for WebLogic Portal 9.2 MP1 is 9.2.1.
The domain upgrade tool provided with a maintenance pack will take the config.xml file of a previous 9.2 GA or MP installation and update the implementation versions for all the appropriate library modules of WLP and WLI domains. For 9.2 GA WLP and WLI domains, the upgrade tool also adds the required base patch libraries as <library></library> elements in the config.xml file. However, base patches are deployed automatically in WLP and WLI domains for all maintenance packs.
After you have installed the latest maintenance pack of WebLogic Portal, WebLogic Integration, or BEA Workshop for WebLogic Platform, the existing config.xml files will be pointing to invalid library modules of the previous installations. You must run the domain upgrade tool to update the config.xml files to point to the new library modules.
The domain upgrade tool is a set of scripts located in: <weblogic_home>/common/bin.
One parameter is required for running the above scripts: a fully qualified path to the config.xml.
| Note: | It is recommended to either make a backup copy of the config.xml file. The reason for this is that the changes are applied to the existing config.xml. |
For example, to run the script for WLI, using a backup of the config.xml file in a temporary directory:
upgradeWLIConfigFile.cmd C:/tmp/config.xml
The script executes commEnv.cmd(on Windows) or commEnv.sh(on UNIX) in the <weblogic_home>/common/bin directory to set the environment for running the upgrade scripts.
The following message is displayed upon a successful upgrade of the config.xml file:
Your <config.xml_you_specified> file has been successfully upgraded.
For both WLI and WLP installations, this message will be displayed twice since the WLW library modules are upgraded first and then the appropriate WLI or WLP (or both) library modules are upgraded.
If you have patches applied on 9.2 GA, these entries are removed because the patches are rolled forward into the maintenance pack. Those patches and the entries in config.xml are not valid: the new library modules and library entries are effective after the upgrade.
| Note: | In a clustered environment, run the domain upgrade script only on the administrative service instance of the config.xml. |
After running the domain upgrade tool:
Take the upgraded config.xml file and copy it back into the domain's config directory (if a temporary location was used for the upgrade) and start the server via the startWebLogic.cmd or startWebLogic.sh.
Verify that no exceptions are thrown in the console and in the server log. Also verify, via WLS Console, that all application(s) are deployed and the implementation versions are correct for the maintenance pack you have installed.
Review the functional changes that are described in Functional Changes Affecting Your WebLogic Portal Environment. If any manual upgrade tasks are required for your particular environment, perform those tasks as instructed.
| Note: | WebLogic Portal 9.2 MP2 does not contain any functional changes. |
|