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 Data Services Server (WSO2 DSS) 3.5.1.

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 DSS 3.5.1, you should first upgrade to WSO2 DSS 3.5.1 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 DSS 3.5.1 to WSO2 EI 6.2.0. The changes in the folder structure for directory locations are as follows:

    Data Service Server 3.5.1Enterprise Integrator 6.2.0

See the following topics for instructions:

Upgrading the database

In WSO2 EI 6.2.0, you can use the same database that you used for WSO2 DSS 3.5.1. Therefore, you can simply restore the backup of the existing databases to use with WSO2 EI 6.2.0.

Migrating the configurations

 Configurations should not be copied directly between servers.

Migrating configuration for the Integration profile

Follow the steps give below to migrate the configurations from WSO2 DSS 3.5.1 to the Integration profile of WSO2 EI 6.2.0.

  1. Copy the database connector JAR files stored in the <DSS_HOME>/repository/components/lib directory to the <EI_HOME>/lib directory.
  2. Copy the keystores and truststores used in the WSO2 DSS 3.5.1 from the <DSS_HOME>/repository/resources/security directory to the <EI_HOME>/repository/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>/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. Check for any configurations that were done for WSO2 DSS 3.5.1 based on your solution and update the following configuration files in WSO2 EI 6.2.0 accordingly:

        • axis2.xml

        • axis2_client.xml

        • carbon.xml

  4. If you have secondary user stores created for WSO2 DSS 3.5.1, you need to copy the 'userstore' folder in the <DSS_HOME>/repository/deployment/server/ directory to the <EI_HOME>/repository/deployment/server/ directory in WSO2 EI 6.2.0.
  5. If there are any third-party libraries used with WSO2 DSS 3.5.1 that you want to migrate, copy the relevant libraries to WSO2 EI 6.2.0: 
    • If you have used JMS libraries, JDBC libraries, etc., copy the files from <DSS_HOME>/repository/components/lib directory to the <EI_HOME>/lib directory.
    • If you have used OSGi bundles such as SVN kit etc., copy the contents of <DSS_HOME>/repository/components/dropins directory to the <EI_HOME>/dropins directory.
  6. Check for any other configurations that were done for WSO2 DSS 3.5.1 based on your solution, and update the configurations in WSO2 EI 6.2.0 accordingly. For example, configurations related to external user stores, caching, mounting, transports, etc.

Migrating artifacts

  • To migrate the data service artifacts, copy the <DSS_HOME>/repository/deployment/server/dataservices directory of WSO2 DSS 3.5.1 to WSO2 EI 6.2.0.
  • If you have custom artifacts created in the <DSS_HOME>/repository/deployment/server/ directory of WSO2 DSS 3.5.1, copy them to the <EI_HOME>/repository/deployment/server/ directory in WSO2 EI 6.2.0.
  • If multitenancy is used, copy the tenant directory packages from the <DSS_HOME>/repository/tenants directory to the <EI_HOME>/repository/tenants directory.

Starting the server

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

  • No labels