How are Spectrum Server alarms published to the OneClick client?

book

Article ID: 143091

calendar_today

Updated On:

Products

CA eHealth CA Spectrum

Issue/Introduction

Given that there are two components in the chain (Spectrum Server <- -> OC Web Server and OC Web Server <--> OC client), how are Spectrum Server alarms published to the OneClick client?

Are the mechanisms the same or different, is it a publish or pull method, and what is the frequency?

Environment

Release : All Releases

Component : Spectrum Core / SpectroSERVER

Resolution

  • The SS <-> Tomcat connection is persistent over Corba.
  • The OC Client <-> One Click Web Server connection is done at a 10 second poll from OC Client to OC Web Server.
  • Tomcat on the OC Web Server has a notification queue that batches alarm updates from SpectroSERVER(s). This queue is operating on a 10 second interval.
  • If an alarm is placed into the Tomcat notification queue and it clears before the OC Client processes it then it is removed.
  • If an alarm became ready on Tomcat just after the OC Client polled the web server, then the alarm would only be sent on the NEXT client poll so the alarm would be “delayed” essentially by 10 seconds.
  • In the worst case scenario an alarm sent by a SpectroSERVER could in theory take 20 seconds to arrive on the client (from the time Tomcat received it).
  • The best case with some lucky timing alarms can be seen in as little as 1 second.