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.

...

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

...

Analytics profile

If you have configured EI 6.5.0 to WSO2 to publish ESB data to the Analytics profile, you need to enable the same in 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 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.

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
:
  1. .
  2. Update the configuration files with information of the migrated keystores and truststores. For instructions, see Configuring Keystores in WSO2 products.

  3. Go to the <EICopy 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/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file. See Changing the Carbon Database for instructions.
  4. 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.

  5. Go to the <EIresources/security directory to the same directory in WSO2 EI 6.6.0.
  6. 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/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.
  7. 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.

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

Business Process profile

...

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

...

Migrating configurations of the Business Process profile

Note

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

...

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

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

...

.

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.

    If you have secondary user stores created for

     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 , you need to from the <EI_6.5.0_HOME>/wso2/business-process/repository/resources/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.

...

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 packages in the <EI_6.5.0_HOME>/wso2/business-process/repository/deployment/server/bpel directory , copy them to the same directory in WSO2 EI 6.6.0.If multitenancy
  • is used, copy the tenant artifacts from the 

    Copy the BPMN .bar packages in the <EI_6.5.0_HOME>/wso2/business-process/repository

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

Analytics profile

...

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

Migrating Log4j configurations

...