This is the latest release in the 6.x.x family. For EI 7.0.0, click here.

All docs This doc

Versions Compared

Key

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

...

Info

The downtime is limited to the time taken for switching databases in the production environment.

ESB profile

Follow the instructions given below to upgrade the ESB profile from WSO2 EI 6.5.0 to WSO2 EI 6.6.0.

Upgrading the databases

You can use the same databases that you used for the ESB profile of WSO2 EI 6.5.0 with WSO2 EI 6.6.0. However, you need to first apply the following updates.

...

To run the migration client:

  1. Create the <EI_HOME>/migration/ directory inside <EI_6.5.0_HOME>, copy the migration-conf.properties file, and update the following property:

    admin.user.nameThe user name of the system administrator.

    Note that you do not need to update the keystore-related properties given in the file.

  2. Copy the migration JAR file to the <EI_6.5.0_HOME>/dropins/ directory.
    1. Open a terminal and navigate to the <EI_6.5.0_HOME>/bin/ directory.

    2. Execute the product startup script with the '-Dmigrate.from.product.version=ei650' command as shown below.

      Panel
      borderColor#542989
      bgColor#ffffff
      borderWidth1
      Localtab Group
      Localtab
      titleOn MacOS/Linux/CentOS

      Open a terminal and execute the following command:

      Code Block
      sh integrator.sh -Dmigrate.from.product.version=ei650
      Localtab
      titleOn Windows

      Open a terminal and execute the following command:

      Code Block
      integrator.bat -Dmigrate.from.product.version=ei650
  3. Once the migration is successful, stop the server and delete the migration JAR (org.wso2.carbon.ei.migration-6.6.0.jar) from the <EI_6.5.0_HOME>/dropins/ directory.
  4. You can now connect your WSO2 EI 6.6.0 instance to the old database. This is discussed under Migrating configurations of the ESB profile.

Migrating configurations of the ESB profile

Info

We are no more packing smb provider by default. If you need to use VFS SMB feature, please download the  jcifs-1.3.17.jar from here then place it in <EI_HOME/lib directory and continue with the feature. Please note that, since the above library is licensed under LGPL version 2.1 and by downloading and installing the library you will have to comply with the terms of LGPL version 2.1 and its restrictions as found in this page.

...

Note

 Do not copy configuration files directly between servers. Instead, update the files manually.

To migrate all the required folders, files, libraries, etc. from WSO2 EI 6.5.0 to WSO2 EI 6.6.0:

  1. Copy the database connector JAR files stored in the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.6.0.
  2. Copy the keystores and truststores used in the ESB profile of WSO2 EI 6.5.0 from the <EI_6.5.0_HOME>/repository/resources/security directory to the same directory in WSO2 EI 6.6.0.

...

Migrating configurations of the ESB profile

Note

 Do not copy configuration files directly between servers. Instead, update the files manually.

To migrate all the required folders, files, libraries, etc. from WSO2 EI 6.5.0 to WSO2 EI 6.6.0:

  1. Copy the database connector JAR files stored

     

  2. If you have secondary user stores created for the ESB profile of WSO2 EI 6.5.0, you need to copy the 'userstore' folder in the <EI_6.5.0_HOME>/lib directory repository/deployment/server/ directory to the same directory in WSO2 EI 6.6.0.Copy the keystores and truststores used in the ESB profile of
  3. If there are any third-party libraries used with WSO2 EI 6.5.0 from the <EI_that you want to migrate, copy the relevant libraries from WSO2 EI 6.5.0 _HOME>/repository/resources/security directory to the same directory in WSO2 EI 6.6.0.: 
    • If you have
    secondary user stores created for the ESB profile of
    • used JMS libraries, JDBC libraries, etc., copy the contents from the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.
    5
    • 6.0
    , you need to copy the 'userstore' folder in
    • .
    • If you have used OSGi bundles such as SVN kit etc., copy the contents from the <EI_6.5.0_HOME>/
    repository/deployment/server/ directory
    • dropins directory to the same directory in WSO2 EI 6.6.0.
    If there are any third-party libraries used with WSO2 EI 6.5.0 that you want to migrate, copy the relevant libraries

Anchor
updating_configs_esb
updating_configs_esb
To migrate the configurations from WSO2 EI 6.5.0 to WSO2 EI 6.6.0:

...

  • If you have used JMS libraries, JDBC libraries, etc., copy the contents from the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.6.0.
  • If you have used OSGi bundles such as SVN kit etc., copy the contents from the <EI_6.5.0_HOME>/dropins directory to the same directory in WSO2 EI 6.6.0.

...

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. The instructions are available in Changing the Carbon Database.

...

Check for any other configurations that were done for WSO2 EI 6.5.0 based on your solution, and update the configuration files in WSO2 EI 6.6.0 accordingly. For example, check the configurations related to external user stores, caching, mounting, transports, etc.

...

  1. Update the configuration files with information of the migrated keystores and truststores. For instructions, see Configuring Keystores in WSO2 products.
  2. Go to the <EI_HOME>/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file. For instructions, see Changing the Carbon Database and select your database type.
  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. The instructions are available in Changing the Carbon Database.

  4. Check for any other configurations that were done for WSO2 EI 6.5.0 based on your solution, and update the configuration files in WSO2 EI 6.6.0 accordingly. For example, check the configurations related to external user stores, caching, mounting, transports, etc.

  5. See the instructions on migrating log4j configurations for the ESB profile.
Info

WSO2 EI no longer packs the smb provider by default. If you need to use the VFS SMB feature, you can download the  jcifs-1.3.17.jar from here and then place it in <EI_HOME/lib directory. Please note that (since the above library is licensed under LGPL version 2.1) by downloading and installing the library you have to comply with the terms of LGPL version 2.1 and its restrictions as found in this page.

Migrating artifacts of the ESB profile

...