This use-case describes the means to test the availability and authenticity of a deployed web service.
The test should be generally accessible (local or Internet), provide a result with or without authentication as well as with or without an existing authorization. Also, the test should be available on all listeners, in all protocols/dialects, and with all transport security options.
The test should not be rely on any particular eventing model. The test should not dilute metrics. The requested operation should always respond, with exception for avoiding denial of service.
High-level Story (Abstract)
A college or university deploys a web service such as the Academic History Web Service and wants to proactively detect problems by testing the service.
After deploying and testing the web service, the appropriate administrator of an organization's monitoring tools configures that tool to invoke a Status request on the service at a desired interval.
If the invocation fails, that failure is reported by the monitoring tool.
A successful invocation includes the status (success or failure) of invocation attributes including authentication and authorization (if specific metrics were requested) as well as dynamic/negotiated details (e.g. transport security attributes).
The metrics are compared with threshold values set in the monitoring tool, and the appropriate administrators are alerted if thresholds are exceeded.
- The service is deployed with a SOAP endpoint using SSL.
- The monitor is configured to invoke the 'Status' operation, with an authentication token for 'operator'.
- The service is responding, so the Status invocation succeeds. The reply include various name-value pairs.
Rewrite the detailed story with specifics, when available.