MONITORING ISDA WEB SERVICES
TABLE OF CONTENTS
o URL to monitor
o Detecting a web service failure
o What to do when a web service fails
o Operational requirements
o Security requirements
I. URL to monitor
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.
III. What to when a web service fails
If at any point you run into difficulties, immediately contact ISDA web service support.
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.
The resulting display will indicate the service that has failed along with its associated server.
2) If all services on a given server have failed, contact ISDA web service support immediately; otherwise continue with the next step.
3) Restart the apache and tomcat servers on the affected web server. Complete the following steps.
a) logon onto the server using a root account
b) go to the /root directory
cd /root
c) stop the apache and tomcat servers.
./stopweb
d) verify that the apache server has stopped:
ps aux | grep apache
and you should get something similar to:
root 19053 0.0 0.0 3756 652 pts/0 S+ 11:48 0:00 grep apache
e) verify that the tomcat server has stopped:
ps aux | grep tomcat
and you should get something similar to:
root 19117 0.0 0.0 3892 652 pts/0 S+ 11:50 0:00 grep tomcat
f) start the apache and tomcat servers:
./startweb
g) to verify that apache is running, do the following:
ps aux | grep apache
if apache is running, you should get something similar to:
root 18888 0.0 1.8 1182484 75972 pts/0 Sl 11:39 0:00 /usr/local/jdk1.6.0/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/home/apache-tomcat-5.5.23/conf/logging.properties -Djava.endorsed.dirs=/home/apache-tomcat-5.5.23/common/endorsed -classpath :/home/apache-tomcat-5.5.23/bin/bootstrap.jar:/home/apache-tomcat-5.5.23/bin/commons-logging-api.jar -Dcatalina.base=/home/apache-tomcat-5.5.23 -Dcatalina.home=/home/apache-tomcat-5.5.23 -Djava.io.tmpdir=/home/apache-tomcat-5.5.23/temp org.apache.catalina.startup.Bootstrap start
root 18905 1.1 0.0 6364 3416 ? Ss 11:39 0:00 /home/apache/bin/httpd -k start
apache 18906 0.0 0.0 6364 3424 ? S 11:39 0:00 /home/apache/bin/httpd -k start
apache 18907 0.0 0.0 6364 3424 ? S 11:39 0:00 /home/apache/bin/httpd -k start
apache 18908 0.0 0.0 6364 3424 ? S 11:39 0:00 /home/apache/bin/httpd -k start
apache 18909 0.0 0.0 6364 3424 ? S 11:39 0:00 /home/apache/bin/httpd -k start
apache 18910 0.0 0.0 6364 3424 ? S 11:39 0:00 /home/apache/bin/httpd -k start
root 18923 0.0 0.0 5044 652 pts/0 S+ 11:39 0:00 grep apache
h) to verify that tomcat is running, do the following:
ps aux | grep tomcat
if tomcat is running, you should get something similar to:
root 18888 0.0 1.9 1183780 81012 pts/0 Sl 11:39 0:00 /usr/local/jdk1.6.0/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/home/apache-tomcat-5.5.23/conf/logging.properties -Djava.endorsed.dirs=/home/apache-tomcat-5.5.23/common/endorsed -classpath :/home/apache-tomcat-5.5.23/bin/bootstrap.jar:/home/apache-tomcat-5.5.23/bin/commons-logging-api.jar -Dcatalina.base=/home/apache-tomcat-5.5.23 -Dcatalina.home=/home/apache-tomcat-5.5.23 -Djava.io.tmpdir=/home/apache-tomcat-5.5.23/temp org.apache.catalina.startup.Bootstrap start
root 19001 0.0 0.0 3660 652 pts/0 S+ 11:42 0:00 grep tomcat
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.
5) email ISDA web service support indicating the date and time, the web server(s) and the web service(s) for which a failure was reported.
IV. Operational requirements
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
All access to any web service monitoring/diagnostic tools is controlled by ACEGI. This means that in addition to having an appropriate x509 certificate, the certificate CN (for application certificates) or the email address (for personal certificates) must also be configured in ACEGI. Contact isda web service support to have your x509 certificate appropriately configured, in ACEGI, for access to web service monitoring/diagnostic tools.