This documentation is for WSO2 Enterprise Integrator version 6.2.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc
Skip to end of metadata
Go to start of metadata

This page walks you through the process of upgrading to WSO2 Enterprise Integrator (WSO2 EI) 6.2.0 from WSO2 Message Broker (WSO2 MB) 3.1.0.

For information on what is new in this release and why you should upgrade, see About this Release.

If you are upgrading from a version older than WSO2 MB 3.1.0, you should first upgrade to WSO2 MB 3.1.0 and then upgrade to WSO2 EI 6.2.0.

  • See Default ports of WSO2 Products in the WSO2 Administration Guide, for more information on ports. The default ports in WSO2 EI are listed under Enterprise Integrator.
  • The distribution folder structure has changed from WSO2 MB 3.1.0 to WSO2 EI 6.2.0. The changes in the folder structure for directory locations are as follows:

    Message Broker 3.1.0Enterprise Integrator 6.2.0

See the following topics for instructions:

Be sure to stop the publishers that are connected to WSO2 MB 3.1.0 before commencing the migration process.

Upgrading the databases

See the following information about upgrading the Carbon database of WSO2 MB 3.1.0 to the Message Broker profile in WSO2 EI 6.2.0.

Upgrading the Carbon database

In WSO2 EI 6.2.0, you can use the same Carbon database that you used for MB 3.1.0. Therefore, you can simply restore the backup of the existing Carbon database to use with WSO2 EI 6.2.0.

Upgrading the broker-specifc database

The Message Broker profile of WSO2 EI comes with several changes to the broker-specific database, and therefore you must upgrade this database as explained below. We are providing a simple tool that you can easily download and run to carry out this upgrade. Follow the steps given below.

  1. Disconnect all the subscribers and publishers of WSO2 MB 3.1.0.
  2. Shut down the server.
  3. Run the migration script to update the database:
    1. Open a terminal and navigate to the <EI_HOME>/wso2/broker/dbscripts/mb-store/migration-3.1.0_to_3.2.0 directory, which contains scripts for each database type.
    2. Run the migration script relevant to your database type. For example, if you are using an Oracle, use the following script: oracle-mb.sql.
  4. Download and run the migration tool:
    1. Download the migration tool.
    2. Unzip the file. The directory structure of the unzipped folder is as follows:

      |-- lib <folder>
      |-- <file>
      |-- <file>
      |-- README.txt <file>
      |-- org.wso2.carbon.mb.migration.tool.jar

  5. 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 and copy it to the lib directory.
  6. Open the file from the folder structure shown above and update the database connection details shown below. 

    #Configurations for the database

    The parameters in the above file are as follows:

    • dburl: The URL for your broker-specific database. For example, jdbc:mysql://localhost/wso2_mb
    • driverclassname:The database driver class. For example, com.mysql.jdbc.Driver for MySQL.
    • dbuser: The user name for connecting to the database.
    • dbpassword: The password for connecting to the database.
  7. Run the migration tool:
    1. If you are on a Linux environment, open a command prompt and execute the following command:
    2. If you are on a non-Linux environment, execute the org.wso2.carbon.mb.migration.tool.jar manually.

The database is now upgraded with the changes relevant to the Message Broker profile of WSO2 EI 6.2.0.

Migrating the configurations

 Configurations should not be copied directly between servers.

Follow the steps below:

  1. Copy the database connector JAR files stored in the <MB_HOME>/repository/components/lib directory of WSO2 MB 3.1.0 to the <EI_HOME>/lib directory of WSO2 EI 6.2.0.
  2. Copy the keystores and truststores used in WSO2 MB 3.1.0 from the <MB_HOME>/repository/resources/security directory to the <EI_HOME>/wso2/broker/respository/resources/security directory in WSO2 EI 6.2.0.
  3. Update the configuration files.

    1. Update the configuration files with information of the migrated keystores and truststores. See Configuring Keystores in WSO2 products for more information.

    2. Go to the <EI_HOME>/wso2/broker/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file.

      Note that you need to update the datasourcedetails for the Carbon database as well as the broker-specific database in the master-datasources.xml file.

    3. Go to the <EI_HOME>/wso2/broker/conf directory and update the datasource references in the user-­mgt.xml and registry.xml files to match the updated configurations in the master­-datasources.xml file.
    4. Check for any further configurations that were done for WSO2 MB 3.1.0 based on your solution and update the following configuration files in the Message Broker profile of WSO2 EI 6.2.0 accordingly:

        • broker.xml

        • metrics.xml

        • metrics-properties.xml

        • messaging-event-broker.xml

  4. If you have secondary user stores created for WSO2 MB 3.1.0, you need to copy the 'userstore' folder in the <MB_HOME>/repository/deployment/server/ directory to the <EI_HOME>/wso2/broker/repository/deployment/server directory in the Message Broker profile of WSO2 EI 6.2.0.

  5. Check for any other configurations that were done for WSO2 MB 3.1.0 based on your solution and update the configurations in the Message Broker profile of WSO2 EI 6.2.0 accordingly. For example, configurations related to external user stores, caching, mounting, transports etc.

Migrating tenant artifacts

If multitenancy is used, copy the tenant artifacts from the <MB_HOME>/repository/tenants directory of WSO2 MB 3.1.0 to the <EI_HOME>/wso2/broker/repository/tenants directory of WSO2 EI 6.2.0.

Configuring the JMS client

To be able to connect the queues, topics and durable topic subscribers in EI-Broker, change the AMQP transport port of the JMS client as 5675.

Starting the server

Once you have completed the migration, you can start the WSO2 EI runtime. For details see Running the Product.

  • No labels