Table of Contents

Search

  1. Preface
  2. Introduction to RulePoint
  3. Managing Your Account
  4. Using RulePoint User Interface
  5. User Management
  6. Topology Management
  7. Managing Hosts and Nodes
  8. Managing Application Services
  9. Managing System Services
  10. High Availability
  11. Managing Deployment
  12. Dashboard
  13. Object Import and Export
  14. Markers
  15. Log Management
  16. Licenses
  17. Error Codes
  18. Glossary

Administrator Guide

Administrator Guide

Deployment Overview

Deployment Overview

Deployment involves creating objects in design time and deploying these objects into the application services in run time, so that the configured application services begin processing events.
After you complete configuring all the RulePoint objects, you need to deploy the objects from the design-time to the run-time environment. RulePoint objects are of two types, primary objects and supporting objects. Primary objects, which include the source, responder, and rule, drive the execution of the run-time components. The supporting objects, which support the primary objects, include the topics, connections, analytics, watchlists, templates, and responses.
The following table shows the supporting objects for each primary object:
Primary objects
Supporting objects
Source
  • Topic
  • Connection
Responder
  • Response
  • Connection
Rule
  • Topic
  • Analytic
  • Watchlist
  • Response
  • Template
When you deploy the objects, the grid manager deploys the sources into the source controller, responders into the responder controller, while rules into the event processor. You must deploy only the primary objects. The grid manager deploys the supporting objects along with the primary objects. When you try to deploy an object, it will be evaluated and checked for validity. You can deploy the primary object only if it is valid. After you deploy a primary object, the state of that object and its supporting objects changes from Draft to Deployed state. You can choose to deploy the source, rules, and responders in bulk, or you can deploy each object individually.
The following figure shows the deployment of primary and supporting objects into the run-time environment:
You can view the current status of the object, such as Draft, Deployed, or Needs_Deployment on the user interface.

Deployment and Scalability

When you plan to scale your system to handle more events or rules, or increase the available memory of each application service, you need to configure more application services in your run-time environment. Add multiple instances of service controllers and event processors and distribute the deployment of rules, sources, and responders across these instances. If you configure a high-availability environment, you can deploy objects into primary and backup instances of the service controllers and event processors.
After successfully deploying objects from the design time to the run time, source controllers begin to fetch events, rule processors process events, and responder controllers dispatch alerts.

0 COMMENTS

We’d like to hear from you!