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.

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>

Migrating artifacts of the ESB profile

...