This documentation is for WSO2 Enterprise Integrator version 6.0.0 . View documentation for the latest release.

All docs This doc
Skip to end of metadata
Go to start of metadata

This page walks you through the process of upgrading to WSO2 Enterprise Integrator (WSO2 EI) 6.0.0 from WSO2 Business Process Server (WSO2 BPS) 3.6.0.

If you are upgrading from a version older than WSO2 BPS 3.6.0, you will need to first upgrade to WSO2 BPS 3.6.0 and then upgrade to WSO2 EI 6.0.0.

  • For information on the default ports in WSO2 EI runtimes, see Default ports of WSO2 EI.
  • The distribution folder structure has changed from WSO2 BPS 3.6.0 to WSO2 EI 6.0.0. The changes in the folder structure for directory locations of the configuration related files are as follows:
Enterprise Service Bus 5.0.0Enterprise Integrator 6.0.0


Migrating the database

When upgrading to WSO2 EI 6.0.0, you can use the same database you used for WSO2 BPS 3.6.0. Follow the steps below to configure WSO2 EI 6.0.0 database to connect to WSO2 BPS 3.6.0 database:

  1. Copy database connector .jar files from <BPS_HOME>/repository/components/lib to <EI_HOME>/lib directory. For example, the ojdbc7.jar for the Oracle database can be copied here.

  2. Upgrade the database configuration in WSO2 EI as follows:
    1. Copy <BPS_HOME>/repository/conf/datasources/master-datasources.xml file to <EI_HOME>/wso2/business-process/conf/datasources directory. 
    2. Copy <BPS_HOME>/repository/conf/datasources/activiti-datasources.xml file to <EI_HOME>/wso2/business-process/conf/datasources directory. 
    3. Copy <BPS_HOME>/repository/conf/datasources/bps-datasources.xml file to <EI_HOME>/wso2/business-process/conf/datasources directory.
  3. If you have used customized database names for the user and registry databases you have to update them in the registry.xml and user-mgt.xml files.

    1. Update the database name for the registry database in the <EI_HOME>/wso2/business-process/conf/registry.xml file.
    2. Update the database name for the user database in the <EI_HOME>/wso2/business-process/conf/user-mgt.xml file.
  4. Open the <EI_HOME>/wso2/business-process/conf/humantask.xml file and change GenerateDdl to false .You can see the deployed humantask packages with the version in the console. A migration success message is printed once the migration completes successfully.


Migrating configuration files

Check for any configurations that were done for WSO2 BPS 3.6.0 based on your solution and update the following configuration files in EI 6.0.0 accordingly:

    • humantask.xml

    • axis2.xml

    • bps.xml

    • Activiti.xml

    • Tenant-mgt.xml

    • b4p-coordination-config.xml


Migrating artifacts

  1. Copy the BPEL .zip packages in <BPS_HOME>/repository/deployment/server/bpel directory to <EI_HOME>/wso2/business-process/repository/deployment/server/bpel directory.
  2. Copy the BPMN .bar packages in <BPS_HOME>/repository/deployment/server/bpmn directory to <EI_HOME>/wso2/business-process/repository/deployment/server/bpmn directory. 

  3. Copy the humantask .zip packages in <BPS_HOME>/repository/deployment/server/humantasks to <EI_HOME>/wso2/business-process/repository/deployment/server/humantasks directory.

Migrating tenant artifacts

Copy the tenant directory packages from <BPS_HOME>/repository/tenants to <EI_HOME>/wso2/business-process/repository/tenants directory.

Starting the server

Once you have completed the migration, you can start the EI-Business Process runtime. For details see Running the Product.

The Management Console, BPMN Explorer and Human Task Explorer URLs for the EI-Business Process runtime in WSO2 EI 6.0.0 are as follows:

  • Management Console : https://<ip>/<port>:9445/carbon/

  • BPMN Explorer : https://<ip>/<port>:9445/bpmn-explorer

  • HumanTask Explorer : https://<ip>/<port>:9445/humantask-explorer

  • No labels