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.
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.
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.
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.The WebSphere MQ Everyplace Configuration Guide provides more information on the bridge function.
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(TM), 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.
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.
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 Appendix C. Differences between trace in WebSphere MQ Everyplace version 1.2.6 or lower and version 2.0