Configuring Workflow to use a 64-bit JRE
search cancel

Configuring Workflow to use a 64-bit JRE


Article ID: 50604


Updated On:


CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



Generally the 1.5GB memory maximum limit of the 32-bit JRE is sufficient for Workflow, but under heavy usage this may not be enough. This document details how to configure Workflow's Tomcat to use a 64-bit JRE to allow additional memory to be designated for use by Workflow.


The following will only work in a 64-bit Environment and should only be attempted on systems with more than 4 gigabytes (GB) of available memory.

  1. Install the Java 1.6 64-bit JRE on the Service Desk system that CA Workflow is installed on.

  2. Edit the NX.env file and add the following entries in the Tomcat section: -Xms64M [email protected]_JRE_INSTALL_DIR_CAWF=C:/Progra~1/Java/jre6
    where the -Xmx2048M is the maximum memory Java will utilize, and the JRE_INSTALL_DIR is the location where the 64-bit JRE has been installed. This does not have to be an exact value - for instance 4096 MM for 4 GB; you can specify 5000M as long as the resources are available.

    If Workflow is deployed on a secondary server, the 64-bit JRE installation and the nx.env changes are only applied on that secondary server.

  3. Restart Service Desk.

The new memory setting should be visible in the stdlog on the startup_tomcat line:
startup_tomcat: C:/Progra~1/Java/jre6... -Xrs64M -Xmx2G...

Currently there is no upper limit to the amount of memory that can be specified for the 64-bit JRE. If you have 16 GB of RAM on your Workflow Server, it is conceivable to dedicate 10 GB to Tomcat for Workflow. This however is an extreme example and for most implementations dedicating an amount between 4 GB and 6 GB should be more than enough.


Component: ARGIS