Skip to content

Notification Service_148865606

Jump to bottom
nxi edited this page Apr 9, 2015 · 1 revision
Created by Tony Lam, last modified on Jul 06, 2010

Introduction

The notification framework is part of the GumTree core services that provides a centralised gateway for developers to push notification to the users.

Design

Requirement

There are a number of user requests on making GumTree to notify users with current experiment status and unexpected error. The notification can also be viewed as alert and broadcast, depending on its context.
  • Notification can be given with priority
  • Duplicated notification can be discarded (configurable)
  • All notifications should be persisted for audit trail
  • Notification can be sent to different places:
    • Email (SMTP)
    • SMS
    • Web services (Twitter, Facebook)
    • Social communication protocols (MSN, Jabber, Skype)
    • GumTree server (as broadcast system)
    • Workbench (alert popup, tray balloon help)
    • Twitter
    • Growl (Mac only) 
  • Client can send notification directly using the notification service, or indirectly by publishing an event and let a monitor to turn the event into a notification
  • Configurable via Eclipse preference page and JMX

Use Cases

SICS reconnection
SICS client reports the lost of connection, and ask the user to reconnect.
Workflow current status
The Quokka workflow broadcast its current status to other workbench components and the web status dashboard. The workflow can also send completion notice to users via email or SMS.
Reactor tripped alert
GumTree notifies users via SMS or email for reactor trip while it is running an experiment.
Document generated by Confluence on Apr 01, 2015 00:11

Home | Developer Guide | Copyright © 2013 ANSTO

Clone this wiki locally