see How to acquire and verify a M.I.T. x509 Application Certificate for detailed instructions.

see How to create an Application Certificate Java keystore for detailed instructions.

The DSPS wsMonitor application requires that the mapping.app.mit.edu.jks keystore be installed on any server that is to be monitored. Copy the mapping.app.mit.edu.jks to the $WSETCDIR/keystore directory (overwrite the existing mapping.app.mit.edu.jks keystore) on each of the servers below:

• isda-ws1.mit.edu
• isda-ws2.mit.edu
• isda-ws3.mit.edu
• isda-ws4.mit.edu
• map-dev-ws1.mit.edu
• map-test-ws1.mit.edu
• map-dev-console.mit.edu
• map-prod-console.mit.edu
• ws-dev.mit.edu
• ws-test.mit.edu
• ws-stage.mit.edu
• ws-prod.mit.edu

In addition, if you want to use the JMX jconsole to monitor other DSPS tomcat containers, copy the mapping.app.mit.edu.jks to the $WSETCDIR/keystore directory (overwrite the existing mapping.app.mit.edu.jks keystore) on each of the servers below:

• maven-dev.mit.edu
• maven-stage.mit.edu
• maven-prod.mit.edu
• build-dev.mit.edu
• build-stage.mit.edu
• build-prod.mit.edu
• src-dev.mit.edu
• src-stage.mit.edu
• src-prod.mit.edu

Once you have copied the new mapping.app.mit.edu.jks to a server, all the Tomcat containers on that server must be restarted.  This is necessary because the mapping.app.mit.edu.jks is used by Tomcat itself and is only read by Tomcat at startup.