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

Migrating artifacts of the ESB profile

You should manually deploy the Composite Application Archive (C-APP) files that you have in WSO2 EI 6.65.0 is based on Carbon Kernel 4.5.0 and, therefore, log4j2 is introduced. Also, the carbon.logging jar is not packed with the to WSO2 EI 6.6.0.

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

...

  1. Replace carbon logging or commons.logging dependencies with pax-logging dependency:

    Code Block
    <!-- Pax Logging -->
    <dependency>
       <groupId>org.ops4j.pax.logging</groupId>
       <artifactId>pax-logging-api</artifactId>
       <version>${pax.logging.api.version}</version>
    </dependency>
    
    <!-- Pax Logging Version -->
    <pax.logging.api.version>1.10.1</pax.logging.api.version>
  2. If log4j dependency is directly used:

    1. Option 1Replace the log4j dependency with log4j2 and rewrite the loggers accordingly:

      Code Block
      <dependency>
         <groupId>org.ops4j.pax.logging</groupId>
         <artifactId>pax-logging-log4j2</artifactId>
         <version>${pax.logging.log4j2.version}</version>
      </dependency>
    2. Option 2Replace log4j dependency with pax-logging dependency and rewrite the loggers using commons.logging accordingly.

  3. If commons.logging is imported using Import-Package add the version range. org.apache.commons.logging; version="${commons.logging.version.range}" <commons.logging.version.range>[1.2.0,2.0.0)</commons.logging.version.range>

Migrating artifacts of the ESB profile

...

    • 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:

Message Broker profile

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

Migrating configurations of the Message Broker 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 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>/

...

  1. wso2/

...

  1. broker/

...

  1. repository/

...

  1. resources/

...

  1. security directory to the same directory in WSO2 EI 6.6.0.

...

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

...

  1.  directory to the same directory in WSO2 EI 6.6.0

...

  1. .

Anchor
updating_configs_mb
updating_configs_mb
To migrate the configurations from WSO2 EI 6.5.0

...

to WSO2 EI 6.

...

Message Broker profile

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

Migrating configurations of the Message Broker 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:

Copy the database connector JAR files stored in the 

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

  3. Update the configurations related to the broker-specific database in the master-datasources.xml file and other related configurations files. See Changing the Default Broker 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 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>

/lib directory

/wso2/broker/repository/tenants directory to the same directory in WSO2 EI 6.6.0.

Copy the keystores and truststores used in the Message Broker profile of WSO2 EI 6.5.0 from the <EI_

Business Process profile

Follow the instructions given below to upgrade the Business Process profile from WSO2 EI 6.5.0

...

to

...

WSO2 EI 6.6.0.

...

Migrating configurations of the Business Process 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 in the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.6.0. For example, the JAR for the Oracle database (ojdbc7.

...

  1. jar) can be copied.

  2. Copy the keystores and truststores used in the Business Process profile of WSO2 EI 6.5.0

...

  1. from the <EI_6.

...

  1. 5.0

...

Update the configuration files with information of the migrated keystores and truststores. For instructions, see Configuring Keystores in WSO2 products.

...

  1. _HOME>/wso2/business-process/

...

  1. repository/

...

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

...

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.

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.

Business Process profile

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

Migrating configurations of the Business Process 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 in the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.6.0. For example, the JAR for the Oracle database (ojdbc7.jar) can be copied.

  2. Copy the keystores and truststores used in the Business Process profile of WSO2 EI 6.5.0 from the <EI_6.5.0resources/security directory to the same directory in WSO2 EI 6.6.0.
  3. If you have secondary user stores created for the Business Process profile of WSO2 EI 6.5.0, you need to copy the 'userstore' folder in the <EI_6.5.0_HOME>/wso2/business-process/repository/deployment/server/ directory to the same directory in WSO2 EI 6.6.0.

Anchor
updating_configs_bp
updating_configs_bp
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 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/

    repository/resources/security directory to the same directory in WSO2 EI 6.6.0.If you have secondary user stores created

    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, you need to copy the 'userstore' folder in the <EI_

    6.5.0

    _HOME>/wso2/business-process/repository/deployment/server/ directory to the same directory

    based on your solution. For example, check and update the following configurations in WSO2 EI 6.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

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

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

Migrating artifacts of the Business Process profile

Follow the steps given below:

  • Copy the BPEL .zip packages in the <EI_6.5.0_HOME>/wso2/business-process/repository/deployment/

