...
Application Requirements for Deployment:
Web-based pplications applications deployed for ISDA monitoring services can enjoy the expectation of a stable and monitored servlet container (currently tomcat) for their use. All applications must provide at least minimal self-reporting, however. All applications must support service of a standard page retreivable retrievable from <application-root>/indexping.jsp. This page's content must satisfy the following criteria:
...
Note that, if you just want operations staff to notice that your application has completely shut down, you as an application developer are welcome to make this page static content containing nothing more than "SUCCESS", but you are also welcome to make checks of application state and connectivity to any backend services you may utilize, so long as such checks do not impact the retreivability of ping.jsp well within the expected window. If your test process may take an extended period which could exceed the ping.jsp retreival window but still not represent an error condition, this must not impact the timely retreivability retrievability of ping.jsp; your application must instead make any required checks asynchronously with ping.jsp used only to report on those checks.
...
These are designed as supplementary tests which are capable of making end-user-like calls to the web applications, thus testing their entire range of function without simply relying on self-reporting. In a few cases these are also performable via Nagios, but generally speaking we use a separate server (isda-console1.mit.edu) with its own custom-coded test array.
IPS cannot set up end-to-end testing for every application we host or support.We have constrained this requirement to web services for which we have assumed primary support.
These are notes on easy HTTP-based tests which will perform a basic functionality check of not just an application but also any backend servers it's relying upon.
...