...
The following URL is used to monitor all ISDA web services and web servers:
https://isda-ws3.mit.edu/wsUtilities/wsping.jsp
The wsping.jsp is designed to send a transaction to each of the web services on all of the ISDA production web service servers. Each transaction will test the connectivity to a specific web service and to any associated back-end service that is being used by the web service. This includes:
User Authorization Web Service: tests connectivity to the Roles database via the User Authorization web service (uaws).
MITID Web Service: tests connectivity to the MIT ID database via the MIT ID web service (mitidws).
Geocodes Web Service: tests connectivity to the geocodes web service (geows) located at http://www.geonames.org via the geocodes web service (geows).
II. Detecting a web service failure
Once you have executed https://isda-ws3.mit.edu/wsUtilities/wsping.jsp, if the reply contains either of the words failed or exception, then at least one of the web services on at least one of the web servers has failed.
...
1) To determine the server and web service that has failed, open a web browser and go to the URL:
https://isda-ws3.mit.edu/wsUtilities/wsping.jsp
Be patient as it may take several minutes before the results are displayed.
...
4) After apache and tomcat has been restarted, open a new browser and go to:
https://isda-ws3.mit.edu/wsUtilities/wsping.jsp
If a failure is still being reported, contact ISDA web service support immediately; otherwise continue with the next step.
...
An x509 MIT personal certificate or an x509 MIT application certificate is required to access https://isda-ws3.mit.edu/wsUtilities/wsping.jsp
.
V. Security requirements
...