Upgrading from WSO2 Enterprise Service Bus

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

<clone sequential="true">
    <target>
         <sequence>
              <send>
                   <endpoint key="ABC"/>
               </send>
         </sequence>
     </target>
     <target>
         <sequence>
             <switch xmlns:ns="http://org.apache.synapse/xsd" source="get-property('XYZ')">
                  <case regex="CASE1 ">
                       <log level="custom">
                           <property name="#### CASE ####" value="IN CASE1"/>
                       </log>
                       <sequence key="TEST.PQR "/>
                        <drop/>
                     </case>
                     <default>
                        <log level="custom">
                           <property name="#### DEFAULT ####" value="IN DEFAULT"/>
                        </log>
                        <drop/>
                     </default>
                  </switch>
           </sequence>
     </target>
</clone>

Migrating the configuration files

1. In WSO2 EI 6.0.0 you can use the same database that you used in ESB 5.0.0. Configure WSO2 EI 6.0.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.0.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.0.0 accordingly. For example, configurations related to external user stores, caching, mounting, transports, etc.

   Note

   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
   • logging-bridge.properties
   • osgi-debug.option
   • cloud-services-desc.xml
   • authenticators.xml
   • ciper-tool.properties
   • catalina-server.xml
   • carbon.xml
   • identity.xml
   • nhttp.properties
   • passthru-http.properties
   • synapse.properties
   • synapse-handlers.xml
   • user-mgt.xml
   • jndi.properties



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

Migrating artifacts

You should manually deploy Composite Application Archive (CAR) files that you have in ESB 5.0.0 to EI 6.0.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.0.0.

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.0.0.

<sequence xmlns="http://ws.apache.org/ns/synapse" name="main">
   <in>
      <log/>
   </in>
   <out>
      <send/>
   </out>
</sequence>