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

Versions Compared


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


  1. Copy the database connector JAR files stored in the <ESB_HOME>/repository/components/lib directory to the <EI_HOME>/lib directory.
  2. Copy the keystores and truststores used in the WSO2 ESB 5.0.0 from the <ESB_HOME>/repository/resources/security directory to the <ESB<EI_HOME>/repository/resources/security directory in WSO2 EI 6.1.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>/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file with the details of the Carbon database.
    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.

  4. If you have secondary user stores created for WSO2 ESB 5.0.0, you need to copy the 'userstore' folder in the <ESB_HOME>/repository/deployment/server/ directory to the <EI_HOME>/repository/deployment/server/ directory in WSO2 EI 6.1.0.
  5. If there are any third-party libraries used with WSO2 ESB 5.0.0 that you want to migrate, copy the relevant libraries them to WSO2 EI 6.1.0: 
    • If you have used JMS libraries, JDBC libraries, etc., copy the files from the <ESB_HOME>/repository/components/lib directory to to the <EI_HOME>/lib directory.
    • If you have used OSGi bundles such as SVN kit etc., copy the contents of the <ESB_HOME>/repository/components/dropins directory to to the <EI_HOME>/dropins directory.
  6. Check for any other configurations that were done for WSO2 ESB 5.0.0 based on your solution, and update the configurations in WSO2 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 WSO2 EI 6.1.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.


  • To migrate deployment artifacts including message flow configurations, copy the required Synapse artifacts from the <ESB_HOME>/repository/deployment/server/synapse-configs/default directory of WSO2 ESB 5.0.0 to WSO2 EI 6.1.0.
  • To migrate any connector artifacts, copy the JARs from the <ESB_HOME>/repository/deployment/server/synapse-configs/default/synapse-libs and <ESB_HOME/repository/deployment/server/synapse-configs/default/imports/ directories in WSO2 ESB 5.0.0 to the same directories in WSO2 EI 6.1.0.
  • If you have custom artifacts created in the <ESB_HOME>/repository/deployment/server/ directory of WSO2 ESB 5.0.0, copy them to the same directory in WSO2 EI 6.1.0.


  • Copy the tenant artifacts of ESB from the <ESB_HOME>/repository/tenants directory to the <EI_HOME>/repository/tenants directory of EI of WSO2 EI 6.1.0.


    You may not be able to access the tenant domain after migrating to WSO2 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:

    Code Block
    <sequence xmlns="" name="main">
  • If you are migrating ESB Analytics to the Analytics profile of WSO2 EI, copy the <ESB_ANALYTICS_HOME>/repository/tenants directory to the <EI_HOME>/wso2/analytics/repository/tenants directory of WSO2 EI 6.1.0.