This documentation is for WSO2 Complex Event Processor 4.1.0. View documentation for the latest release.
||
Skip to end of metadata
Go to start of metadata

Automating the deployment process is a common practice in production and development environments. There are many tools to perform this task. Puppet is our recommended tool to perform deployment automation. You can find the necessary puppet modules that are relevant to WSO2 CEP 4.0.0 here. The following sections explain how you can refer/use these puppet modules when developing your own puppet modules for WSO2 CEP.

WSO2 CEP Puppet Modules

These puppet modules can be used to install WSO2 CEP in all its deployment modes (i.e. standalone mode, high availability mode and distributed mode). Also, it contains the necessary modules to install an Apache Storm cluster that is required for the distributed deployment of CEP. It also has enabled deployment of 3 main deployment patterns of wso2 CEP easily using Hiera to store deployment parameters.

Setup

CEP Module

To install CEP in its normal mode(i.e. standalone mode) with default parameters:

include ‘cep’ 

To install CEP in a specific role with default parameters:

include ‘cep:hanode’
include ‘cep:distributednode’
Storm Module

To install each server of a storm cluster with default parameters:

include ‘storm::nimbus’
include ‘storm::supervisor’
include ‘storm::zookeeper’
include ‘storm::stormui’ 


References

Classes 
  • cep : Installs and manages the CEP in standalone mode.

  • cep:hanode : Installs and configures the CEP as a worker in high availability(HA) mode.

  • cep:distributednode : Installs and configures the CEP as a worker or a manager in distributed mode.
Parameters

 

Parameter

Description

version

The version of the WSO2 CEP server.  These scripts can only be used for version 4.0.0 onwards. (e.g. 4.0.0)

owner

The owner of the CEP installation folder (e.g. root).

group

The group of the CEP installation folder (e.g. root).

maintenance_mode

The mode of the installation. Possible values are as follows.

  • refresh: Stops the server if running and restarts it.
  • new: Deletes the existing installation, and redeploys and starts the server.
  • zero: Downloads a fresh copy of the wso2 CEP pack and perform a fresh deployment.

offset

The port offset of the carbon server.

clustering

This indicates whether clustering is enabled or not. e.g., If the value is true, clustering is enabled.

depsync

This indicates whether deployment synchronisation is enabled or not. e.g., If the value is false, deployment synchronisation is disabled.

local_member_port

The  local member port to be used in the Hazelcast cluster.

members

The members of the  Hazelcast cluster. The hostname of each member with the local member port of each host should be specified.

membership_scheme

The Hazelcast cluster membership schema.

ha_eventsynch_port

The port used for syncing events among two CEP nodes in HA mode.

ha_mgt_port

The port on which the HA management service is run when the CEP is deployed in HA mode.

manager_port

The port on which the HA management service is run when the CEP is deployed in distributed mode.

managers

CEP instances acting as managers in distributed mode. Hostname and the manager service port of each manager should be specified.

worker

This indicates whether the CEP instance is acting as a worker in HA or distributed mode.

manager

This indicates whether the CEP instance is acting as a manager in distributed mode.

presenter

This indicates whether the CEP instance is acting as a presenter in HA or distributed mode.

presenter_port

The port which presenter instances use to receive events.

registry_db_connection_url

The connection URL of the registry database (e.g., jdbc:mysql://192.168.57.170:3306/regdb?autoReconnect=true).

registry_db_user

The username to be used to connect to the registry database.

registry_db_password

The password to log into the registry database.

registry_db_driver_name

The driver class name to be used to connect to the registry database (e.g., com.mysql.jdbc.Driver).

userstore_db_connection_url

The connection URL of userstore database.

userstore_db_user

The username to be used to connect to the user store database.

userstore_db_password

The password to log into the user store database.

userstore_db_driver_name

The driver class name to be used to connect to the user store database.

  • No labels