This documentation is for WSO2 Enterprise Integrator version 6.1.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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

This page walks you through the process of upgrading to WSO2 Enterprise Integrator (WSO2 EI) 6.1.0 from WSO2 Enterprise Service Bus (WSO2 ESB) 5.0.0.

If you are upgrading from a version older than ESB 5.0.0, you will need to first upgrade to ESB 5.0.0 and then upgrade to WSO2 EI 6.1.0.

  • For information on the default ports in WSO2 EI runtimes, see Default ports of WSO2 EI.
  • The distribution folder structure has changed from ESB 5.0.0 to WSO2 EI 6.1.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


Migrating the configuration files

  1. In WSO2 EI 6.1.0 you can use the same database that you used in ESB 5.0.0. Configure WSO2 EI 6.1.0 to use the existing database as follows:

    1. Copy the database drivers from <ESB_HOME>/repository/components/lib directory to <EI_HOME>/lib directory. 
    2. Copy <ESB_HOME>/repository/conf/datasources/master-datasources.xml file to <EI_HOME>/conf/datasources directory. This will update the datasource configuration in WSO2 EI.
    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 that you made in the above step. 
  2. If there are any third-party libraries used with ESB 5.0.0 that you want to migrate, copy the contents of the following directories as applicable from ESB 5.0.0 to EI 6.1.0: 
    • If you have used JMS libraries, JDBC libraries, etc., copy the files from <ESB_HOME>/repository/components/lib directory to <EI_HOME>/lib directory.
    • If you have used OSGi bundles such as SVN kit etc., copy the contents of <ESB_HOME>/repository/components/dropins directory to <EI_HOME>/dropins directory.
  3. Check for any other configurations that were done for ESB 5.0.0 based on your solution and update the configuration files in EI 6.1.0 accordingly. For example, configurations related to external user stores, caching, mounting, transports, etc.


    The following files have changed from ESB 5.0.0 to EI 6.0.0:

    • axis2.xml
    • axis2_nhttp.xml
    • axis2_pt.xml
    • tenant-axis2.xml
    • cache.xml
    • config-validation.xml
    • osgi-debug.option
    • cloud-services-desc.xml
    • authenticators.xml
    • catalina-server.xml
    • carbon.xml
    • identity.xml
    • synapse-handlers.xml
    • user-mgt.xml

    Do not copy and paste the configuration files as there are some changes from ESB 5.0.0 to EI 6.1.0. You need to update the configuration files based on the usage.

Migrating configurations for the EI Analytics profile

Note that this step is required only if the database type configured with the EI Analytics profile is either H2 or MySQL.

If you want to connect your EI Analytics 6.1.0 installation to the same databases that were used with your previous Analytics installation, update the configurations in the <EI_HOME>/wso2/analytics/conf/analytics/rdbms-config.xml file according to the configurations in the same file of your previous Analytics installation.

Migrating artifacts

You should manually deploy Composite Application Archive (CAR) files that you have in ESB 5.0.0 to EI 6.1.0. If you have a mediator packed in a CAR, all the artifacts using that mediator should also be included in the same CAR. See Deploying Composite Applications in the Server in WSO2 Admin Guide for further details.

To migrate deployment artifacts including ESB message flow configurations, copy the required Synapse artifacts from the <ESB_HOME>/repository/deployment/server/synapse-configs/default directory of ESB 5.0.0 to EI 6.1.0.

If you have created a messages store in your configuration and configured the provider path as repository/conf/ in your ESB 5.0.0 instance, this needs to be updated with the file path in EI 6.1.0. To do this, edit the message store artifact so that the provider path is configured as conf/

Migrating tenant artifacts

If multi-tenancy is used, copy the tenant artifacts from <ESB_HOME>/repository/tenants directory from ESB 5.0.0 to EI 6.1.0.

You may not be able to access the tenant domain after migrating to EI 6.1.0. To fix this issue, change the tenant’s main sequence located in <EI_HOME>/repository/tenants/1/synapse-configs/default/sequences/main.xml as below:

<sequence xmlns="" name="main">
  • No labels