This documentation is for WSO2 Enterprise Integrator version 6.0.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.0.0 from WSO2 Message Broker (WSO2 MB) 3.1.0.

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

  • For information on the default ports in WSO2 EI runtimes, see Default ports of WSO2 EI.
  • The distribution folder structure has changed from WSO2 MB 3.1.0 to WSO2 EI 6.0.0. The changes in the folder structure for directory locations of the configuration related files are as follows:
Enterprise Service Bus 5.0.0Enterprise Integrator 6.0.0

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


Migrating the database

When upgrading to WSO2 EI 6.0.0, you can use the same database you used for WSO2 MB 3.1.0. Follow the steps below to configure WSO2 EI 6.0.0 database to connect to WSO2 MB 3.1.0 database:

  1. Copy database connector .jar files from <MB_HOME>/repository/components/lib to <EI_HOME>/lib directory. 
  2. Go to <DSS_HOME>/repository/conf/datasources directory and copy the master-datasources.xml file and  metrics-datasources.xml file to <EI_HOME>/conf/datasources directory. This will upgrade the database configuration in WSO2 EI 6.0.0.
  3. Go to the <EI_HOME>/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.

Migrating configuration files

Check for any configurations that were done for WSO2 MB 3.1.0 based on your solution and update the following configuration files in EI 6.0.0 accordingly:

    • broker.xml

    • metrics.xml

    • metrics-properties.xml

    • messaging-event-broker.xml

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