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

WSO2 EI 6.6.0 requires Message Processor Tasks to be stored in the registry using a new naming convention. The naming convention has changed from
TASK_PREFIX + messageProcessorName + taskNumber (in WSO2 EI 6.5.0) to TASK_PREFIX + messageProcessorName + SYMBOL_UNDERSCORE + taskNumber (in WSO2 EI 6.6.0).

When you run the following migration client, the existing Task references in the registry will be removed. Later in this migration guide, when you migrate the integration artifacts from your EI 6.5.0 instance to EI 6.6.0, new records will be created in the registry with the new naming convention.

To run the migration client:

...

Step 1: Set up the WSO2 EI 6.6.0 server

Apply the following updates to your EI 6.6.0 server.

Connect the ESB profile of EI 6.6.0 to your existing databases (which are used for registry data and user management data):

Panel
borderColor#542989
bgColor#ffffff
borderWidth1
Expand
titleConnecting to the database
  1. Open the master-datasources.xml file (stored in the <EI_6.6.0_HOME>/conf/datasources/ directory) and update the parameters given below.

    Tip

    By default, registry and user management data are stored in one database and is configured in the master-datasources.xml file. If you have separate databases for registry and user management data, you may need separate datasource configurations.

    ElementDescription
    urlThe URL of the database.
    username and passwordThe name and password of the database user.
    driverClassNameThe class name of the database driver.
  2. Open the registry.xml file (stored in the <EI_6.6.0_HOME>/conf directory) and specify the datasource name (as defined in step 'a').

    Code Block
    <dbConfig name="wso2registry">    
        <dataSource>jdbc/MY_DATASOURCE_NAME</dataSource>
    </dbConfig>
  3. If a JDBC user store is used, open the user-mgt.xml file (stored in the <EI_6.6.0_HOME>/conf/ directory), and update the following database connection parameters under the <UserStoreManager class="org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager"> section.

    ElementDescription
    urlThe URL of the database.
    username and passwordThe name and password of the database user.
    driverClassNameThe class name of the database driver.
  4. Further, update the system administrator configurations and the datasource name in the user-mgt.xml file. See Configuring a JDBC user store for instructions.


Step 2: Run the migration client

Now, let's run the migration client from EI 6.6.0. This client changes any message processor data according to the new naming convention.

  1. Create a folder named 'migration' inside  <EI_6.6.0_HOME> .

  2. Copy the  migration-conf.properties  file to the <EI_6.56.0_HOME>/migration folder  folder and update the following properties:

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

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


  3. Copy Download the migration JAR file and copy it to the <EI_6.56.0_HOME>/dropins/ directory.
  4. Open a terminal and navigate to the <EI_6.

    5

    6.0_HOME>/bin/ directory.

  5. 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
  6. 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.56.0_HOME>/dropins/ directory.

...

  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. 
  3. 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>/repository/deployment/server/ directory to the same directory in WSO2 EI 6.6.0.
  4. If there are any third-party libraries used with WSO2 EI 6.5.0 that you want to migrate, copy the relevant libraries 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.

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

  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_6.6.0_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 <EIthe <EI_6.6.0_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 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_6.6.0_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.

...

  • To migrate mediation artifacts including message flow configurations, copy the required Synapse artifacts from the <EI_6.5.0_HOME>/repository/deployment/server/synapse-configs/default directory to the same directory in WSO2 EI 6.6.0.
  • To migrate connector artifacts: 
    • Create a folder named synapse-libs in the <EI_6.6.0_HOME>/repository/deployment/server/synapse-configs/default/ directory of WSO2 EI 6.6.0, and copy the JARs from the directory by the same name in WSO2 EI 6.5.0. Note that this directory will not exist in your WSO2 EI 6.5.0 distribution if no connectors are used.
    • Copy the JARs from the <EI_6.5.0_HOME>/repository/deployment/server/synapse-configs/default/imports directory to the same directory in WSO2 EI 6.6.0.
  • To migrate the data service artifacts, copy the <EI_6.5.0_HOME>/repository/deployment/server/dataservices directory to the same directory in WSO2 EI 6.6.0.
  • If you have custom artifacts created in the <EI_6.5.0_HOME>/repository/deployment/server/ directory, copy them to the same directory in WSO2 EI 6.6.0.
  • If multitenancy is used, copy the tenant artifacts from the <EI_6.5.0_HOME>/repository/tenants directory to the same directory in 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 WSO2 EI 6.6.0.
  2. Copy the keystores and truststores used in the Message Broker profile of WSO2 EI 6.5.0 from the <EI_6.5.0_HOME>/wso2/broker/repository/resources/security directory to the same directory in WSO2 EI 6.6.0.
  3. If you have secondary user stores created for the Message Broker profile of WSO2 EI 6.5.0, you need to copy the 'userstore' folder in the <EI_6.5.0_HOME>/wso2/broker/repository/deployment/server/ directory to the same directory in WSO2 EI 6.6.0.

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

  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_6.6.0_HOME>/wso2/broker/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file. See Changing the Carbon Database  for  for instructions.

  3. Update the configurations related to the broker-specific database in the master-datasources.xml file and other related configurations files. See  See Changing the Default Broker Carbon Database  for instructions.

  4. Go to the <EI_6.6.0_HOME>/wso2/broker/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 in Changing the Carbon Database .
  5. Check for any further configurations that were done for the Message Broker profile in WSO2 EI 6.5.0 based on your solution. For example, check and update the following configurations in the Message Broker profile of WSO2 EI 6.6.0:

    1. broker.xml

    2. metrics.xml

    3. metrics-properties.xml

    4. messaging-event-broker.xml

    5. Check configurations related to external user stores, caching, mounting, transports etc.

  6. See the instructions on migrating log4j configurations for the Message Broker profile.

Migrating artifacts of the Message Broker profile

If multitenancy is used, copy the tenant artifacts from the <EI_6.5.0_HOME>/wso2/broker/repository/tenants directory to the same directory in WSO2 EI 6.6.0.

...

  1. Update the configuration files with information of the migrated keystores and truststores. For more information, see Configuring Keystores in WSO2 products.
  2. Go to the <EI_6.6.0_HOME>/wso2/business-process/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_6.6.0_HOME>/wso2/business-process/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 fileThe instructions are available in Changing the Carbon Database .
  4. Go to the <EI_6.6.0_HOME>/wso2/business-process/conf/datasources directory and update the files relevant to your BPMN/BPEL database: 
    • If you are using BPMN, update the activiti-datasources.xml file with the datasource connection details.
    • If you are using BPEL, update the bps-datasources.xml file with the datasource connection details.
    For instructions, see Changing the Default Databases for BPMN and BPEL .
  5. Open the <EI_6.6.0_HOME>/wso2/business-process/conf/humantask.xml file and change GenerateDdl to false. You can see the deployed human task packages with the version in the console. A migration success message is printed once the migration completes successfully.

    Code Block
    <GenerateDdl>false</GenerateDdl>
  6. Check for any further configurations that were done for the Business Process profile of WSO2 EI 6.5.0 based on your solution. For example, check and update the following configurations in WSO2 EI 6.6.0:

    1. humantask.xml

    2. axis2.xml

    3. bps.xml

    4. Activiti.xml

    5. Tenant-mgt.xml

    6. b4p-coordination-config.xml

    7. process-cleanup.properties

    8. Check the configurations related to external user stores, caching, mounting, transports, etc.

  7. See the instructions on migrating log4j configurations for the Business Process profile.

...