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

Task 1. Create Database Tables

Task 1. Create Database Tables

You can create tables in IBM DB2, Microsoft SQL Server, or Oracle. In this lesson, you create tables in the Oracle database under the user rulepoint. You can make changes as and when the implementation progresses.
  1. Run the
    ddl <database>_cust_acc.sql
    script available in the following directory:
    for example, for Oracle, run
    ddl oracle_cust_acc.sql
    from
    <
    RULEPOINT_HOME
    >/samples/Banking/db/Oracle
  2. Open command prompt, navigate to
    <
    RULEPOINT_HOME
    >/samples/Banking/db/<
    database
    >
    , and log in to the database as RulePoint user.
  3. Open the
    ddl
    file, and update the email IDs with the email IDs of your organisation.
    The ddls contain the sample email ID.
  4. To see the email response in the banking use cases, edit the email IDs in the script, and then run the following script:
    cd <
    RULEPOINT_HOME
    >/samples/Banking/db/<
    database
    > sqlplus rulepoint/rulepoint@infaorcl @oracle_cust_acc.sql commit;
  5. Verify if the following proposed tables are created, so that you can implement the banking use case:
    • CUSTOMER_INFO
    • ACCOUNT_INFO
    • TRANSACTION_INFO
    • PREFERRED_INFO
    • RELATIONSHIP_MANAGER_INFO

0 COMMENTS

We’d like to hear from you!