||
Skip to end of metadata
Go to start of metadata

This topic describes how you can successfully migrate to WSO2 BPS 3.6.0 from the previous WSO2 BPS version (3.5.1). If you want to upgrade from earlier versions than 3.5.1/3.5.0, follow the instructions found here to migrate to version 3.5.1 and then use this guide.

Prior to doing the migration, download the latest version of BPS from http://wso2.com/products/business-process-server/. The location that you extract the latest version of BPS will be referred to as <NEW_BPS_HOME> in this document. <OLD_BPS_HOME> refers to the location of the previous version of BPS (BPS 3.5.1).

Important: Do not start the new BPS server until you finish all the steps mentioned in this document. When copying existing packages to the new BPS home directory, some directories will not be available. In these instances, you have to create new directories using the instructions in this topic.

Migration can be divided to three main steps.

Repository migration

BPEL package migration

  1. Copy the existing BPEL .zip packages from the <OLD_BPS_HOME>/repository/deployment/server/bpel directory to the <NEW_BPS_HOME>/repository/deployment/server/bpel directory.
  2. Copy the BPEL super tenant extracted packages from the <OLD_BPS_HOME>/repository/bpel/-1234/<extracted BPEL folder list> directory to the <NEW_BPS_HOME>/repository/bpel/-1234/<extracted BPEL folder list> directory.
  3. If you have any tenants, do the following.
    1. Create a <NEW_BPS_HOME>/repository/tenants/<tenantID>/bpel directory.
    2. Copy the existing BPEL .zip packages from the <OLD_BPS_HOME>/repository/tenants/<tenantID>/bpel to the newly created directory <NEW_BPS_HOME>/repository/tenants/<tenantID>/bpel.
    3. Create a <NEW_BPS_HOME>/repository/bpel/<tenantID>/ directory.
    4. Copy the BPEL tenant extracted packages from the <OLD_BPS_HOME>repository/bpel/<tenantID>/<extracted BPEL folder list> to the newly created directory <NEW_BPS_HOME>/repository/bpel/<tenantID>/<extracted BPEL folder list>.

Humantask package migration

  1. Copy the humantask .zip packages from <OLD_BPS_HOME>/repository/deployment/server/humantasks to the <NEW_BPS_HOME>/repository/deployment/server/humantasks directory.
  2. Copy super tenant extracted HumanTask packages from <OLD_BPS_HOME>/repository/humantasks/-1234/<extracted humantasks folder list> to the newly created directory at <NEW_BPS_HOME>/repository/humantasks/-1234/<extracted humantasks folder list>
  3. If you have any tenants,do the following.
    1. Create <NEW_BPS_HOME>/repository/tenants/<tenantID>/humantasks directory.
    2. Copy the humantask .zip packages from <OLD_BPS_HOME>/repository/tenants/<tenantID>/humantasks to the <NEW_BPS_HOME>/repository/tenants/<tenantID>/humantasks directory.
    3. Create <NEW_BPS_HOME>/repository/humantasks/<tenantID>/ directory.
    4. Copy humantask tenant extracted packages from <OLD_BPS_HOME>/repository/humantasks/<tenantID>/<extracted humantask folder list> to the newly created directory <NEW_BPS_HOME>/repository/humantasks/<tenantID>/<extracted humantasks folder list>.

BPMN Migration

  1. Copy the bpmn .bar packages from <OLD_BPS_HOME>/repository/deployment/server/bpmn to creating directory at <NEW_BPS_HOME>/repository/deployment/server/bpmn directory. 

  2. If you have any tenants,do the following.

    1. Create <NEW_BPS_HOME>/repository/tenants/<tenantID>/bpmn directory.
    2. Copy the humantask .zip packages from <OLD_BPS_HOME>/repository/tenants/<tenantID>/bpmn to the <NEW_BPS_HOME>/repository/tenants/<tenantID>/bpmn directory.

Database migration

  1. Point the existing user, registry and BPS databases to the new version of BPS. 

    You can have one database for both user and registry. 

    To do this, do the following.

    1. Configure the BPS datasource by modifying the <NEW_BPS_HOME>/repository/conf/datasources/bps-datasources.xml file.
    2. Configure the user and registry datasources by modifying the <NEW_BPS_HOME>/repository/conf/datasources/master-datasources.xml file.
  2. 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 <NEW_BPS_HOME>/repository/conf/registry.xml file.
    2. Update the database name for the user database in the <NEW_BPS_HOME>/repository/conf/user-mgt.xml file.
  3. Open the <NEW_BPS_HOME>/repository/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.

    <GenerateDdl>false</GenerateDdl>
  4. Copy database connector .jar files to the <NEW_BPS_HOME>/repository/components/lib directory. For example, the ojdbc7.jar for the Oracle database can be copied here.
  5. The Activiti database upgrades for Activiti databases will be automatically executed once you start the server for the first time. However, if you are enabling the user substitution feature, execute the <NEW_BPS_HOME>/dbscripts/bps/bpmn/activiti.<DBMS_NAME>.create.substitute.sql against your Activiti engine database.

  • No labels