Apache Tomcat is a service that Sage CRM uses to perform functions that handles features in the core app of CRM. Apache Tomcat handles the redirects into CRM from the sdata sub-domain. These redirects are functions like the dashboard, calendar, exporting files and uploads. When the dashboard does not work, it might be an indication that the Tomcat service is having trouble in the back end and needs to be looked at.
When you get the dreaded "The Dashboard has experienced a problem. Please contact your System Administrator". It should not be a doom and gloom affair; it can normally be corrected with just a few steps and basic checks.
Before doing any of these steps, you can check your Tomcat health status under the menu in CRM, Administration->System->System Health. This should show you if something is wrong with Tomcat and other CRM functions.
Here are my steps to diagnose Tomcat for Sage CRM
- Verify the logs. This is the first place you should start.
- Verify to see if the service is running.
- Verify if Tomcat is connecting to your SQL database.
- Verify your redirection ports in IIS.
- Verify your SDATA handler mapping and authorization.
- Advanced section.
For more logging and debugging, see the Advanced section, numbers 3,4,5. This will give more technical info on the debugging process or finding failed requests.
Let's look at each of these steps now.