Page History
...
| Product | Versions | Description | Released Versions | Upcoming Versions | |
|---|---|---|---|---|---|
| API Manager | 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0 and , 1.9.1, 1.10.0 and 2.0.0 | Requires configurations in addition to the standard worker/manager cluster, particularly if distributed mode is used. See here for the additional configurations. Worker/Manager separation is usually done for the Gateway, but can be done for the Publisher and Store as well. | 1.5.0, 1.6.0, 1.7.0, 1.8.0 and , 1.9.0, 1.9.1, 1.10.0 and 2.0.0 | NA | |
Application Server | 5.2.0, 5.2.1 and 5.3.0 | Standard worker/manager separation. | 5.2.0 and 0, 5.2.1 and 5.3.0 | NA | |
| Business Process Server | 3.1.0, 3.2.0, 3.5.0, 3.5.1 and 3.56.0 | While clustering BPS is relevant to this topic, it requires configurations in addition to the standard worker/manager cluster. See here for the additional configurations. | 3.1.0 and , 3.2.0, 3.5.0, 3.5.1 and 3.6.0 | NA | |
| Business Rules Server | 2.1.0 | Standard worker/manager separation. | 2.1.0 | NA | |
| Data Services Server | 3.1.0, 3.1.1, 3.2.0, 3.2.1, 3.2.2, 3.5.0 and 3.35.01 | Standard worker/manager separation. | 3.1.0, 3.1.1, 3.2.0, 3.2.1 and , 3.2.2, 3.5.0 and 3. | 05.1 | NA |
| Enterprise Service Bus | 4.8.0, 4.8.1 and , 4.9.0 and 5.0.0 | Standard worker/manager separation with some additional ESB-specific configurations. | 4.8.0 and , 4.8.1, 4.9.0 and 5.0.0 | 5.1.0 | |
| Task Server | 1.1.0 | Standard worker/manager separation. See here for additional steps needed. | 1.1.0 | NA |
The following WSO2 products do NOT commonly use worker/manager separation in a clustered environment.
| Product | Versions | Description | Released Versions | Upcoming Versions | |
|---|---|---|---|---|---|
| Business Activity Monitor | 2.4.0, 2.4.1 and 2.5.0 | BAM does not have a concept of worker/manager separation, but the Analyzer nodes require clustering. See here for BAM clustering. | 2.4.0, 2.4.1 and 2.5.0 | NA | |
| Complex Event Processor | 3.0.0, 3.1.0, 4.0.0, 4.1.0 and 4.02.0 | CEP does not use a standard worker/manager cluster in a typical production environment. | 3.0.0 and , 3.1.0, 4.0.0, 4.1.0 and 4.2.0 | NA | |
| Data Analytics Server | 3.0.0, 3.0.1 and 3.1.0 | DAS does not use a standard worker/manager cluster in a typical production environment. | NA3.0.0, 3.0.1 and 3.1.0 | NA | |
| Enterprise Store | 2.0.0 and 2.1.0 | ES does not support worker/manager separation. | NA2.0.0 and 2.1.0 | NA | |
| Governance Registry | 4.6.0, 5.0.0, 5.1.0, 5.2.0 and 5.03.0 | No concept of worker/manager separation. See here for clustering Governance Registry. | 4.6.0 | 5.0.0.0, 5.0.0, 5.0.1, 5.1.0, 5.2.0 and 5.3.0 | NA |
| Identity Server | 4.5.0, 4.6.0, 5.0.0, 5.1.0 and 5.12.0 | Worker/manager separation is not possible in the Identity Server and is not used as a typical scenario when deploying the Identity Server. See here for clustering the Identity Server. | 4.5.0, 4.6.0, 5.0.0, 5.1.0 and 5.02.0 | 5.13.0 | |
| Message Broker | 2.2.0 and 3.0.0 | MB does not use a standard worker/manager cluster in a production environment. | 2.2.0 and 3.0.0 | NA |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
This worker/manager deployment setup provides proper separation of concerns between a Carbon-based product's UI components, management console, and related functionality with its internal framework serving requests to deployment artifacts. Typically, the management nodes are in read-write mode and authorized to add new artifacts or make configuration changes, whereas the worker nodes are in read-only mode, authorized only to deploy artifacts and read configurations. This deployment model provides improved security, since security since its management nodes can be set up behind an internal firewall and only exposed to internal clients while only worker nodes can be exposed externally. Also, since the user interface is not loaded onto 'worker' nodes, the deployment model is more efficient in memory utilization.
...
Overview
Content Tools
Activity