Informatica RulePoint is a general purpose Complex Event Processing server. You can build an application on RulePoint to process large amounts of data in real time, detect anomalies, and take action. Informatica RulePoint provides a programming model to build such applications.
The RulePoint programming model consists of the following primary objects:
Sources. Sources connect to external systems to fetch data. The sources convert the fetched data into events. The events are published on topics.
Rules. Rules process events on topics. You can use the rule processing language, DRQL to create rules. The rule definition includes information about the topics and the number of events you want RulePoint to process, the conditions to check, and the response to generate when there is a deviation. As part of overall rule processing, the rule might call out functions called analytics. Rules also rely on watchlists that act as reference data sets during rule processing.
RulePoint also provides an easy way to create rules using templates. Templates are abstract rules that could become a rule when you provide all its parameters.
Responders. Responders dispatch alerts to external systems. When a rule condition is matched, the rule processing engine creates a response that is sent to the specified external system using a conduit called responder.
RulePoint consists of the following supporting objects that you reference in the primary objects:
Topics. Logically group events into a group. A topic describes the types and properties of events coming into the system.
Connections. Connect RulePoint objects, such as sources, analytics, and responders to the target database.
Response. Define how you want RulePoint to respond if the event matches the conditions defined in the rule.
Analytics. Analyze data within a system and implements a data processing function.
Watchlists. Contain the items that you store as a single object with a unique name that you define. The rule uses this name so that it can use the data stored in the object.
Templates. Enable users to easily create new rules. A template includes a rule statement that contains substitution parameters and instructional text to define those parameters.
For more information about the objects, see the
RulePoint User Guide
.
Proactive Monitoring for PowerCenter ships with a set of sources, topics, rules, templates, analytics, watchlists, and responders that are specific for the governance monitoring of PowerCenter.
Object States
Objects are in Draft state when you create the objects, you never deploy the objects, or when you undeploy objects. You need to deploy the objects to the application services for rule processing to begin. In the default topology, when you deploy the objects, the grid manager deploys the sources along with the supporting objects to the source controller, responders and supporting objects to the responder controller, and rules and supporting objects to the event processor. When you successfully deploy the primary objects and their supporting objects, the objects are in Deployed state. After you deploy the objects, the source controller begins to fetch events, the rule processor processes events, and the responder controller dispatches alerts.
If you need to change the object properties, undeploy the objects. When you undeploy primary objects, all secondary objects associated with the primary objects are also undeployed. After a successful undeploy, the state of the objects changes to Draft. After you complete the changes, you can deploy the objects again. When you edit and save the objects, the state of the objects changes to Needs_Deployment state. You need to deploy the objects again. For more information about deployment and the state of RulePoint objects, see the "Managing Deployment" chapter in the
RulePoint Administrator Guide
.
You can configure the application and system services in RulePoint for high availability, and reassign objects across the configured application services for processing. For more information, see the "High Availability" chapter in the