Additional Porting and Deployment Considerations
BEA WebLogic Server 7.0 Upgrade Guide
2-27
“Wireless Application Protocol Applications” on page 2-35
“Writable config.xml File” on page 2-35
“XML 7.0 Parser and Transformer” on page 2-36
“Deprecated APIs and Features” on page 2-36
“Removed APIs and Features” on page 2-37
Applications and Managed Servers
By default, applications are deployed to the Administration Server. However, in most
cases, this is not good practice. You should use the Administration Server only for
administrative purposes. Use the Administration Console to define new managed
servers and associate the applications with those servers. For more information, see
Using WebLogic Server Clusters
and
Overview of WebLogic System Administration
in the
Administration Guide
.
Deployment
By default, WebLogic Server version 7.0 uses the two-phase deployment model. For
more information on this deployment model and other 7.0 deployment features, see
WebLogic Server Deployment
in
Developing WebLogic Server Applications
.
Therefore, if you deploy a 4.5 or 5.1 application in your 7.0 server, the deployment
model is unspecified and, thus, uses a two-phase deployment. For more information,
see the
Release Notes
.
Plug-ins
The communication between the plug-in and WebLogic Server 4.5 and 5.1 is clear
text. The plug-ins in WebLogic Server 7.0 support SSL communication between the
plug-in and the back-end WebLogic Server.
To upgrade the plug-in, copy the new plug-in over the old one and restart the IIS,
Apache, or iPlanet web server.
