Page Comparison

...

Tests  that alarms can be generated and viewed correctly through the Alarm webgui. Specific alarms are tested in the tests cases related to the concrete specific functionalities.

Basic alarm

1. Delete a file on a pillar.
2. Run an integity integrity check for missing files.
   •  A new alarm should be generated by the integrity service, indicating that a integrity problem has been detected. 
     
     

...

Tests that alarms are stored on the messagebus persistent and durable (

•   Stop  Ensure the alarm service .is running,  and  that it is a durable subscriber Generate a
  • ssh bm_webserviceand run tomcat-init.sh stop and then webservice@int-bitmag-02.kb.dk and run tomcat-init.sh start .
  • This should cause a durable subscriber to have been registered.
•  Generate a alarm (run a integrity check on a  inconsistent collection).
•  Start the alarm service.
  
  • The alarm should be received on the alarm service.
•  Stop the alarm service.
• • if it isn't running
  • The alarm service should be present under the active durable subscribers (can be checked at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp)
•   Shutdown the alarm service
  
  • Stop the service with alarm-service-it.sh stop
    • This will stop the webclient, remove the alarm service from the tomcat90/webapps/ folder and restart the webclient tomcat server
  • Checked that the alarm service is present under offline durable subscribers at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp
•  Generate an alarm (run a integrity check on a  inconsistent collection).
•  Restart the message bus.
• • Note the time of the alarm, and any other details to be able to identify it again.
•  Start the alarm service again
  • Using alarm-service-it.
  • The alarm should be received on the alarm servicesh start
  • When the webclient is restarted, it will automatically perform some checks that will cause alarms. This is where you need to use the details about the alarm you triggered to check that the alarm is present.