Prerequisites for Upgrading a WebLogic Platform Domain

Plan and prepare for the upgrade, as described in Roadmap for Upgrading Your Application Environment
Undeploy WebLogic Platform applications (applications which contain components from Workshop, WLP, or WLI).

Note:

You must upgrade these applications before deploying them to the upgraded domain. For information about upgrading WLI, WLP, and Workshop applications, see the WLI Upgrade Guide, the WLP Upgrade Guide, and the Workshop Upgrade Guide, respectively.

Note:

You do not need to undeploy WLP-only applications; the Domain Upgrade Wizard undeploys them automatically. You must, however, upgrade the applications before deploying them to the upgraded domain.

Note:

You do not need to undeploy WebLogic Server (WLS) applications. In most cases, WLS applications will continue to run in the upgraded WLS 10.0 application environment. For information about changes that affect WLS applications in your environment, see WebLogic Server 10.0 Compatibility with Previous Releases.

Ensure that the domain directory contains, at a minimum, the following files:

Note:

This is required only if you are upgrading from a pre-9.x domain.

config.xml
Security-related files, including SerializedSystemIni.dat, DefaultAuthenticatorInit.ldift, DefaultAuthorizerInit.ldift, and DefaultRoleMapperInit.ldift

If the security-related files are not available, the server fails to start; an authentication error message is logged.

Transaction log (.tlog) files that reside in the domain

For more information, see Transaction Log Files.

Ensure that the console from which you are running the Domain Upgrade Wizard supports Java-based GUIs.
Review Important Notes About the Domain Upgrade Process.
Ensure that the JMS store is backed up.
If JMS JDBC stores are used, ensure that the corresponding database is running.

Note:

PointBase databases are automatically started and shut down by the Domain Upgrade Wizard.

Domain Upgrade Guide

Prerequisites for Upgrading a WebLogic Platform Domain