See information about the latest product version
Migrating the Version 6.1 WebSphere Message Broker component
Migrate your Version 6.1 components and resources to WebSphere® Message Broker Version 8.0.
Read Preparing for migration.
You can migrate to WebSphere Message Broker Version 8.0 from the following products:
- WebSphere Message Broker Version 6.1
- WebSphere Message Broker with Rules and Formatter Extension Version 6.1
For full product version and release levels, see Supported migration paths.
For the latest details of all supported levels of hardware and software, visit the WebSphere Message Broker Requirements website.
The architecture of WebSphere Message Broker Version 8.0 is simplified:
- The broker has no requirement for a database. When you migrate
from WebSphere Message Broker Version
6.1, the following changes
apply:
- Because a database is no longer a mandatory requirement for a broker, DB2® and DB2 Runtime Client (the Derby database supported only on Windows systems) are not supplied when you purchase WebSphere Message Broker Version 8.0.
- The mqsicreatebroker and mqsichangebroker commands are updated to remove the specification of database parameters.
- The DatabaseInstanceMgr that was available
on Windows systems to manage Derby and DB2 databases is removed from Version
8.0. Commands that control
the DatabaseInstanceMgr and the Derby
database are removed:
- mqsicreatedb
- mqsideletedb
- mqsichangedbimgr
- The broker security model is implemented by using WebSphere MQ queues. The Configuration Manager component is removed and you cannot migrate existing components of this type. All operational data that is maintained by the Configuration Manager component is retrieved when you migrate your brokers.
- The commands that controlled the Configuration Manager component
are removed:
- mqsichangeconfigmgr
- mqsicreateconfigmgr
- mqsideleteconfigmgr
- mqsireportconfigmgr
- All topic-based publish/subscribe operations
are handled by WebSphere MQ. Because
access control for publishers and subscribers is managed by WebSphere MQ, the User
Name Server component is no longer required,
and is removed; you cannot migrate existing components of this type.
The following commands are no longer available:
- mqsichangeusernameserver
- mqsicreateusernameserver
- mqsideleteusernameserver
- In WebSphere Message Broker Version 8.0, publish/subscribe is controlled by WebSphere MQ. If your applications use publish/subscribe functions, and you have message flows that include one or more Publication nodes, you must migrate your subscriptions to WebSphere MQ after you migrate your queue manager but before you migrate your broker. Information about how to run the migmqbrk command to migrate the subscriptions and perform other tasks that might be required, is provided in Migrating publish/subscribe information to WebSphere MQ. After migration, you must use WebSphere MQ facilities to change subscriptions. A subscription related to the SYSTEM.BROKER.ADMIN.REPLY queue has to be removed manually.
If you are using cloned WebSphere Message Broker support in Version 6.1, you must change to use WebSphere MQ Clustering for Publish and Subscribe.
The instructions in this section apply to all operating systems that are supported by Version 6.1.
Complete the following migration tasks in the order that is shown to reduce the possibility of problems.