Novell SENTINEL 6.1 SP2 - INSTALLATION GUIDE 02-2010 Installation Manual page 30

the machine. However, performance testing shows that the 64-bit JVM requires nearly double the
RAM to perform the same tasks as compared to the 32-bit JVM. So using the 64-bit JVM for a
process that does not require this additional RAM wastes memory resources. For example, if a
process was allocated 1200m with a 32-bit JVM, there is no benefit to running that process on a 64-
bit JVM unless more than double the amount of RAM is allocated to it. In this example, the amount
must be more than 2400m.
There are several processes that can benefit from having an additional RAM at their disposal
(beyond the 1200m limit of a 32-bit JVM). For example, DAS_RT can hold more Active Views. A
Collector Manager can support more Collectors and Connectors. The Correlation Engine can
support more rules. DAS_Query, DAS_Binary, and DAS_Aggregation can also take advantage of
additional RAM. However, a few processes such as DAS_iTRAC, DAS_Proxy, and Sonic are not
likely to make use of memory beyond the 1200m that is supplied with a 32-bit JVM.
To move all the processes on a machine to use the 64-bit JVM:
1 Stop the Sentinel services. Select Start > Control Panel > Administrative Tools > Services,
right-click Sentinel, then select Stop.
2 Back up the
3 Modify the
Windows: Set

 Linux: Set
4 Reload the environment variables.
Windows: Replace

variable.
Linux: Log out and log in to Sentinel.

5 Open the
6 Modify the
you want to allocate additional memory.
Start by doubling the value that was already there for every process. This is necessary because
of the overhead of the 64-bit JVM as described earlier. Then, for processes that you want to
have additional RAM, modify their values again and choose an even higher number.
7 Save the
syntax.
8 Start the Sentinel services. Select Start > Control Panel > Administrative Tools > Services,
right-click Sentinel, then select Start.
To move individual processes on a machine to use the 64-bit JVM:
NOTE: On Windows, only the Correlation Engine and Collector Manager can be moved
individually to 64-bit JVM. This limitation exists because other processes use the dynamic link
libraries (DLLs) found in the PATH environment variable, and there is only one PATH environment
variable for both 32-bit and 64-bit processes. Only one type of DLL (32-bit or 64-bit) can appear
first in the PATH. On UNIX, any process can be moved individually to 64-bit.
1 Stop the Sentinel services. Select Start > Control Panel > Administrative Tools > Services,
right-click Sentinel, then select Stop.
2 Back up the
30 Sentinel 6.1 Installation Guide
ESEC_HOME/config/configuration.xml
path environment variable to point to 64-bit JVM.
ESEC_JAVA_HOME
ESEC_JAVA_HOME
ESEC_JAVA_HOME
%ESEC_HOME%\lib\x86
ESEC_HOME/config/configuration.xml
setting of every process entry in the
-Xmx<#>m
file and open the file in a Web browser to validate the XML
configuration.xml
ESEC_HOME/config/configuration.xml
file.
to
%ESEC_HOME%\jre64\bin
to
$ESEC_HOME/jre64/bin
with
%ESEC_HOME%\lib\x86_64
file in a text editor.
configuration.xml
file.
in the path
file for which