Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs   |   Site Map   |   Search   |   Contact   |   Glossary   |   WebLogic Server Documentation
BEA WebLogic Server 6.0 Release Notes :   Previous topic   |   Next topic   |   Contents

The following sections contain information necessary to upgrade your system from WebLogic Server 5.1 to WebLogic Server 6.0:

• Upgrading WebLogic Server License Files

• Upgrading Your WebLogic Configuration

• WebLogic Server Tools

• JSP Error Handling

• JVM Upgrade Issues

• Platform Support Issues

• LDAP Security Realm

Upgrading WebLogic Server License Files

The Java format license file (WebLogicLicense.class) and the XML-format license file (WebLogicLicense.XML) are no longer supported. These files were used in conjunction with earlier releases of WebLogic Server and must be converted to a new format. The new license file is called license.bea. For instructions on how to convert your licenses to the new format, see Installing a WebLogic Server License.

Upgrading Your WebLogic Configuration

The following sections describe the changes required to upgrade your configuration to WebLogic Server 6.0.

webLogic.properties File Replaced

In earlier versions of WebLogic Server, configuration properties were stored in the weblogic.properties file. In WebLogic Server 6.0, configuration attributes for the server are stored in a persistent XML file, config.xml. Configuration attributes for applications are stored in .xml files specific to that particular application. Depending on your application you may have web.xml, weblogic.xml, or application.xml files associated with your application. The weblogic.properties file that handled configuration in earlier releases of WebLogic is not used in WebLogic Server 6.0.

Convert your existing weblogic.properties file to the appropriate .xml files using the Administration Console. Procedures for converting your weblogic.properties file are provided in the Console Help documentation.

• Do not edit the config.xml file directly. Access to the configuration is provided through the Administration Console, a command line utility, or programmatically through the configuration API. For details on configuring WebLogic Server, refer to the Administration Guide.

• Security properties are stored in the fileRealm.properties file.

• The weblogic.common.ConfigServicesDef API, which provided methods to get properties out of the weblogic.properties file, has been removed from this version.

• The weblogic.jsp.windows.caseSensitive property is a system property. Specify this in the command line, not in the weblogic.properties file. Make sure to set the following in your WebLogic Server start script: -Dweblogic.jsp.windows.caseSensitive=true

• The weblogic.httpd.compileJspEnabled property has been removed. In its place, you must add the following value to the JSPServlet in your weblogic.properties file: neverStale=true

WebLogic Classpath Property

Earlier versions of WebLogic Server used the WebLogic classpath property (weblogic.class.path) to facilitate dynamic class loading. In WebLogic 6.0, the weblogic.class.path is no longer needed. You can now load classes from the Java system classpath. To include the classes that formerly were specified in weblogic.class.path in the standard Java system classpath, use the -classpath option on the command line, or set the CLASSPATH environment variable.

Startup Scripts

If you used WebLogic Server startup scripts with a previous version of the product, modify them to work with 6.0.

• Modify the startup scripts as described in Setting the Classpath Option. The WebLogic classpath is no longer used; use the Java system classpath as described in the preceding section, WebLogic Classpath Property.

• 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 as well as Migrating from Earlier Versions of WebLogic Server.

JSP Error Handling

The behavior of the JSP include directive has changed between WebLogic Server 5.1 and the current version. In versions through WebLogic Server 5.1, the JSP include directive logged a Warning-level message if it included a non-existent page. In WebLogic Server 6.0 and later, it reports 500 Internal Server Error in that case.You can avert the error by placing an empty file at the referenced location.

BEA, mirroring Oracle's support policy, supports the Oracle releases called out in Installing and Using WebLogic jDriver for Oracle. BEA no longer supports the following Oracle client versions: 7.3.4, 8.0.4, 8.0.5, and 8.1.5.

If you want to use the Oracle Client Version 7.3.4, you can use the backward compatible oci816_7 shared library. As stated above, BEA no longer supports this configuration.

If you want to upgrade to Oracle Client Version 8.1.6, or read detailed documentation on the WebLogic jDriver and Oracle databases, see Installing and Using WebLogic jDriver for Oracle

For supported platforms, as well as DBMS and client libraries, see the BEA Platform Support Page. The most current certification information will always be posted on the Platform Support page.

The following table lists the WebLogic JMS configuration attributes that have been added since WebLogic Server 5.1.

For information on migrating an existing application, see Migrating WebLogic Server Applications

