Understanding major lines of the source code of a component surely helps one to understand how it works, but it may take tremendous efforta lot of effort. This page walks you through the source code of Holmes Rule Management, in the hope to

...

msinfo.setServiceName("holmes-rule-mgmt");
msinfo.setVersion("v1");
msinfo.setUrl("/api/holmes-rule-mgmt/v1");
msinfo.setProtocol("REST");
msinfo.setVisualRange("0|1");
msinfo.setEnable_ssl(true);

Transaction

...

ID Servlet Filter

Servlet filter TransactionIdFilter is setup to intercepts all HTTP requests. (In RuleActiveApp)

...

If the DcaeConfigurations has update (by checking its MD5 against the previous version), all existing rules are wiped out, and one a rule is generated for each rule in DcaeConfigurations. All the rule operations are done through the RESTful Rule Management REST APIs discussed in the next section.  (In DcaeConfigurationPolling.run())

...

1. Creating a Rule
   
   This service saves a rule into the database, and deploys it to the Drools rule engine if it is enabled. The HTTP request should be in such format:
   
   PUT /api/holmes-rule-mgmt/v1/rule
   {
   

   "ruleName": "Alarm Compression",
   "loopControlName": "Control Loop Name",
   "description"(optional): "This is the description of the rule.",
   "content": "template header\n ruleId\n package packageName...",
   "enabled": 0|1

   }
   
   This request is handled by RuleMgtResources.addCorrelationRule(), where the “content” in the HTTP body is used as a the rule. The rule is deployed to the Doorls rule engine via Holmes Engine Management REST API, and is saved to database table APLUS_RULE. On successfully deploying the rule, the rule ID is returned to the client. Note that if a rule with the same name already exists in database, the deployment will fail, and an error message "A rule with the same name already exists." is returned to the client.
   
   
2. Modifying a Rule
   
   This service updates an existing rule, and deploys it to the Drools engine if it is enabled. The HTTP request should be in such format:
   
   POST /api/holmes-rule-mgmt/v1/rule
   {
   

   “ruleId": "ruleid0937261",
   "loopControlName": "Control Loop Name",
   "description"(optional): "This is the description of the rule.",
   "content": "template header\n ruleId\n package packageName...",
   "enabled": 0|1

   }
   
   This request is handled by RuleMgtResources.updateCorrelationRule(), where the “content” in the HTTP body is used as a the new rule. The old rule is updated in database table APLUS_RULE, and is deployed to Doorls rule engine via Holmes Engine Management Restful API. On successfully updating the rule, the rule id is returned to the client.
   retrieved from database table APLUS_RULE using the rule ID. If the new rule is the same as the old, nothing will be done and the rule ID is returned to the client; else, the old rule is deleted from the Doorls rule engine, and the new rule is saved to database and is deployed to rule engine if it is enabled. Both rule operations (delete and deploy) are done through Holmes Engine Management REST API. At the end the rule ID is returned to the client.
   
   

3. Deleting a Rule 
   
   This service removes a rule from Holmes. The HTTP request should be in such format:
   
   DELETE  /api/holmes-rule-mgmt/v1/rule/{ruleid}
   
   where {ruleid} is the rule ID, which is used to delete the rule from database and the Doorls rule engine (via Holmes Engine Management REST API). 

4. Querying Rules

   This service queries rules using certain criteria. The HTTP request should be in such format:

   DELETE  /api/holmes-rule-mgmt/v1/rule/queryrequest={“ruleid": "ruleid0937261","rulename": "Alarm Compression","creator":"creator name","modifier":"modifier name","enabled":=0}
   
   where all the query parameters are optional. This request is handled by RuleMgtResources.getCorrelationRules(), where the query parameters are used to query the database for matching rules. In the SQL query, rulename is wildcat match, the rest is exact match.
   Here is a sample result returned to the client:

    {

   "correlationRules": [

   {

   "ruleId": "ruleid098271",
   "ruleName": "Alarm Compression",
   "description": "The description of the rule.",
   "content": "template header\n ruleId\n package packageName...",
   "createTime": 1484188925231,
   "creator": "admin",
   "updateTime": 1485188925231,
   "modifier": "user1",
   "enabled": 0

   }

   ],

   "totalCount": 1

   }

   Deleting a Rule 

   Note that this service does not query the rule engine, all information is from database.

   
   
   

   rulemgt/src/main/resources/swagger.json is the OpenAPI Specification (OAS) file that describes all the above APIs. This wiki page has the complete spec of these REST APIs.