Automating the deployment process is commonly used a common practice in a production or and development environments. There are many tools exist to perform this task. Puppet is our recommended tool to perform deployment automation. You can find the necessary puppet modules which that are relevant to WSO2 CEP 4.0.0 here. You The following sections explain how you can refer/use these puppet modules when developing your own puppet modules for WSO2 CEP. Please find further details on this below.
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 necessary to install an apache storm Apache Storm cluster which that is required for the distributed deployment of CEP. It 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,:
Code Block | ||
---|---|---|
| ||
include ‘cep’ |
To install CEP in a specific role with default parameters, :
Code Block | ||
---|---|---|
| ||
include ‘cep:hanode’ include ‘cep:distributednode’ |
Storm Module
To install each server of a storm cluster with default parameters use, :
Code Block | ||
---|---|---|
| ||
include ‘storm::nimbus’ include ‘storm::supervisor’ include ‘storm::zookeeper’ include ‘storm::stormui’ |
...
cep : Installs and manages the CEP in standalone mode.
cep:hanode : Install Installs and configure configures the CEP as a worker in high availability(HA) mode.
- cep:distributednode : Install Installs and configure 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 only 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). |
| Mode The mode of the installation, following are the allowed values,. Possible values are as follows.
|
| Portoff set The port offset of the carbon server. |
| Flag to indicate if This indicates whether clustering is enabled or not. ( e.g. true), If the value is |
| Flag to indicate if deployment synchronization This indicates whether deployment synchronisation is enabled or not (. e.g. false), If the value is |
| The local member port to be use to be used in hazelcast the Hazelcast cluster. |
| Members The members of the hazelcast cluster, should specify the Hazelcast cluster. The hostname of each member with the local member port of each host should be specified. |
| The Hazelcast cluster membership schema. |
| Port The port used for syncing events among two nodes in CEP nodes in HA mode of CEP. |
| Port The port on which the HA management service is run when the CEP is deployed in HA mode of CEP. |
| Port The port on which the HA management service is run when the CEP is deployed in distributed mode of CEP. |
| CEP instances acting as managers in distributed mode of CEP. Hostname and the manager service port of each manager should be specified. |
| Flag to indicate if the This indicates whether the CEP instance is acting as a worker in HA or distributed mode of CEP. |
| Flag to indicate if the This indicates whether the CEP instance is acting as a manager in distributed mode of CEP. |
| Flag to indicate if the This indicates whether the CEP instance is acting as a presenter in HA or distributed mode of CEP. |
| Port The port which presenter instances use to receive events. |
| Connection The connection URL of the registry database (e.g., jdbc:mysql://192.168.57.170:3306/regdb?autoReconnect=true). |
| Username The username to be used to connect to the registry database. |
| Password to login to The password to log into the registry database. |
| Driver The driver class name to be used to connect to the registry database (e.g., com.mysql.jdbc.Driver). |
| Connection The connection URL of userstore database. |
| Username The username to be used to connect to the user store database. |
| Password to login to The password to log into the user store database. |
| Driver The driver class name to be used to connect to the user store database |
. |