Classloading In Weblogic Server 7.0; Modifying Startup Scripts - BEA WebLogic Server 7 Upgrade Manual

2
Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0

Classloading in WebLogic Server 7.0

Earlier versions of WebLogic Server used the WebLogic classpath property
(
weblogic.class.path
later, the
the Java system classpath.
To include the classes that were formerly specified in
standard Java system classpath, set the
-classpath
java -classpath %CLASSPATH%;%MyOldClassspath% weblogic.Server
where
applications.

Modifying Startup Scripts

If you used WebLogic Server startup scripts with a previous version of the product,
modify them to work with 7.0.
Modify the startup scripts as described in
Administration Guide. The WebLogic classpath is no longer used; use the Java
system classpath as described in the preceding section,
WebLogic Server 7.0" on page
WebLogic Server 7.0 is started from the domain directory. Make sure that your
startup script starts the server from the domain directory.
With the new management system, there is a distinction between an
Administration Server and Managed Servers. Consequently, scripts that start
servers must be rewritten according to how you plan to administer your servers.
For the new commands and their required arguments, see
WebLogic Servers
2-8 BEA WebLogic Server 7.0 Upgrade Guide
) to facilitate dynamic classloading. In WebLogic 6.0 and
weblogic.class.path
option on the command line as in the following example:
%MyOldClasspath%
It is no longer necessary to include the license file in the classpath.
in the Administration Guide.
is no longer needed. You can now load classes from
CLASSPATH
contains only the directories that point to your old
Setting the Classpath
2-8.
weblogic.class.path
environment variable, or use the
in the
"Classloading in
Starting and Stopping
in the