Knowledgebase
Configuring Memory Allocated to FileCatalyst Direct Products
Posted by Greg Pettit on 06 December 2012 04:06 PM

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 each FileCatalyst product for Windows, Linux and Mac.

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.

  

FileCatalyst Direct Server

Windows

STAND-ALONE:  When running FileCatalyst Server stand-alone (directly launching the executable), the FileCatalyst Server will run using a maximum of 1024 MB of memory.  This cannot be modified since the values are embedded inside the FileCatalyst.exe binary.

SERVICE:  When running FileCatalyst Server as a Windows Service, you can configure the application to use either a smaller or larger memory footprint based on your needs:

  1. Stop FileCatalyst Server
  2. Edit fcconf.conf found in the application installation directory (by default C:\Program Files\FileCatalyst Server\fcconf.conf) and enter in the memory values you require.

    # Java Additional Parameters
    wrapper.java.additional.1=-XX:MaxDirectMemorySize=1G
    # Initial Java Heap Size (in MB)
    wrapper.java.initmemory=1024
    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024
  3. Start FileCatalyst Server

 

Linux

STAND-ALONE:  Linux installations include basic startup scripts (fc_server.sh, fc_server_console.sh) which can be modified to use more memory.  Here is a sample from a launch script:

java -Djava.library.path=. -Xms64M -Xmx1024M -XX:MaxDirectMemorySize=512M -jar FileCatalystServer.jar -controlpanel &

To run with 2GB of RAM, modify the script to look like the following:

java -Djava.library.path=. -Xms2048M -Xmx2048M -XX:MaxDirectMemorySize=2048M -jar FileCatalystServer.jar -controlpanel &

SERVICE:  When running FileCatalyst Server as a Linux/Solaris Service, you may configure the application to use a different memory footprint by editing wrapper.conf:

  1. Stop FileCatalyst Server
  2. Edit wrapper.conf found in the application installation directory (by default /opt/utechsoft/server/conf/wrapper.conf).  Enter the memory values you require.

    # Java Additional Parameters
    wrapper.java.additional.1=-XX:MaxDirectMemorySize=1G
    # Initial Java Heap Size (in MB)
    wrapper.java.initmemory=1024
    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024
  3. Start up FileCatalyst Server service

 

MacOSX

STAND-ALONE:  MacOSX configurations are managed by a "Info.plist" file residing inside the FileCatalystServer.app package which tells the system the parameters needed to start the application.

To access the Info.plist:

  1. select the FileCatalyst Server icon and right click
  2. select Show Package the Contents folder
  3. edit the info.plist with a text editor. To increase the memory used edit  the following line:

    <string>-Xms1024M -Xmx1024M</string>

SERVICE:  The service script (fc_service) supplied for MacOSX service installations creates an Info.plist file as part of its service registration.  You can modify the fc_service script to change the memory constraints before registering the application as a service (or to re-register the service after memory settings have been modified):

  1. select the FileCatalyst Server icon and right click
  2. select Show Package and locate the Contents/Resources/Java/ folder
  3. edit the fc_service script memory values:

    <string>-Xms64M</string>
    <string>-Xmx1024M</string>
    <string>-XX:MaxDirectMemorySize=512M</string>
  4. Run the script to register the service
  5. Start the service script up.

 

FileCatalyst HotFolder 

Windows

STAND-ALONE: When running FileCatalyst HotFolder stand-alone (directly launching the executable), the FileCatalyst HotFolder will run using a maximum 1024 MB of memory.  These values are embedded inside the FileCatalyst.exe application.

SERVICE: When running FileCatalyst HotFolder as a Windows service, the application may be configured to fit your needs. To modify these values do the following:

  1. Stop FileCatalyst HotFolder
  2. Edit fchf.conf found in the application installation directory (by default C:\Program Files\FileCatalyst HotFolder\fchf.conf).  Enter the memory values you require.

    # Java Additional Parameters
    wrapper.java.additional.1=-XX:MaxDirectMemorySize=1G
    # Initial Java Heap Size (in MB)
    wrapper.java.initmemory=1024
    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024
  3. Start FileCatalyst HotFolder

 

Linux

STAND-ALONE:  Linux installations include basic startup scripts (fc_hotfolder.sh, fc_hotfolder_console.sh) which can be modified to use more memory.  Here is a sample from the launch script:

java -Djava.library.path=. -Xms64M -Xmx1024M -XX:MaxDirectMemorySize=512M -jar FileCatalystHotFolder.jar -controlpanel &

To run with 2GB of RAM, modify the script to look like the following:

java -Djava.library.path=. -Xms2048M -Xmx2048M -XX:MaxDirectMemorySize=2048M -jar FileCatalystHotFolder.jar -controlpanel &

SERVICE:  When running FileCatalyst HotFolder as a Linux/Solaris Service, you may configure the application to use a different memory footprint by editing wrapper.conf:

  1. Stop FileCatalyst HotFolder
  2. Edit wrapper.conf found in the application installation directory (by default /opt/utechsoft/hotfolder/conf/wrapper.conf).  Enter the memory values you require.

    # Java Additional Parameters
    wrapper.java.additional.1=-XX:MaxDirectMemorySize=1G
    # Initial Java Heap Size (in MB)
    wrapper.java.initmemory=1024
    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024
  3. Start FileCatalyst HotFolder service

 

Mac

STAND-ALONE:  MacOSX configurations are managed by a "Info.plist" file residing inside the FileCatalystHotFolder.app package which tells the system the parameters needed to start the application.

To access the Info.plist:

  1. select the FileCatalyst HotFolder icon and right click
  2. select Show Package the Contents folder
  3. edit the info.plist with a text editor. To increase the memory used edit  the following line:

    <string>-Xms1024M -Xmx1024M</string>

SERVICE:  The service script (fc_service) supplied for MacOSX service installations creates an Info.plist file as part of its service registration.  You can modify the fc_service script to change the memory constraints before registering the application as a service (or to re-register the service after memory settings have been modified):

  1. select the FileCatalyst Server icon and right click
  2. select Show Package and locate the Contents/Resources/Java/ folder
  3. edit the fc_service script memory values:

    <string>-Xms64M</string>
    <string>-Xmx1024M</string>
    <string>-XX:MaxDirectMemorySize=512M</string>
  4. Run the script to register the service
  5. Start the service script.

 

 

FileCatalyst Central

Windows

Locate the file mawrapper.conf in the FileCatalyst Central installation. To increase the memory used, edit the following lines:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

To maximize performance improvement we recommend that the both values be identical, which will cause Java to allocate a contiguous block of memory.

 

Linux

Locate the file wrapper.conf in the FileCatalyst Central installation directory and within the service_wrapper/common/conf directory. To increase memory used by Central, edit the following lines:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

To maximize performance improvement we recommend that the both values be identical, which will cause Java to allocate a contiguous block of memory.

 

Mac

To access info.plist, right-click the FileCatalyst Central icon, select Show Package, locate the Contents folder and edit the info.plist with a text editor. To increase memory used, edit the following:

<string>-Xms64M -Xmx512M -Djava.util.logging.config.file=maLogConfig.properties</string>

If Central is being run as a service, edit mawrapper.conf and modify the following lines:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

To maximize performance improvement we recommend that the both values be identical, which will cause Java to allocate a contiguous block of memory.

 

 

CK

(0 vote(s))
Helpful
Not helpful

Comments (0)