Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 <WSO2SPOpen the deployment.yaml file in the <WSO2SP_HOME>/conf/dashboard directory.
  2. Deployment configurations for the Business Rules Manager are specified

    under wso2

    under wso2.business.rules.manager

    . Provide the URL(s) of worker node(s) that is/are available to deploy SiddhiApps, under deployment_configs - in the format <HOSTunder deployment_configs in the <HOST_NAME>:<PORT><PORT> format.

    Code Block
    languagepowershell
    deployment_configs:
    	- <NODE1_HOST_NAME>:<NODE1_PORT>
    	  <NODE2_HOST_NAME>:<NODE2_PORT>
    

    Eg:

    Code Block
    languagepowershell
    deployment_configs:
    	- localhost:9090
    	  10.100.4.140:9090
  3. 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 noderequired rule templates under each node. This results in Siddhi applications created out of the specifed rule templates being deployed in the relevant nodes.

    Code Block
    languagepowershell
    deployment_configs:
    	- <NODE1_HOST_NAME>:<NODE1_PORT>:
    		- ruleTemplate1_UUID
    		- ruleTemplate2_UUID
    		- ruleTemplate3_UUID

    Eg:e.g.,

    Code Block
    languagepowershell
    deployment_configs:
    	- localhost:9090:
    	   - sweet-production-kpi-analysis
           - stock-exchange-input
           - stock-exchange-output
  4. A rule template can be configured under more than one node, as long as its instanceCount is manyIf required, you can enter a specific rule template under multiple nodes as shown below.

    Info

    Before entering a specific rule template under multiple node, make sure that you have selected Many for the Instance Count field of the template. For more information, see Creating a Business Rule Template.

    Code Block
    languagepowershell
    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:e.g.,

    Code Block
    languagepowershell
    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 Note that the rule template with UUID the sweet-production-kpi-analysis analysis UUIDhas been configured under two worker nodes. So thatAs indicated by this, if a business rule is derived from sweet-production-kpi-analysis, the belonging SiddhiApps will be Siddhi Applications created from it are deployed in both the nodes.

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

    Code Block
    languagepowershell
    username: admin
    password: admin


    The complete deployment configuration for Business Rules will look like the followinglooks as follows.

    Code Block
    languagepowershell
    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