Filter
Top Products
2 Upgrading WebLogic Server 4.5 and 5.1 to Version 7.0
2-8 BEA WebLogic Server 7.0 Upgrade Guide
Classloading in WebLogic Server 7.0
Earlier versions of WebLogic Server used the WebLogic classpath property
(
weblogic.class.path) to facilitate dynamic classloading. In WebLogic 6.0 and
later, the
weblogic.class.path is no longer needed. You can now load classes from
the Java system classpath.
To include the classes that were formerly specified in
weblogic.class.path in the
standard Java system classpath, set the
CLASSPATH environment variable, or use the
-classpath option on the command line as in the following example:
java -classpath %CLASSPATH%;%MyOldClassspath% weblogic.Server
where %MyOldClasspath% contains only the directories that point to your old
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 Setting the Classpath in the
Administration Guide. The WebLogic classpath is no longer used; use the Java
system classpath as described in the preceding section, “Classloading in
WebLogic Server 7.0” on page 2-8.
WebLogic Server 7.0 is started from the domain directory. Make sure that your
startup script starts the server from the domain directory.
It is no longer necessary to include the license file in the classpath.
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 Starting and Stopping
WebLogic Servers in the Administration Guide.