Deployment - BEA WebLogic Server 7 Upgrade Manual

1
Upgrading WebLogic Server 6.x to Version 7.0

Deployment

WebLogic Server 7.0 provides a new two-phase deployment model. For more
information on this deployment model and other 7.0 deployment features, see
WebLogic Server
6.x deployment model. Deployments initiated through the console or the new
weblogic.Deployer
WebLogic Server 7.0 will not deploy an application that has any errors in its
deployment descriptor. Previous versions of WebLogic Server would deploy an
application that had errors in its deployment descriptor. For example, if your 6.x
application was missing a reference description stanza in the deployment descriptor,
the application will not deploy in the 7.0 server until you add that stanza. A typical
stanza looks like:
<ejb-reference-description>
<ejb-ref-name>ejb/acc/Acc</ejb-ref-name>
<jndi-name>estore/account</jndi-name>
</ejb-reference-description>
Using WebLogic Server 7.0, you can no longer deploy through the console using the
6.x protocol. As a result, you must use the new deployment APIs. If your application
is previously deployed in 6.x and you're just starting your server, the applications will
get deployed with one-phase deployment. The
weblogic.refresh
weblogic.management.tools.WebAppComponentRefreshTool
7.0.
See
MBean attributes and operations.
The applications in the applications directory in development mode on the
Administration Server are now staged. In 6.x, they were not. For more information see
Application Staging
WebLogic Server Applications.
1-24 BEA WebLogic Server 7.0 Upgrade Guide
Deployment. By default, statically configured applications use the
command line utility use the new two-phase deployment model.
command line utilities and the
"Deprecated APIs and Features" on page 1-34
in the section called Two-PhaseDeployment in Developing
and
weblogic.deploy
are deprecated in
for information on deprecated