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

Step 1. Perform Tasks for Deployed Sources

Step 1. Perform Tasks for Deployed Sources

After you deploy the sources and supporting objects, the features on the dashboard allow you to purge the run-time data, start or stop the source, or run the source once.
  1. On the
    Dashboard
    tab, click the
    Metrics
    view.
  2. Select the source controller where you have deployed the source and supporting objects.
    The
    Sources
    and
    Topics
    tabs deployed in that source controller appears on the right pane. You can view the functions on the lower-right pane.
    The following figure shows the deployed sources when you select the source controller in the
    Sources
    view of the contents panel:
     The 
					 Metrics view shows the sources deployed for the selected source controller. You can view the number of events on the lower-right panel. The 
					 Actions menu displays the tasks you can perform for the selected source.
  3. To purge the run-time data for the source, perform the following tasks:
    1. From the
      Actions
      menu on the lower-right pane, select
      Purge Object Metrics
      .
    2. Verify if all the run-time data such as aggregate count and the number of events resets to 0.
  4. To run the source once, perform the following tasks:
    1. From the
      Actions
      menu on the lower-right pane, select
      Run Once
      .
      A success message appears.
    2. Click
      OK
      .
    3. From the
      Actions
      menu on the upper-right pane, select
      Refresh
      , and verify that the number of events are updated.
  5. To stop the source, perform the following tasks:
    1. From the
      Actions
      menu on the lower-right pane, select
      Stop Source
      .
      A success message appears.
    2. Click
      OK
      .
    3. From the
      Actions
      menu on the upper-left pane, select
      Refresh
      .
    4. On the contents pane, verify if the state of the source changes to
      Stopped
      and it does not fetch any event data.
  6. To start the source that was stopped, perform the following tasks:
    1. From the
      Actions
      menu on the lower-right pane, select
      Start Source
      .
    2. A success message appears.
    3. Click
      OK
      .
    4. From the
      Actions
      menu on the upper-left pane, select
      Refresh
      .
      You can also click the
      Refresh
      icon on the upper-left pane.
    5. On the contents pane, verify that the state of the source changes to Started and it starts to fetch event data.

0 COMMENTS

We’d like to hear from you!