com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Upgrading to the Latest BPS Version

Owned by Former user (Deleted)
Last updated: May 08, 2016 by Former user (Deleted)
3 min read

This topic describes how you can successfully migrate to WSO2 BPS 3.5.1 from the previous WSO2 BPS version (3.2.0). If you want to upgrade from earlier versions than 3.2.0, follow the instructions from here to migrate to version 3.2.0 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.2.0).

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 followings.
    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>.

Database migration

  1. Point the existing user, registry and BPS databases to the new version of BPS. 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 deployed humantask packages with version in console. 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, ojdbc7.jar for the Oracle database can be copied here.
  5. Run registry migration SQL in both registry db and user db (If you have registry and user databases point to same database then run only once).
  6. There are no changes required in the existing BPS databases. However, you must add a new databases for BPMN support introduced in this version of BPS. Do the following to achieve this.
    1. Create a new database to be used as the activity database for BPMN support.
    2. Run the corresponding database script for your DBMS found in <NEW_BPS_HOME>/repository/conf/bps/bpmn/create. You should execute all three scripts for that DBMS.
    3. Now specify this datasource in <NEW_BPS_HOME>/repository/conf/datasources/activiti-datasources.xml. Instructions on adding a datasource can be found in Managing Datasources.

Using Human Task Explorer Web Application

A web application for Human Task user operations was introduced with the 3.5.0 release. In order to use this feature,  include Human Task renderings in your task definitions. Users can still use their existing deployments (deployed in 3.2.0 or before) as it is, using the support provided in the carbon mgt-console.

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.