Table of Contents

Search

  1. Preface
  2. Introduction to Banking Use Case
  3. Before You Begin
  4. Alerting Customer Account Balance Details
  5. Notifying Stock Price Changes
  6. Notifying Credit Card Transactions
  7. Notifying Free Health Checkups for Account Holders
  8. Alerting the Bank Manager about Customers with a Particular Account Type in a City Overview
  9. Alerting Customer Cash Withdrawal Details
  10. Alerting Stock Prices to DMAT Account Holders
  11. Checking Customer Cash Withdrawal Details for a Specified Duration
  12. Alerting Consequent Credit Card Transaction Rejections
  13. Monitoring Balance Threshold of Customers
  14. Using the Dashboard Functions
  15. Managing Banking Users and Roles
  16. Importing and Exporting Objects
  17. Setting Up High Availability
  18. Using Custom Services
  19. Using the REST APIs
  20. Using Java Adapter for REST API

Banking Use Case Tutorial

Banking Use Case Tutorial

Setting Up High Availability Overview

Setting Up High Availability Overview

In this lesson, you learn how to enable high availability for the event processor.

Lesson Concepts

In a single node setup, all the service controllers and the rule engine run on a single node. in this lesson, you learn to add multiple nodes and assign the service controllers and rule engine to different nodes. You can run the service controllers and the event processor in a standalone mode or in a high availability mode. In standalone mode, if the node fails, the server takes some time to bring up the node, the controllers, and the event processor running on that node. In the meantime, events may be lost. This can also result in a loss of alerts or duplication of alerts.
A high availability enabled mode has a primary node and a backup node. The primary node takes care of all the evaluation and processing activities, while the backup node mimics the activity of the primary node. When the primary node goes down, the backup node becomes the primary node and processes events and rules. The primary node becomes the backup node and no events are lost.
In this lesson, you also learn to reassign rules to different event processors.

Lesson Objectives

In this lesson, you learn how to perform the following tasks:
  • Add a node.
  • Create a high availability event processor.
  • Verify the high availability settings.
  • Update the deployment policy.
  • Reassign a rule.

Lesson Prerequisite

Before you add a node and start the lesson, verify that you shut down the run-time instance in RulePoint.

0 COMMENTS

We’d like to hear from you!