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

Migrating the Version 6.1 WebSphere Message Broker component

Migrate your Version 6.1 components and resources to WebSphere® Message Broker Version 8.0.

Before you start:

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.

  1. Back up your components and resources to ensure that you can return to your previous version if necessary. For more information and instructions, see the information center for your current product.
    Consider backing up the following resources:
    • The internal configuration repository that is maintained by the Configuration Manager.
    • The broker database.
    • Other critical databases that are accessed by your message flows.
    • All your development resources; for example, message flows and message sets.

      If you use a repository to manage these resources, check that the product you use provides sufficient features for you to recover your resources at a specific version.

  2. Migrate your WebSphere MQ installation to a supported version.
  3. Migrate the WebSphere Message Broker Toolkit by following the instructions in Migrating development resources to WebSphere Message Broker Toolkit Version 8.0.

    If the users of your toolkit operate in a team environment and share resources with each other, upgrade all users to Version 8.0 at the same time to ensure continued access to all resources. Because toolkit resources are stored in a different format when they are first saved in Version 8.0, your users might experience compatibility problems in some circumstances if some of their colleagues are using Version 8.0 and they are still working with a previous version.

  4. Migrate the broker by following the instructions in Performing in-place broker migration for a Version 6.1 broker.
  5. Optional: If you are migrating from a secure domain, you cannot directly migrate security settings for brokers. You must set up equivalent security by using the facilities that are provided by Version 8.0. To set up administration security for a broker, complete the following tasks.
    1. Enabling administration security
    2. Migrating Configuration Manager ACLs
  6. Optional: If you are migrating a broker that is configured on Microsoft Cluster Services, follow the instructions in Migrating a WebSphere Message Broker Version 6.1 broker that is configured on Microsoft Cluster Services (MSCS).
  7. Start the broker by using the mqsistart command.
  8. Review the technical changes that are introduced in Version 8.0; for more information, see Reviewing technical changes in WebSphere Message Broker Version 8.0.
When you have completed migration, consider the list of tasks in Perform post-migration tasks, and follow the guidance that is provided if these tasks apply to your environment.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:08


Task topicTask topic | Version 8.0.0.7 | bh23330_