BMC SLM Engine overview
The main function of the Business Rule Interpretation Engine (BMC SLM Engine) is to interpret stored rules when they are created to construct the filters needed to implement these rules. The engine is written in C++ and runs continuously as a Microsoft Windows process or a UNIX daemon under armonitor, similar to the Assignment Engine and Approval Engine. The command line to start the engine is in the armonitor.cfg file in the conf subfolder of the AR System install folder. The BMC SLM engine starts when AR System starts.
Along with the BMC SLM engine, another the Application Dispatcher (arsvcdsp) engine acts as a "command controller" for all engines running under AR System. It receives commands queued in the Application Pending form and sends a signal to "wake up" the engine that needs to process each command, based on the category. The dispatcher is installed as part of AR System and works with any engine that runs under armonitor.
The SLM:RuleDefinition form is the main form that the BMC SLM engine references. It contains reference to each object needed to create a filter. The metadata needed by the engine to generate the structures needed to create a filter is stored in back-end forms.
The SLM:RuleDefinition form triggers building of these filters by issuing the following application command:
Application-Command BR-BRIE Create-Rule
BR-BRIE is the category of this command and Create-Rule is the command received by the engine. When a filter executes this command, an entry is created in the Application Pending form. This triggers the Application Dispatcher engine to evaluate this command and trigger the BMC SLM Engine to start processing.
The following image shows the back-end forms or metadata used by the BMC SLM engine and how it translates to an auto-generated filter. In BMC Remedy Administrator, each part of the auto-generated filter can be mapped to data in one of these back-end forms.
SLM Engine backend metadata objects
Click on the following image to expand it.