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 8. View Errors

Step 8. View Errors

When one object attempts to connect to another object that does not exist, the dashboard displays an error for that object.
  1. Click the
    Design
    tab, and edit the SQL source.
  2. Under
    Configuration
    , edit the SQL query to:
    select * from customer c,account_info a where c.cust_id=a.cust_id
    The following figure shows the
    Edit Source
    configurations in the
    Sources
    view of the
    Design
    tab:
  3. Click
    Save and Redeploy
    , and click
    OK
    to confirm.
    A message appears that redeployment is successful and if you want to preview the events.
  4. Click
    Cancel
    .
  5. Navigate to the dashboard and verify that the status of the source controller where you deployed the source shows the status as error.
    The following figure shows the error for the
    Customer Account Source
    on the dashboard for the source controller:
  6. To view the logs, perform one of the following tasks:
    • On the
      Dashboard
      tab, click the
      Logs
      view.
    The view displays the node, the log level, the component type, the message, and the log details. You can specify the start and end date to view the logs for that period.
    • Select the source with the error in the contents panel of the dashboard, click the
      State
      view in the
      Activity and Status
      section on the lower pane, and then click the
      Errors
      link.
    Verify that you can view the details, such as the source name, source type, timestamp, error code, and error message. On the right-hand side, you can view the error trace. After you complete viewing the details, close the
    Error Details
    window.
  7. On the
    Design
    tab, edit the SQL source to change the SQL query to:
    select * from customer_info c,account_info a where c.cust_id=a.cust_id
  8. Click
    Save and Redeploy
    .
  9. Navigate to the dashboard and verify that the Source Controller error flag is cleared and you can view the status as
    Last Errors
    on the
    State
    view on the lower-right pane.

0 COMMENTS

We’d like to hear from you!