WSO2 Business Process Server as a Service

Implementation Overview

WSO2 Business Process Server (BPS) 3.5.0 is provided as a service on WSO2 Private PaaS 4.1.0. This is implemented by creating the following:

• Template module

  The template module configures the product in runtime, with a set of key value pairs known as the configuration parameters.

• Cartridge agent plugin

  The cartridge agent plugin, sets the runtime configuration parameters such as hostnames, IP addresses of dependent clusters, dynamic proxy ports and many more.

• Docker image

  The Docker image is built by packaging the following components:

  • Cartridge agent

  • Product distribution

  • Template module

  • Configurator

  • Java runtime

• Puppet module

  The puppet module includes the same set of component as in the Docker image. In the puppet image the template module is used to configure automation.

Deploying WSO2 BPS as a Service

Deploy WSO2 BPS as a service using one of the following methods. 

• Deploy the application on Private PaaS when running on a Virtual Machine.
• Deploy the application on Private PaaS when running on Kubernetes.

Deployment Architecture

The diagram illustrates the deployment architecture of WSO2 BPS on Private PaaS. In the deployment, two different Private PaaS clusters will be created for the BPS manager and worker. These clusters can be scaled independently.

Template Module

The WSO2 BPS 3.5.0 template module provides a set of templates that is used to configure the BPS with the Configurator.

Cartridge Agent Plugin

The Server configurations are automated through the cartridge agent plugin, which was implemented for WSO2 BPS 3.5.0.

The plugin configures the following and many more:

• Server hostname
• Cluster discovery parameters
• Proxy ports