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

Deploying Streaming Applications

A Siddhi application (.siddhi file) can be deployed to run that on production. 

There are two modes deployment 

  • Standard deployment 
    Here we deploy Siddhi Apps in worker node (In Single node, Minimum HA Deployments)
  • Fully distributed deployment
    Here we deploy Siddhi Apps in manager node (Only in Fully Distributed Deployment) 

Refer below sections to get to know how to deploy on the above deployments:

Standard Deployment  

To start a worker node in single node mode, issue one of the following commands:

  • For Windows:   worker.bat
  • For Linux :   ./worker.sh

Siddhi applications can be deployed to the worker node by using one of the following methods:

  1. Dropping the .siddhi file in to the <SP_HOME>/wso2/worker/deployment/siddhi-files/ directory before or after starting the worker node.
  2. Sending a "POST" request to http://<host>:<port>/siddhi-apps with the Siddhi App included in the body of the request. Refer Stream Processor REST API Guide for more information on using WSO2 Strean Processor APIs.

When a Siddhi application is successfully deployed, a message similar to the following example appears in the startup logs.

To configure a Minimum HA deployment refer Minimum High Availability Deployment documentation.

Fully Distributed Deployment

To successfully set up, configure and run Siddhi applications in a fully distributed environment refer Fully Distributed Deployment documentation.



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