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.

...

  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. Verify that the keystores are migrated.  See Configuring Keystores in WSO2 products.

    Tip

    If you successfully followed the instructions on upgrading the databases, the keystore configurations should already be migrated by now.

  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.

...

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

...

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

...