Jama Connect User Guide

Monitor usage

It is important to monitor usage to be sure your organization has an adequate number licenses to meet your needs, and also to allocate an appropriate amount of memory for your usage.

The amount of memory that the application requires depends on several factors including: 

  • the size of your dataset

  • number of concurrent users

  • users' common workflows

If the memory consumption by any of the containers is close to the maximum available memory you can fine tune those values. Keep in mind that the jamacore container requires the highest amount of memory, then elasticsearch containers, and finally searchservice. 


Backup files can be very large in size; be sure to have enough disk space available before starting. If the file is too large and saved directly to your application server, this can cause issues. When you generate an export, be sure the machine you are saving to has more available disk space than the size of your actual database.

Make sure to not over-allocate the total memory of the application server and leave a fair amount of memory (headroom) available for system processes. Use these tables to estimate application server size and allocation.

Monitor usage and fine tune your memory settings as needed. There are several ways to keep an eye on usage:

  •  Log in to the application as root user and select the License management tab to view usage by license type.

  • Use the admin console monitoring graphs.

  • Use any Java application monitoring tool that supports JMS or use JavaMelody (which comes preconfigured with the Jama Connect application). To access JavaMelody navigate to [your.jama.url]/javamelody when you are logged in as root user.