Every runnable has a JAVA-Xmx configuration parameter. It has to be monitored, if the memory usage is rising over time.
Peaks are not a problem, if they do not break the limit. If the system is suffering over a longer time, for example, the memory usage is higher than 70% for more than one hour, check for rarely occurring use cases. They might explain the high memory consumption. This can be:
an exceptional number of parallel running Process Governance processes
more users accessing as usual
expensive reporting
running database maintenance operations
assigning user access right over the whole database etc.
If the defined limit for memory consumption is exceeded, there are two possible measures:
Extend the heap size for the concerned runnable. This can be done in ACC with a configure command for the JAVA-Xmx parameter. But this step only makes sense, if enough additional memory is available.
Scale up by increasing the resources, for example, adding a new node/runnable of the same type or assigning more memory to the virtual machine and increasing the JAVA-Xmx parameter for the runnable to use this memory.
For advanced ARIS server installations Software AG strongly recommends that you request an installation service by Global Consulting Services. You can order that service from your Software AG sales representative.