Component	JMS Attribute	Description
JMS Connection Factories	Message Maximum	Maximum number of messages that can exist for an asynchronous session and that have not yet been passed to the message listener. This attribute defaults to 10.
	Overrun Policy	Overrun policy for multicast sessions. When the number of outstanding messages reaches the Messages Maximum attribute value, messages are discarded based on the specified policy. If set to KeepNew, the most recent messages are given priority over the oldest messages, and the oldest messages are discarded, as needed. If set to KeepOld, the oldest messages are given priority over the most recent messages, and the most recent messages are discarded, as needed. This attribute defaults to KeepOld.
	Allow Close In OnMessage	Flag for specifying whether a connection factory creates message consumers that allow a close() method to be issued within its onMessage() method call. This attribute is disabled by default.
	Transaction Timeout	Timeout value (in milliseconds) for transacted sessions. This attribute defaults to 3600.
	User Transactions Enabled	Flag for specifying whether a connection factory creates sessions that are JTA aware. This attribute is disabled by default.
JMS Servers	JMS Default Connection Factories Enabled	Flag specifying whether the JMS default connection factories are instantiated on the JMS server. This attribute is enabled by default.
JMS Destinations	Enable Store	Flag specifying whether the destination uses the backing store specified by the JMS server. If this flag is enabled, but no backing store is defined, then the configuration fails and WebLogic JMS does not boot. If this flag is disabled, then the destination does not support persistent messages. If this flag is set to Default, then the destination uses the backing store if one is defined. This attribute defaults to Default.
	Multicast Address	IP address used for multicasting. This address is used to transmit messages to multicast consumers. This attribute has no default.
	Multicast TTL	Time-to-live value used for multicasting, specifying the number of routers that the message can traverse en route to the consumers. This attribute defaults to 0.
	Multicast Port	IP port used for multicasting. This port is used to transmit messages to multicast consumers. This attribute defaults to 6001.

.

Windows Convenience Programs Removed

The Windows convenience programs are no longer supported. The following programs have been removed:

• dbping.exe

• install.exe

• remove.exe

• wlconfig.exe

• wlconsole.exe

• wlserver.exe

WebLogic Server Tools

The following sections describe changes to WebLogic Server tools.

Console

The Java-based WebLogic Console and the Administration Servlets have been deprecated and replaced with the Administration Console. Refer to the Administration Guide for details on using the Administration Console.

Command-Line Interface

New command-line interfaces are provided with WebLogic 6.0. In addition, command line parameters have changed. The URL now refers to the Administration Server, and an additional servername parameter allows you to indicate the server on which a specific command is to run.

For more information, see Commands for Managing a WebLogic Domain.

The EJB Deployer tool is no longer provided. Deploy EJBeans in one of the following ways:

• Use the Administration Console to load EJBeans into WebLogic Server.

• Place the .jar file or .jar directory in the /config/examples/applications directory. The EJBeans automatically deploy when WebLogic Server starts.

For details on deploying EJBeans, see Programming WebLogic Enterprise JavaBeans .

Upgrading BEA Jolt

BEA Jolt is currently packaged with the BEA Tuxedo® product, and is not delivered with WebLogic Server 6.0.

If you currently use WebLogic Server 5.1 and BEA Jolt to connect to BEA Tuxedo applications, you will need to download the pre-GA version of BEA Jolt Release 8.0, which is compatible with the WebLogic Server 6.0 software. The pre-GA version of BEA Jolt Release 8.0 will allow you to maintain your WebLogic Server 5.1 feature functionality, and is available via the BEA Download Center.

ZAC is supported in WebLogic Server 6.0. If you wish to use ZAC, you must install Service Pack 1 or any subsequent Service Pack for WebLogic Server 6.0.

The following Java utility programs are no longer available:

• utils.eventsnoop

• utils.eventviewer

• utils.httptest

• util.itertest

WebLogic Tour

The WebLogic Tour is brand new. It uses a version of the J2EE PetStore Demo and is available from the Start menu.

JVM Upgrade Issues

To run WebLogic Server 6.0, you must upgrade to JDK 1.3. Only Java client applications can use JDK 1.2 and above. The latest information regarding certified JVMs is available at our Platform Support Page.

Platform Support Issues

WebLogic does rigorous testing on a variety of platforms. Only those platforms that pass our internal tests are certified. For the latest information on supported platforms, plug-ins, and database drivers see our Platform Support Page.

The LDAP security realm has been rewritten to provide improved performance and configurability. BEA recommends upgrading your LDAP security realm to take advantage of this functionality. The LDAP upgrade can be downloaded from http://commerce.bea.com/downloads/weblogic_server.jsp#wls under "Modules for WebLogic Server 6.0".

When upgrading to the new LDAP security realm, place the ldaprealm.properties file in the wlserver6.0 directory.