WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Migrating Message Broker API applications
If you have applications that use the Message Broker API, check that they access the correct resources.
- If you are migrating from WebSphere® Message Broker Version
6.1, update your Message Broker API applications to use the file
that is supplied by WebSphere Message Broker Version 8.0. You cannot use the ConfigManagerProxy.jar file
from Version
6.1 to work with a Version
8.0 broker or to modify
message flow files.
You do not have to change the methods that the application uses; the Version 8.0 Message Broker API includes all deprecated classes and takes appropriate action.
- If you are migrating from Version 7.0, you can use the ConfigManagerProxy.jar file from Version 8.0 to connect to a Version 7.0 broker.
- You can also continue to use the ConfigManagerProxy.jar file from Version 7.0 to connect to a Version 8.0 broker.
- However, if you use the Version 8.0 file with your Version 7.0 application, you should recompile your application against the new file to take advantage of any deprecation warnings.
- For Message Broker API applications
that connect to a broker, update the connection details that are used
by your CMP applications to
connect to the appropriate broker.
If you are migrating from Version 6.1 and the application connects to a broker that is running on the same queue manager that was previously used by the Configuration Manager to which it connected, no change is required.