Knowledgebase: Pre-Sales
How to Configure Memory Allocated to FileCatalyst Workflow and Webmail
Posted by Aly Essa, Last modified by Aly Essa on 08 June 2016 06:23 PM

Overview

All of our FileCatalyst Products are installed with default memory limits, including both initial reserve and maximum memory. However, these can be configured to fit your specific needs and environment. This article will go through the configuration process for FileCatalyst Workflow or Webmail for Windows, Linux, and MacOSX

NOTE:

  • For all environments:
    If you are using a 32-bit Operating System or Java 32-bit, the maximum memory you can define for JAVA is limited to 1.5GB of memory.  64-bit Operating Systems running 64-bit Java do not have such memory limitations.
  • It is also recommended (but not required) to set the minimum and the maximum memory to the same value, as this allows JAVA to allocate a single continuous block of the memory from the OS on startup.
  • Have all Tomcat Server Service shut down before editing any configuration files.


Environment

FileCatalyst Workflow v4.9 and later.

FileCatalyst Webmail v4.9 and later.

 

Resolution 

Windows

When FileCatalyst Webmail or Workflow is installed on a Windows machine, there are two ways to increase the memory used.

  1. The first is to use the tomcat7w.exe or tomcat8w.exe, which is located in the \apache-tomcat\bin folder. A sample path would be C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\.
    1. Run tomcat7w.exe or tomcat8w.exe as an administrator. You can right-click the file and select the Run as Administrator.
    2. When the Tomcat Properties opens, select the Java tab.
    3. Increase Initial and Maximum Memory Pools as required. We recommend using identical values so the memory block is contiguous.

  2. The second method is to edit your catalina.bat file.
    1. Open the catalina.bat file in a text editor, which is located in the \apache-tomcat\bin. A sample path would be C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\
    2. Add the following line:

      set JAVA_OPTS="-Xms1024m -Xmx1024m -XX:NewSize=256m -XX:MaxNewSize=356m -XX:PermSize=256m -XX:MaxPermSize=356m"

      Again we recommend using identical values for both Xms and Xmx so your memory block is contiguous.

Linux

For a deployment of FileCatalyst Webmail or Workflow is installed on a Linux machine, the catalina.sh startup script needs to be editted.

  1. Navigate to the /apache-tomcat/bin/ folder and open the catalina.sh file in a text editor such as vi.
  2. Add the following line at the bottom of the file:

    export JAVA_OPTS="-Xms1024m -Xmx1024m -XX:NewSize=256m -XX:MaxNewSize=356m -XX:PermSize=256m -XX:MaxPermSize=356m"

    We recommended that the Xms and Xmx values be identical so your memory block is contiguous.

MacOSX

When FileCatalyst Webmail or Workflow is installed on a MacOSX machine, the catalina startup script.

  1. Navigate to the /apache-tomcat-/bin/ folder using Finder.
  2. Edit the catalina.sh file in a text editor.
  3. Add the following line at the end of the file:

    export JAVA_OPTS="-Xms1024m -Xmx1024m -XX:NewSize=256m -XX:MaxNewSize=356m -XX:PermSize=256m -XX:MaxPermSize=356m"

    We recommended that the Xms and Xmx values be identical so your memory block is contiguous.