Migrating to the Latest BPS Version

This topic describes how you can successfully migrate to WSO2 BPS 3.2.0 version from previous WSO2 BPS versions (3.0.0 or 3.1.0) .

Migration procedure

Migration can be divided to three main steps:

Now, lets begin the migration process.

Repository migration

1. Migrate the BPEL packages. To do this:
   
   1. Copy the existing BPEL ZIP packages from <OLD_BPS_HOME>/repository/deployment/server/bpel to the newly created directory at <NEW_BPS_HOME>/repository/deployment/server/bpel.
   2. Copy BPEL super tenant extracted packages from <OLD_BPS_HOME>/repository/bpel/-1234/<extracted BPEL folder list> to the newly created directory at <NEW_BPS_HOME>/repository/bpel/-1234/<extracted BPEL folder list>.
      
      If you have tenants:
      
      1. Copy the existing BPEL ZIP packages from <OLD_BPS_HOME>/repository/tenants/<tenantID>/bpel to the newly created directory at <NEW_BPS_HOME>/repository/tenants/<tenantID>/bpel.
      2. Copy BPEL tenant extracted packages from <OLD_BPS_HOME>repository/bpel/<tenantID>/<extracted BPEL folder list> to the newly created directory in <NEW_BPS_HOME>/repository/bpel/<tenantID>/<extracted BPEL folder list>.
2. Migrate the Human Tasks packages. To do this:
   
   1. Copy humantask ZIP packages from <OLD_BPS_HOME>/repository/deployment/server/humantasks to the newly created directory at <NEW_BPS_HOME>/repository/deployment/server/humantasks.
      
      If you have tenants:
      
      1. Copy humantask ZIP packages from <OLD_BPS_HOME>/repository/tenants/<tenantID>/humantasks to the newly created directory at <NEW_BPS_HOME>/repository/tenants/<tenantID>/humantasks.

Database migration

1. Point to the existing userstore, registry and BPS databases (you may have one database for both User and Registry).
   
   1. To configure BPS data sources, use datasources.properties in <NEW_BPS_HOME>/repository/conf (default H2).
   2. To configure user and registry data sources, use master-datasources.xml in <NEW_BPS_HOME>/repository/conf/datasources (default JDBC/WSO2CarbonDB with H2)
   If you have used customized database names for the user and the registry, specify them in registry.xml and user-mgt.xml found in <NEW_BPS_HOME>/repository/conf (default JDBC/WSO2CarbonDB) and <NEW_BPS_HOME>/repository/conf (default JDBC/WSO2CarbonDB) respectively.
2. Open humantask.xml in <NEW_BPS_HOME>/repository/conf and change GenerateDdl to false. You can see the deployed humantask packages with their respective version in the console. A migration success message is printed once migration is successfully completed.
   <GenerateDdl>false</GenerateDdl>
3. Copy database connector jars to <NEW_BPS_HOME>/repository/components/lib. E.g., ojdbc6.jar for Oracle database

4. Run the registry migration SQL in both the registry db and user db (if you have registry and user databases point to same database then run this only once). 

   This step is only required if you are migrating from BPS 3.0.0 to BPS 3.2.0. You only need to run one of the SQL scripts named as mssql-migration.sql, mysql-migration.sql or oracle-migration.sql depending on your database.

5. Run the appropriate bps-migration script against the BPS persistence database (the database you have configured in the datasources.properties file). 
   
   • To migrate from BPS 3.0.0 to BPS 3.2.0, run the SQL script located in the dbscripts/bps/migration/300_320 folder. 
   • To migrate from BPS 3.1.0 to BPS 3.2.0, run the SQL script located in the dbscripts/bps/migration/310_320 folder.
     E.g., if you are using Oracle as the database and you are migrating from BPS 3.0.0 to BPS 3.2.0, use the oracle.sql file found in the dbscripts/bps/migration/300_320 directory.

Run task migration  tool

1. Once all above listed steps are completed, you can run the tool to convert existing human task deployment/instance data to BPS 3.2.0 compatible data. Now run taskmigrationtool.sh (taskmigrationtool.bat for Windows) found in the <NEW_BPS_HOME>/bin folder. You should be able to see deployed humantask packages with their respective version in the console. Migration success message is printed once the migration successfully finishes.
2. Start the BPS server.