Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


WSO2 Business Rules Manager uses ruleTemplates within templateGroups, to derive business rules from. Each ruleTemplate will have a UUID - that is used to uniquely identify itself. When a ruleTemplate is specified under a worker node; SiddhiApps derived in business rules created out of that ruleTemplate will be deployed in the specified worker node.

  1. Go to the deployment.yaml file under <WSO2SP_HOME>/conf/dashboard
  2. Deployment configurations for the Business Rules Manager are specified under wso2.business.rules.manager
  3. Provide the URL(s) of worker node(s) that is/are available to deploy SiddhiApps, under deployment_configs - in the format <HOST_NAME>:<PORT>

    deployment_configs:
    	- <NODE1_HOST_NAME>:<NODE1_PORT>
    	  <NODE2_HOST_NAME>:<NODE2_PORT>
    

    Eg:

    deployment_configs:
    	- localhost:9090
    	  10.100.4.140:9090
  4. List down the UUIDs of required ruleTemplates under each node such that: when a ruleTemplate is specified under a worker node, SiddhiApps derived in the business rules created out of that ruleTemplate will be deployed in that specific node.

    deployment_configs:
    	- <NODE1_HOST_NAME>:<NODE1_PORT>:
    		- ruleTemplate1_UUID
    		- ruleTemplate2_UUID
    		- ruleTemplate3_UUID

    Eg:

    deployment_configs:
    	- localhost:9090:
    	   - sweet-production-kpi-analysis
           - stock-exchange-input
           - stock-exchange-output
  5. A rule template can be configured under more than one node, as long as its instanceCount is many

    deployment_configs:
    	- <NODE1_HOST_NAME>:<NODE1_PORT>:
    		- ruleTemplate1_UUID
    		- ruleTemplate2_UUID
    		- ruleTemplate3_UUID
    	  <NODE2_HOST_NAME>:<NODE2_PORT>:
    		- ruleTemplate1_UUID
    		- ruleTemplate3_UUID
    	  <NODE3_HOST_NAME>:<NODE3_PORT>:
    		- ruleTemplate2_UUID
    		- ruleTemplate3_UUID
    		- ruleTemplate4_UUID

    Eg:

    deployment_configs:
    	- localhost:9090:
    		- sweet-production-kpi-analysis
    		- stock-exchange-input
    		- stock-exchange-output
    	  10.100.40.169:9090:
    		- identifying-continuous-production-decrease
    		- sweet-production-kpi-analysis

    Notice that the rule template with UUID sweet-production-kpi-analysis has been configured under two worker nodes. So that, if a business rule is derived from sweet-production-kpi-analysis, the belonging SiddhiApps will be deployed in both the nodes.

  6. Specify the username & password, that are common for all the worker nodes

    username: admin
    password: admin
  7. The complete deployment configuration for Business Rules will look like the following

    wso2.business.rules.manager:
    	datasource: BUSINESS_RULES_DB
    	deployment_configs:
    		- localhost:9090:
    			- stock-data-analysis
    			- stock-exchange-input
    			- stock-exchange-output
    			- identifying-continuous-production-decrease
    			- sweet-production-kpi-analysis
     	username: admin
     	password: admin








  • No labels