Specifying Java runtime options for FileNet Deployment Manager

Consider adjusting these options to suit the FileNet Deployment Manager environment and expected workload. For example, if large data maps are expected, which can occur if many security principals are manipulated, try increasing the initial heap size can avoid heap memory issues.

For more information about JVM tuning, see Tuning the Java(tm) Virtual Machine (JVM) for IBM® FileNet(r) P8 components.

JVM runtime arguments

FileNet Deployment Manager uses the IBM Java Virtual Machine (JVM); and the JVM runtime behavior is controlled by arguments that are specified in the DeploymentManager.ini file.

Setting the initial heap size and maximum heap size

You can specify the initial heap size and the maximum heap size that FileNet Deployment Manager uses by setting the -vmargs flag and specifying the initial heap size argument (-Xms) and the maximum heap size argument (-Xmx) in the DeploymentManager.ini file.

Important: When you edit the deploymentmanager.ini file, both the initial heap size parameter and the maximum heap size parameter must be listed after the -vmargs flag. Additionally, the -vmargs flag must be on a line after the -vm flag, if both the -vmargs flag and the -vm flag are present in the DeploymentManager.ini file. For example, the default settings for the initial heap size and the maximum heap size are configured as follows:

-vmargs 
-Xms256m 
-Xmx768m

Java system property settings

Setting the query time limits system property

You can control time limits for queries in the Root Folder and Unfiled Documents nodes within the Folders and Contained Objects asset category of the Add Assets dialog box. The default value is 60 seconds. This value can be configured by setting the Java system property com.filenet.deployment.QueryTimeLimit. To set this Java system property, add the following line to the FileNet Deployment Manager .ini file, where <limit> is the query time limit, in seconds:

-Dcom.filenet.deployment.QueryTimeLimit=limit

Enabling Java logging

To enable Java logging with Apache log4j logging utility, add the following line to the DeploymentManager.ini file, where logfile is the URI specification of the logging configuration file:

-Dlog4j.configuration=file:logfile

For example:

-Dlog4j.configuration=file:/c:\log4j.properties

For more information about modifying the log4j configuration file, see Working with the Apache log4j Configuration File.

For information about log file location and logging configuration and usage, see FileNet Deployment Manager log files.