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.

...

Anchor
updating_configs_esb
updating_configs_esb
To migrate the configurations from EI 6.1.0 to EI 6.6.0:

  1. Go to the <EI_6.6.0_HOME>/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file. The instructions are available in Changing the Carbon Database .
  2. Go to the <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 Changing the Carbon Database .

  3. Check for any other configurations that were done for EI 6.1.0 based on your solution, and update the configuration files in EI 6.6.0 accordingly. For example, check the configurations related to external user stores, caching, mounting, transports, etc.

  4. 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.1.0_HOME>/repository/deployment/server/synapse-configs/default directory to the same directory in 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 EI 6.6.0, and copy the JARs from the directory by the same name in EI 6.1.0. Note that this directory will not exist in your EI 6.1.0 distribution if no connectors are used.
    • Copy the JARs from the <EI_6.1.0_HOME>/repository/deployment/server/synapse-configs/default/imports directory to the same directory in EI 6.6.0.
  • To migrate the data service artifacts, copy the <EI_6.1.0_HOME>/repository/deployment/server/dataservices directory to the same directory in EI 6.6.0.
  • If you have custom artifacts created in the <EI_6.1.0_HOME>/repository/deployment/server/ directory, copy them to the same directory in EI 6.6.0.
  • If multitenancy is used, copy the tenant artifacts from the <EI_6.1.0_HOME>/repository/tenants directory to the same directory in EI 6.6.0.

...

The default databases for the SP-based Analytics profile in EI 6.6.0 are available in the <EI_6.6.0_HOME>/wso2/analytics/wso2/<PROFILE>/database directory. However, you need to create the same databases and tables that you currently have in the DAS-based  Analytics profile in EI 6.1.0, and then transfer the data that you have in EI 6.1.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. The instructions are available in Changing the Carbon Database .

  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_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.
  5. Check for any further configurations that were done for the Message Broker profile in EI 6.1.0 based on your solution. For example, check and update the following configurations in the Message Broker profile of 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.

...

  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. The instructions are available in Changing the Carbon Database .
  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  file.
  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 EI 6.1.0 based on your solution. For example, check and update the following configurations in 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.

...