Page Comparison

...

• Make a backup of the databases used for MB 3.01.0.

• Also, copy the <MB_HOME_3.01.0> directory in order to backup the product configurations.

• Download WSO2 Message Broker 3.12.0 from http://wso2.com/products/message-broker/.

Anchor
step1 step1

Upgrading from MB 3.

...

1.0 to MB 3.

...

2.0

WSO2 MB 3.1.0 comes with several database changes compared to WSO2 MB 3.0.0 in terms of the data format used for storing. We are providing a simple tool that you can easily download and run to carry out this upgrade.

...

1. Disconnect all the subscribers and publishers for WSO2 MB 3.0.0.
2. Shut down the server.
3. Download and run the migration tool:
   
   1. Download the migration tool.

   2. Unzip the org.wso2.mb.migration.tool.zip file. The directory structure of the unzipped folder is as follows:

      Panel
      TOOL_HOME |-- lib <folder> |-- config.properties <file> |-- tool.sh <file> |-- README.txt <file> |-- org.wso2.carbon.mb.migration.tool.jar

   3. Download the relevant database connector and copy it to the lib directory in the above folder structure. For example, if you are upgrading your MySQL databases, you can download the MySQL connector JAR from http://dev.mysql.com/downloads/connector/j/5.1.html and copy it to the lib directory.
   4. Update the config.properties file with the database parameters for your MB database. You can find the current configurations for the MB database in the master-datasources.xml file that is stored in the <MB_HOME_300>/repository/conf/datasources directory.

   5. Run the migration tool:

      1. If you are on a Linux environment, open a command prompt and execute the following command: tool.sh.

      2. If you are on a non-Linux environment, execute org.wso2.carbon.mb.migration.tool.jar manually.
4. Start WSO2 MB 3.12.0.
5. Reconnect all the publishers and subscribers to MB 3.12.0.

Testing the upgrade

1. Verify that all the required scenarios are working as expected as shown below. This confirms that the upgrade is successful.

   1. Make sure that the server starts up fine without any errors.

   2. Verify that the Users and Roles are picked up:

   1. Navigate to Configure -> Accounts & Credentials -> Users and Roles

   2. Verify that the list of users and roles are shown correctly.

   3. View the permissions of a chosen role, and make sure that the permissions are correct.
2. Verify that all the messages to the Queues and Topics have been successfully published in the MB 3.12.0 instance.
3. Run some of the samples to see that the system is working fine.