...

  • server/

...

  • bpel directory

...

  • to the same directory in WSO2 EI 6.6.0.
  • Copy the BPMN .bar packages in the <EI_6.5.0_HOME>/wso2/business-process

...

  • /repository/deployment/server/bpmn directory to the same directory in WSO2 EI 6.6.0. 

  • Copy the humantask .zip packages in the <EI_6.5.0_HOME>/wso2/business-process/

...

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

...

  • repository/deployment/server/humantasks directory to the same directory in WSO2 EI 6.6.0.
  • If you have custom artifacts created in the <EI_6.5.0_HOME>/wso2/business-process/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>/wso2/business-process/

...

Code Block
<GenerateDdl>false</GenerateDdl>

...

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.

Migrating artifacts of the Business Process profile

Follow the steps given below:

  • Copy the BPEL .zip packages in the <EI_6.5.0_HOME>/wso2/business-process/repository/deployment/server/bpel directory to the same directory in WSO2 EI 6.6.0.
  • Copy the BPMN .bar packages in the <EI_6.5.0_HOME>/wso2/business-process/repository/deployment/server/bpmn directory to the same directory in WSO2 EI 6.6.0. 

  • Copy the humantask .zip packages in the <EI_6.5.0_HOME>/wso2/business-process/repository/deployment/server/humantasks directory to the same directory in WSO2 EI 6.6.0.
  • If you have custom artifacts created in the <EI_6.5.0_HOME>/wso2/business-process/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>/wso2/business-process/repository/tenants directory to the same directory in WSO2 EI 6.6.0.

Analytics profile

If you have configured EI 6.5.0 to publish ESB data to the Analytics profile, you need to enable the same in EI 6.6.0. To do this, follow the instructions in Publishing ESB Data to Analytics.

...

  • repository/tenants directory to the same directory in WSO2 EI 6.6.0.

Analytics profile

If you have configured EI 6.5.0 to publish ESB data to the Analytics profile, you need to enable the same in EI 6.6.0. To do this, follow the instructions in Publishing ESB Data to Analytics.

Info

Note that from EI 6.6.0 onwards, you need to configure the <EI_HOME>/conf/carbon.xml file to enable the ESB server to publish statistics to the Analytics profile, whereas in the EI 6.5.0 and older versions you need to configure the<EI_HOME>/repository/deployment/server/eventpublishers/MessageFlowConfigurationPublisher.xml and <EI_HOME>/repository/deployment/server/eventpublishers/MessageFlowStatisticsPublisher.xml files instead.

Migrating Log4j configurations

Tip

The following configurations apply when migrating all profiles of WSO2 EI from version 6.5.0 to 6.6.0.

WSO2 EI 6.6.0 is based on Carbon Kernel 4.5.0 and, therefore, log4j2 is introduced. Also, the carbon.logging jar is not packed with the EI 6.6.0 distribution and the pax-logging-api is used instead. When you migrate from WSO2 EI 6.5.0 to WSO2 EI 6.6.0, be sure to follow the instructions on configuring log4j2. If you have used a custom log4j component in EI 6.5.0, be sure to apply the following changes to your component:

  1. Replace carbon logging or commons.logging dependencies with pax-logging dependency:

    Code Block
    <!-- Pax Logging -->
    <dependency>
       <groupId>org.ops4j.pax.logging</groupId>
       <artifactId>pax-logging-api</artifactId>
       <version>${pax.logging.api.version}</version>
    </dependency>
    
    <!-- Pax Logging Version -->
    <pax.logging.api.version>1.10.1</pax.logging.api.version>
  2. If log4j dependency is directly used:

    1. Option 1Replace the log4j dependency with log4j2 and rewrite the loggers accordingly:

      Code Block
      <dependency>
         <groupId>org.ops4j.pax.logging</groupId>
         <artifactId>pax-logging-log4j2</artifactId>
         <version>${pax.logging.log4j2.version}</version>
      </dependency>
    2. Option 2Replace log4j dependency with pax-logging dependency and rewrite the loggers using commons.logging accordingly.

  3. If commons.logging is imported using Import-Package add the version range. org.apache.commons.logging; version="${commons.logging.version.range}" <commons.logging.version.range>[1.2.0,2.0.0)</commons.logging.version.range>

Starting the profiles

You can now start the WSO2 EI 6.6.0 product. For instructions on starting each of the profiles in the product, see Running the Product.