This documentation is for WSO2 Message Broker 3.0.0. View documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Follow the steps given below.


Before you begin:

  • Make sure that the publishers to MB 2.2.0 are stopped before data migration starts.
  • Make sure that all the configuration files are updated in MB 3.0.0.
  • Data migration should only take place after all the users, roles, queues, topics etc. are created in MB 3.0.0.
  1. Both MB 2.2.0 and MB 3.0.0 should be started.


    Be sure to use a port offset for one of the two product installations using the carbon.xml file (stored in the <MB_HOME>/repository/conf folder).

  2. Start the JMS Client. The following events will be executed:
    • The JMS Subscriber will receive all the messages from the Queues and Topics in MB 2.2.0.
    • The JMS Publisher will publish the messages (that were received from MB 2.2.0) to MB 3.0.0.