This documentation is for WSO2 Enterprise Integrator version 6.2.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

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.2.0 from WSO2 Business Process Server (WSO2 BPS) 3.6.0.

For information on what is new in this release and why you should upgrade, see About this Release.

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

  • See Default ports of WSO2 Products in the WSO2 Administration Guide, for more information on ports. The default ports in WSO2 EI are listed under Enterprise Integrator.
  • The distribution folder structure has changed from WSO2 BPS 3.6.0 to WSO2 EI 6.2.0. The changes in the folder structure for directory locations are as follows:

    Business Process Server 3.6.0Enterprise Integrator 6.2.0

See the following topics for instructions:

Upgrading the databases

In WSO2 EI 6.2.0, you can use the same Carbon database and BPEL/BPMN databases that you used for WSO2 BPS 3.6.0. Therefore, you can simply restore the backup of the existing databases to use with WSO2 EI 6.2.0.

Migrating the configurations

Follow the steps below:

  1. Copy the database connector JAR files stored in the <BPS_HOME>/repository/components/lib directory of WSO2 BPS 3.6.0 to WSO2 EI 6.2.0. For example, the JAR for the Oracle database (ojdbc7.jar) can be copied.

  2. Copy the keystores and truststores used in WSO2 BPS 3.6.0, from the <BPS_HOME>/repository/resources/security directory to the <EI_HOME>/wso2/business-process/repository/resources/security directory in WSO2 EI 6.2.0.
  3. Update the configuration files.
    1. Update the configuration files with information of the migrated keystores and truststores. See Configuring Keystores in WSO2 products for more information.
    2. Go to the <EI_HOME>/wso2/business-process/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file with the details of the Carbon database.
    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 file.
    4. Go to the <EI_HOME>/wso2/business-process/conf/datasources directory and update the activiti-datasources.xml file with details of the datasource connection to the BPMN database.
    5. Go to the <EI_HOME>/wso2/business-process/conf/datasources directory and update the bps-datasources.xml file with details of the datasource connection to the BPEL database.
    6. 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.

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

      • humantask.xml

      • axis2.xml

      • bps.xml

      • Activiti.xml

      • Tenant-mgt.xml

      • b4p-coordination-config.xml


  4. If you have secondary user stores created for WSO2 BPS 3.6.0, you need to copy the 'userstore' folder in the <BPS_HOME>/repository/deployment/server/ directory to the <EI_HOME>/wso2/business-process/repository/deployment/server/ directory in WSO2 EI 6.2.0.
  5. Check for any other configurations that were done for WSO2 BPS 3.6.0 based on your solution and update the configurations in WSO2 EI 6.2.0 accordingly. For example, configurations related to external user stores, caching, mounting, transports etc.

Migrating artifacts

Follow the steps given below:

  1. Copy the BPEL .zip packages in the <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 the <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 the <BPS_HOME>/repository/deployment/server/humantasks directory to <EI_HOME>/wso2/business-process/repository/deployment/server/humantasks directory.
  4. If you have custom artifacts created in the <BPS_HOME>/repository/deployment/server/ directory of WSO2 BPS 3.6.0, copy them to the <EI_HOME>/wso2/business-process/repository/deployment/server/ in WSO2 EI 6.2.0.
  5. If you have used multitenancy, copy the tenant directory packages from <BPS_HOME>/repository/tenants to the <EI_HOME>/wso2/business-process/repository/tenants directory.

Starting the server

Once you have completed the migration, you can start the Business Process profile of WSO2 EI. For details see Running the Product.

The Management Console, BPMN Explorer and Human Task Explorer URLs for the Business Process profile in WSO2 EI 6.2.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