Migration notes

This section contains information that you might need to consider when migrating from one version or release of WebSphere MQ Everyplace to a higher version or release.

Migration information for the C codebase

For specific migration information for C codebase implemenations of WebSphere MQ Everyplace, refer to the migration information section of the WebSphere MQ Everyplace Application Programming Guide.

Migrating from version 1.2.7 to version 2.0

If you are upgrading to version 2.0 you must consider how the following changes affect your WebSphere MQ Everyplace application.

Changes to MQeFields

In order to comply with Java 2 Platform Micro Edition's (J2ME) Connected Limited Device Configuration(CLDC)/Mobile Information Device Protocol (MIDP) specification several methods have been modified or removed from MQeFields:

Peer channels

Peer channels have been removed from the WebSphere MQ Everyplace version 2.0 codebase, because they caused problems with message routing and assured delivery.

Changes to MQeChannel

The com.ibm.mqe.MQeChannel class has been moved and is now known as com.ibm.mqe.communications.MQeChannel. Any references to the old class name in administration messages is replaced automatically with the new class name.

MQeAttribute

The following changes have been implemented in relation to MQeAttribute:

MQeQueueManager

In version 1 code, the MQeFields structure passed to the MQeQueueManager allowed the specification of the following two aliases. They specified the default class names to use when loading attribute keys, where an attribute key class was not specified.

These values are hard-coded in the version 2.0 codebase, and cannot be changed using the alias mechanism. If the values are specified in .ini files, or calls to the MQeQueueManager, they are not used, but cause no problems.

Deprecated methods and classes

The following have been deprecated in version 2.0

A number of classes have been removed from the product. We reccomend that you update any applications written to make use of the classes listed below to use the equivalent function provided in WebSphere MQ Everyplace version 2.0. To enable existing applications to be run during this migration, WebSphere MQ Everyplace provides the MQeDeprecated.jar jar file.

The MQeDeprecated.jar file contains the following classes:

For more details on replacements for the above classes, refer to the the listing for each class in the WebSphere MQ Everyplace Java Programming Reference.

Security

The following changes have been made to security:

These changes have the following implications:

You must also refer to the migration section, if one exists, of each manual for more information on upgrading to WebSphere MQ Everyplace Version 2.0.

Migrating from version 1.2.6 or lower to release 2.0

If you are migrating from version 1.2.6 or lower to WebSphere MQ Everyplace version 2.0, consider the following product changes on your existing application.

Aliases

Several Java class aliases, which were commonly used in version 1.2.6 are defaulted in version 2.0. The WebSphere MQ Everyplace Java Programming Reference section on MQeAlias() methods provides more information on this.

Attribute keys

In WebSphere MQ Everyplace version 1 code, the MQeFields structure passed to the MQeQueueManager specifies the default class names to use when loading attribute keys, where an attribute key class was not specified:

(ascii)AttributeKey_2=com.ibm.mqe.attributes.MQeSharedKey
(ascii)AttributeKey_1=com.ibm.mqe.MQeKey

In version 2.0, you cannot change these values using the alias mechanism, because they are hardcoded. If you specify the values in .ini files, or calls to the MQeQueueManager, they are not used, but cause no problems.

MQBridge programming

In previous versions of WebSphere MQ Everyplace you had to instantiate an MQBridges object in order to connect to a WebSphere MQ system. In version 2.0, the bridge function is automatically available providing the relevant services are available on the class path. Chapter 9, "Interoperability with other messaging systems", of the WebSphere MQ Everyplace Application Programming Guideprovides more information on the bridge function.

Mini-certificate server

In previous versions of WebSphere MQ Everyplace the product code included a WLTS certificate issuance server, with application programming interfaces to allow programmatic control of the server. Version 2.0 replaces this with SupportPac, ESO3, "WebSphere MQ Everyplace WTLS Mini-Certificate Server", which you can download for free from the WebSphere MQ Web site at
http://www.ibm.com/software/mqseries/txppacs.

Registry

Improvements to the persistent data representation in the registry and the message store means changes in the format of the data. These changes mean that a registry generated under version 1 of WebSphere MQ Everyplace is not acceptable to a queue manager started using version 2.0 of WebSphere MQ Everyplace. The application generates an exception error to signal this fact. In Java this is com.ibm.mqe.MQeExceptionCodes.Except_QMgr_RegistryDataVersion. If you encounter this exception you will need to migrate the data in the registry. WebSphere MQ Everyplace provides classes to perform this migration. The required classes are in the package com.ibm.mqe.validation, and the only public class is com.ibm.mqe.validation.MQeDiskImageValidator. An example of how to use this class to perform migration is provided in examples.migration.Migrator.

Trace

The tracing mechanism for WebSphere MQ Everyplace Version 2.0 differs from the mechanism provided by version 1 of the product. These differences are detailed in the "Migration notes" section of the WebSphere MQ Everyplace System Programming Guide.

Migrating from version 1.2.4 and 1.2.5

If you are upgrading to version 2.0 from version 1.2.4, and you use home-server and store-and-forward queues, you should be aware of the following:

You need to make sure that any WebSphere MQ Everyplace systems with which your upgraded system needs to interact are upgraded to at least version 1.2.5.



© IBM Corporation 2002. All Rights Reserved