Summary:

Psi-probe is an intended replacement for Tomcat Monitor, and provides advanced monitoring options for a Tomcat install. We do not support deploying additional webapps along with a CRM install, however there may be cases where this is useful, such as troubleshooting thread waits and suspected memory leaks.

More info:

1: Download the latest version from here:

http://code.google.com/p/psi-probe/downloads/list

2: Stop the Tomcat service.

3: Extract probe.war from the archive and place it in ..\CRM\tomcat\webapps: You need to add a Tomcat user for Probe. The user does not need to be either a Windows or CRM user. Edit tomcat-users.xml in ..\CRM\tomcat\conf. Users should be added in the following format:

<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<role rolename="poweruser"/>
<role rolename="poweruserplus"/>
<role rolename="probeuser"/>
<user username="admin" password="Password" roles="manager"/>
</tomcat-users>

5: Next, we need to allow Tomcat's JRE to use Java Management Extensions (JMX). This allows enhanced monitoring of webapps. Open regedit, and go to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\CRMTomcat6\Parameters\Java

Add the following 2 lines to the Options key (you might as well add the PermGen options if they're not already applied):

-Dcom.sun.management.jmxremote
-XX:MaxPermSize=256m

If you already have a higher MaxPermSize setting, then that hsould be left as-is.

6: Start the Tomcat service. Probe will deploy, and be available at http://<CRM server>:<Tomcat port>/probe/

7: When prompted, you can log in using the username and password you entered in the tomcat-users.xml (admin/Password in the example above).