WSO2 Stream Processor Profiles

WSO2 Stream Processor has four profiles in order to run different functions. When you start and run any of these profiles, you are running only the subset of Stream Processor features that are specific to that profile. Some use cases supported require you to run two or more of these profiles in parallel.

The four profiles are as follows.

Editor profile

Purpose	This runs the developer environment where the following can be carried out: Creating Siddhi applications/Siddhi application templates. Testing and debugging Siddhi applications to determine whether they are ready to be used in a production environment. For more information about creating and testing Siddhi applications, see Understanding the Development Environment. For more information about creating business templates, see Creating a Business Rule Template.
Starting and running the profile	Navigate to the `<SP_HOME>/bin` directory and issue one of the following commands: For Windows: `editor.bat` For Linux: `./editor.sh`
Deployment	To deploy a Siddhi application in this profile, place the relevant `<SIDDHI_APPLICATION_NAME>.siddhi` file in the `<SP_HOME>/wso2/editor/deployment/workspace` directory. The Siddhi files created and saved via the Stream Processor Studio are stored in the `<SP_HOME>/wso2/editor/deployment/workspace` directory by default.
Tools shipped	When you start WSO2 SP in the editor profile, the URLs to access the following tools appear in the start-up logs. Stream Processor Studio Template Editor

Dashboard profile

Purpose	This profile is available for the following purposes: Visualizing processed data via dashboards. For more information, see Visualizing Data. Deploying and managing business templates and business rules. For more information, see Creating Business Rules. Running the Status Dashboard to monitor the health of your WSO2 SP deployment. For more information, see Monitoring Stream Processor.
Starting and running the profile	Navigate to the `<SP_HOME>/bin` directory and issue one of the following commands: For Windows: `dashboard.bat` For Linux: `./dashboard.sh`
Deployment	The following deployments are possible: Custom widgets can be deployed by placing the compiled react code in the `<SP_HOME>/wso2/dashboard/deployment/web-ui-apps/portal/extensions/widgets` directory. For more information, see Creating Custom Widgets. Business rules that need to deployed can be added in the `<SP_HOME>/wso2/dashboard/resources/business-rules` directory. For more information, see Managing Business Rules - Deploying Business Rules.
Tools	When you start WSO2 SP in the dashboard profile, the URLs to access the following tools appear in the start-up logs. Dashboard Portal Business Rules Manager Status Dashboard

Worker profile

Purpose This profile runs the Siddhi applications in a production environment when WSO2 SP is deployed in a single node or as a minimum HA cluster. For more information, see Deploying Streaming Applications.

Starting and running the profile

Navigate to the <SP_HOME>/bin directory and issue one of the following commands:

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

Deployment To deploy a Siddhi application in this profile, place the relevant <SIDDHI_APPLICATION_NAME>.siddhi in the <SP_HOME>/wso2/worker/deployment/siddhi-files directory.

Manager profile

Purpose This profile runs the distributed Siddhi applications in a production environment when WSO2 SP is set up as a fully distributed deployment. For more information, see Fully Distributed Deployment.

Starting and running the profile

Navigate to the <SP_HOME>/bin directory and issue one of the following commands:

For Windows: manager.bat
For Linux: ./manager.sh

Deployment To deploy a Siddhi application in this profile, place the relevant <SIDDHI_APPLICATION_NAME>.siddhi file in the <SP_HOME>/wso2/manager/deployment/siddhi-files directory.