Preface
Introduction to Banking Use Case
- Banking Use Case Overview
- Banking Scenario
- Problem
- RulePoint Solution
- High-Level Overview of Banking Use Cases Covered
- Proposed Data Model
Before You Begin
- Before You Begin Overview
- Task 1. Create Database Tables
  - Table Definition Types in the Banking Database
- Task 2: Complete Prerequisites
- Task 3. Import Existing Samples
Alerting Customer Account Balance Details
- Alerting Customer Account Balance Details Overview
- Step 1. Create a Project
- Step 2. Create a Topic
- Step 3. Create an SQL Connection
- Step 4. Create an SQL Source
- Step 5. Create a Schedule
- Step 6. Create an RTAM Responder
- Step 7. Create an RTAM Response
- Step 8. Create a Wizard Rule
- Step 9. Deploy the Wizard Rule, Source, and Responder
- Step 10. View the RTAM Alert
Notifying Stock Price Changes
- Notifying Stock Price Changes Overview
- Step 1. Create a Topic
- Step 2. Create Web Service Connection
- Step 3. Create a Web Service Source
- Step 4. Create a Schedule
- Step 5. Create Email Connection
- Step 6. Create Email Responder
- Step 7. Create Email Response
- Step 8. Create Wizard Rule
- Step 9. Deploy the Rule, Source, and Responder
- Step 10. View the Email Response
Notifying Credit Card Transactions
- Notifying Credit Card Transactions Overview
- Step 1. Create a Topic
- Step 2. Create a JMS Connection
- Step 3. Create a JMS Source
- Step 4. Create a JMS Responder
- Step 5. Create a JMS Response
- Step 6. Create an Advanced Rule
- Step 7. Deploy the Rule, Source, and Responder
- Step 8. View the JMS Response
Notifying Free Health Checkups for Account Holders
- Notifying Free Health Checkups for Account Holders Overview
- Step 1. Create a Topic
- Step 2. Create a Source
- Step 3. Create a Schedule
- Step 4. Create a Watchlist
- Step 5. Create an Advanced Rule Using the Watchlist
- Step 6. Deploy the Rule, Source, and Responder
- Step 7. View the Email Response
Alerting the Bank Manager about Customers with a Particular Account Type in a City Overview
- Alerting the Bank Manager about Customers with a Particular Account Type in a City Overview
- Step 1. Create an Analytic
- Step 2. Create an Advanced Rule
- Step 3. Deploy the Rule, Source, and Responder
- Step 4. View the RTAM Alert
Alerting Customer Cash Withdrawal Details
- Alerting Customer Cash Withdrawal Details Overview
- Step 1. Create a Topic
- Step 2. Create an SQL Source
- Step 3. Create a Schedule
- Step 4. Create an Advanced Rule
- Step 5. Deploy the Rule, Source, and Responder
- Step 6. View the RTAM Alert
Alerting Stock Prices to DMAT Account Holders
- Alerting Stock Prices to DMAT Account Holders Overview
- Step 1. Create an Advanced Rule
- Step 2. Deploy the Rule, Source, and Responder
- Step 3. View the Email Alert
Checking Customer Cash Withdrawal Details for a Specified Duration
- Checking Customer Cash Withdrawal Details for a Specified Duration Overview
- Step 1. Create an Advanced Rule
- Step 2. Deploy the Rule, Source, and Responder
- Step 3. View RTAM Alert
Alerting Consequent Credit Card Transaction Rejections
- Alerting Consequent Credit Card Transaction Rejections Overview
- Step 1. Create an SQL Responder
- Step 2. Create an Advanced Rule
- Step 3. Deploy the Rule, Source, and Responder
- Step 4. View JMS Messages
- Step 5. View the RTAM Alert
Monitoring Balance Threshold of Customers
- Monitoring Balance Threshold of Customers Overview
- Step 1. Create a Template
- Step 2. Create a Template Rule
- Step 3. Create a Deployment Policy
- Step 4. Deploy the Rule, Source, and Responder
- Step 5. View the RTAM Alert
- Step 6. Upgrade a Template
- Step 7. Upgrade a Template to Include an Additional Parameter
- Step 8. Update the Rule
- Step 9. View the RTAM Alert
- Step 10. Revert the Template History
- Step 11. Create a Template from the Wizard Rule
- Step 12. Create a Template Rule
- Step 13. Deploy the Rule, Source, and Responder
- Step 14. View the RTAM Alert
Using the Dashboard Functions
- Using the Dashboard Functions Overview
- Step 1. Perform Tasks for Deployed Sources
- Step 2. Perform Tasks for Deployed Topics
- Step 3. Perform Tasks for Deployed Rules
- Step 4. Perform Tasks for Deployed Responses
- Step 5. Set the Time Line Filter
- Step 6. Purge an Application Service
- Step 7. Purge the Topology
- Step 8. View Errors
Managing Banking Users and Roles
- Managing Banking Users and Roles Overview
- Step 1. Create a Banking Role
- Step 2. Create a User
- Step 3. Log In to RulePoint with New User
- Step 4. Provide Project-Level Permissions
- Step 5. Edit the Role
Importing and Exporting Objects
- Importing and Exporting Objects Overview
- Step 1. Export Selected Objects
- Step 2. Import Objects
Setting Up High Availability
- Setting Up High Availability Overview
- Step 1. Add a Node
- Step 2. Create an Event Processor for High Availability
- Step 3. Verify the High Availability Settings
- Step 4. Update the Deployment Policy
- Step 5. Reassign a Rule
Using Custom Services
- Using Custom Services Overview
- Step 1. Create the JAR File
- Alert Server Downtime Using Custom Source Overview
- Notify Unexpected Bank Shutdown Using Custom Analytics Overview
Using the REST APIs
- Using the REST APIs Overview
- Step 1. Log In to RulePoint Using the REST Call
- Step 2. Get Project ID to Create Objects in a Project
- Step 3. Create a Topic
- Step 4. Create a JDBC Connection
- Step 5. Create an SQL Source
- Step 6. Add Dynamic Schedule to the Source
- Step 7. Create an RTAM Responder
- Step 9. Create an RTAM Response
- Step 10. Create an Advanced Rule
- Step 11. Deploy the Responder
- Step 12. Deploy the Rule
- Step 13. Deploy the Source
- Step 14. View the Objects in the Dashboard
Using Java Adapter for REST API
- Using Java Adapter For REST API Overview
- Step 1. Configure the BankingAdapaterDemo.java File
- Step 2. Run the Code

Banking Use Case Tutorial

6.2
- 6.1.2
- 6.1

Back Next

Proposed Data Model

The proposal of the data model for the use case consists of creating five basic tables in an Oracle environment, which simulates the type of customer data collected in the banking database.

You can also choose to use H2, IBM DB2, or Microsoft SQL server. The data includes personal and account information of the customer. For example, data consists of the name, date of birth, email ID, phone number, account number, type of account, total balance in the account, and information of the Relationship Manager assigned to the privileged customer.

The proposed model describes how the bank can use RulePoint to retrieve this information from the database and provide relevant services to the customer. The values acquired from the database are used in rule processing and sending out appropriate alerts.

Rename Saved Search

Table of Contents

Banking Use Case Tutorial

Banking Use Case Tutorial

Proposed Data Model

Proposed Data Model