IBM Integration Bus and WebSphere Message Broker FAQ for Migration

Technote (FAQ)


Question

The following is a list of answers to frequently asked questions (FAQ) about Migration in IBM Integration Bus (IIB) and WebSphere Message Broker (WMB) for new and experienced users.

Answer

Index of questions in this document:



1. What are the supported migration paths for WMB/IIB ?


WMB/IIB provides migration paths from previous versions of the product. The following pages give information on migration:





2. Where can I find the detailed System requirements for WMB/IIB?

The detailed system requirements for WMB/IIB are located here:






3. Where can I find new features in different versions of WMB/IIB?


New features introduced in different versions of Broker can be found in the following pages:






4. What are the steps I must take for migration?


The migration steps are detailed in the WMB/IIB documentation links below:






5. How much disk space is required for WMB/IIB?


The memory and disk space requirements for different versions on different operating systems are listed here:






6. In what order should I migrate WMB/IIB components?


WMB/IIB has two components - Toolkit and Runtime. Migration of Runtime can be performed independent of Toolkit. In such a case, deployment using new features of the higher version might not work. For details on upgrading different components, please see the following links:






7. Will migrating Broker to a new version affect my applications ?


Before migrating Broker, please ensure that the newer version of WMB/IIB is tested/supported with your applications. The following system requirements pages list all the supported software.






8. How can I verify that my migration was successful?


A successful migration would require all the migration steps are completed successfully. Migration verification can be performed using the following instructions:


It is also recommended to check the broker logs (syslogs on UNIXes, Event viewer logs on Windows) for any errors.




9. Would migration require broker to be in a stopped state ?


Migrating to WMB V8/IIB V9 can be performed in a couple of ways:

  • Immediate or in-place migration would require broker to be in a stopped state prior to migration.
  • For parallel migration, the broker does not need to be stopped.

For more details please see the following links:





10. Will I see a performance gain with the new Broker version ?


Please check the performance reports for different versions of WMB to understand the performance characteristics of WMB :






11. How do I migrate publish/subscribe applications ?

Starting with WMB V7 the publish/subscribe engine is hosted in WMQ. This involves migration of publish/subscribe configuration (topics, subscriptions, ACLs and message flows). The detailed procedure is listed in the following links:





12. How will migration affect development projects such as message flow projects?

  

As a part of migrating the broker, you must migrate development source projects. Details are included in the following links:






13. Where can I find changes to message flow nodes in the new version of Broker?

In general, you can find changes made to nodes including the removal of a node in the following documentation links:





14. What is the end of support life cycle of the WMB/IIB version I'm migrating to?

Here is the link to life cycle dates listed by product:



  


15. Are there environment changes required to run broker successfully after the migration?

On Windows, when WMB/IIB command console is invoked, it sets the command environment for the user to execute any mqsi* commands.

On UNIXes, a sample profile "mqsiprofile" is provided under <WMB install>/bin/profiles directory that may be sourced in the user's environment to set up the command environment.

Any other environment variables required by the applications, such as user-defined nodes, application databases etc. will have to be exported in the broker environment after migration.

Please refer to the following links for details of setting up command environment:






16. Can I migrate from a stand-alone Broker to a multi-instance Broker?

It is not possible to migrate a stand alone broker at previous version to a multi-instance broker at the version you are migrating to.




17. What are my coexistence options for running different versions of WMB/IIB on the same machine?

Please refer to the following links to find out version co-existence:






18. Is it possible to use a different version of Toolkit and Broker runtime?

Toolkit and Broker Runtime can be at different versions. Note, new features that are introduced in a higher version of Broker will not work with a previous version of Toolkit and vice versa.




19. Where can I download the latest maintenance release?

WMB/IIB Fix Packs can be downloaded from the following link: http://www.ibm.com/support/docview.wss?&uid=swg27006041

The following FixCentral link contains some specific APAR fixes: http://www-933.ibm.com/support/fixcentral/





20. What ODBC configuration changes are required to connect to an application database during migration?

ODBC configuration changes are dependent on the Broker version. Please check the following links that describe the ODBC definitions that are required to be updated when migrating:


Checklist for WebSphere Message Broker ODBC setup on UNIXes: https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/checklist_websphere_message_broker_odbc_setup_on_unixes?lang=en


Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Message Broker Migration AIX, HP-UX, Linux, Solaris, Windows, z/OS 8.0, 7.0, 6.1, 6.0 All Editions

Product Alias/Synonym

WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Integration Bus
Migration

Software version:

9.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, z/OS

Reference #:

1649468

Modified date:

2014-06-12

Translate my page

Machine Translation

Content navigation