Versions Compared

Old Version 32

changes.mady.by.user Former user

Saved on

compared with

New Version 33

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

For information on understanding the general flow of WSO2 CEP samples, see WSO2 CEP Samples. The following sections explain the generic setup instructions to execute the samples.

...

SampleRequirements
All samples
JMS related samples

The JMS samples are explained to be tried out using following JMS providers

MQTT related samples

The MQTT samples are explained to be tried out using following MQTT-supported servers

Kafka related samples

The Kafka samples are explained to be tried out using following Kafka Broker versions

For more information on the prerequisites required for the email related samples, see Setting up Email samples		Email related samples

WebSocket related samples

Java Development Kit / JRE version 1.7.*

Apache Storm related samples

Apache Storm version 0.9.3 or later (to run Storm samples.)

...

It is recommended to use WSO2 CEP in the sample mode only to run the samples, because the server has limited functionality in the sample mode. Thereby, the CEP dashboard, WebSocket local receiver, WebSocket local publisher, and the UI publisher applications are not available when running CEP in the sample mode.

.

In the normal mode the <CEP_HOME>/bin/wso2server.bat or  <CEP_HOME>/bin/wso2server.sh  script starts an instance of the CEP using the configuration files  in <CEP_HOME>/repository/deployment/server directory and any sample configurations passed in as -sn <n> is ignored.

Excerpt

To start the CEP with a sample configuration, run the following command with -sn <n>, where <n> denotes the number assigned to the sample.

Code Block
On Linux:	./wso2cep-samples.sh -sn <n>
On Windows:	wso2cep-samples.bat -sn <n>

For example, to start the CEP with the configuration of sample 0101, run the following command inside <CEP_HOME>/bin directory:

Code Block
On Linux: 	./wso2cep-samples.sh -sn 0101 
On Windows:	wso2cep-samples.bat -sn 0101
However, if you need these capabilities in the sample mode, copy the <CEP_HOME>/repository/deployment/server/webapps/ and <CEP_HOME>/repository/deployment/server/jaggeryapps/ directories to the <CEP_HOME>/samples/artifacts/<SAMPLE_NUMBER>/ directory

The <CEP_HOME>/samples/artifacts directory contains the sample configurations of CEP. Each configuration is inside a sub directory by the name of the sample numbered <n>. For example, the cep artefacts for sample 0101 is inside<CEP_HOME>/samples/artifacts/0101 directory.

Note
Info

These configurations on running the samples do the following:

  • Create <CEP_HOME>/repository/conf/data-bridge/stream-definitions.xml file, which is used to create the stream definitions for the sample.

  • Point the default Axis2 repo to <CEP_HOME>/sample/artifacts/<SAMPLE_NUMBER>/ directory. (<CEP_HOME>/repository/deployment/server/ directory is used as the default Axis2 repo.)

...

Info
Previous Apache ActiveMQ versions may not contain SLF4J related files in the client JAR. Therefore, if you get an error, add  SLF4J related JAR file to<CEP_HOME>/samples/lib/ directory of the samples.

...

Before you run MQTT samples, set up and start a MQTT-supported server. Configure MQTT sample clients by copying relevant MQTT client libraries to <CEP_HOME>/samples/lib folder as mentioned below.

...

Before you run Kafka samples, set up and start a Kafka broker. Configure Kafka sample clients by copying relevant Kafka client libraries to <CEP_HOME>/samples/lib folder as mentioned below.

...