|
|
The following sections describe the procedures for upgrading application environments from WebLogic Server 9.0, 9.1, or 9.2 to the WebLogic Server 10.0 release:
| Note: | BEA does not recommend upgrading an application environment that is currently deployed in production. Instead, you should upgrade your application environment while it is under development or test and execute standard procedures for quality assurance and performance tuning before promoting the upgraded environment to production. |
This option is useful if the process of creating and customizing a domain has been automated. The steps to create a new domain are as follows:
This step can be accomplished using the Configuration Wizard or using automated scripts, built using WebLogic scripting tools such as WLST.
You may need to update your automated scripts, for example, to reference the 10.0 domain template and/or to implement new features provided in the 10.0 release.
For example, starting in WebLogic 9.1, the default security providers are XACML-based, as described in
Security for BEA WebLogic Server 10.0. You may choose to add support for the security providers prior to WebLogic 9.1 or make the appropriate changes to use the new XACML-based security providers.
| Note: | If you used a custom 9.x template in step 2, the 9.x applications may already be deployed. |
Updating an existing domain is useful for maintaining customizations within your test domain if generation of the domain has not been automated. There are two options for upgrading an existing domain, as follows:
BEA_HOME, BEA_JAVA_HOME, JAVA_HOME, and WL_HOME to the appropriate values. CLASSPATH to remove path information that is no longer required, such as patch file information that applies to a pre-10.0 release.
If you developed Beehive applications in 9.0, 9.1 or 9.2, you must upgrade the applications as described in Upgrade Paths in Beehive Integration in WebLogic Server 10.0.
|