You can disable selected BAM components when starting the server . Note that this method is a workaround to using an actual server profile. We plan to provide this facility through server profiles in a future release. In the meantime, you can use this workaround.using start-up parameters as follows.
| Command (on Linux) | Description |
|---|---|
sh <PRODUCT_HOME>/bin/wso2server.sh -Ddisable.analytics=true | Used to disable the analytics-related components. If you run this command to start BAM on a particular node, the node does not join the task execution. You use this property to start a node that works as a receiver. |
sh <PRODUCT_HOME>/bin/wso2server.sh -Ddisable.receiver=true | Used to disable the receiver-related components. If you run this command, the thrift server does not start and you do not need to open 7611+<BAM_PORT_OFFSET> and 7711+<BAM_PORT_OFFSET> ports. You use this property to start a node that works as an analyzer. |
sh <PRODUCT_HOME>\bin\wso2server.sh -Ddisable.cassandra.server.startup=true | Used to disable running Cassandra, which is bundled with BAM by default. In this case, you are recommended to point to an external Cassandra cluster. |
| Info |
|---|
You can use multiple parameter values to disable multiple BAM components simultaneously. For example, you can use the following command to simultaneously disable both the analytics-related and receiver-related components, which are described above. sh |