Sentinel Installation and Configuration. Novell Sentinel 6 SP3

NOTE:

All the tablespaces are “auto-enabled”, by default.

Sentinel Installation and Configuration

When installing Sentinel, for performance and backup reasons, the following should be considered:

1. When performing a clean installation of Sentinel after having a previous version of Sentinel installed, it is highly recommended that you remove certain files and system settings from the previous installation. Not removing these files could cause a new, clean installation to fail. This should be done on every machine you are performing a clean installation.

For more information about which files to remove, see “Uninstalling

Sentinel” section.

2. The performance of Active Views and Mapping can improve dramatically if you point the temp directory of the DAS_RT and

DAS_Query processes to a fast disk (For example, a disk array). To point the temp directory of these processes to a fast disk, do the following on the machine where DAS is installed: a. Create a directory on the fast disk to place the temp files. If on

UNIX, this directory must be owned and writable by the Sentinel

Administrator User and the group esec.

NOTE:

Installer automatically creates a backup of configuration.xml

at

%ESEC_HOME%\config\configuration.xml

. b. Open the file %ESEC_HOME%\config\configuration.xml in a text editor. c. For the DAS_RT and DAS_Query processes, add the JVM argument java.io.tmpdir, setting it to the directory you just created. d. To make this change to the DAS_RT process, look for the line containing the text

-Dsrv_name=DAS_RT and add the argument mentioned below next to it.

-Djava.io.tmpdir=<tmp_directory>

An example of what the line should like (your –Xmx, -Xms, and –XX args might look different) is:

<process component="DAS" image="&quot;$(ESEC_JAVA_HOME)/java&quot; server -Dsrv_name=DAS_RT -

Djava.io.tmpdir=/opt/Temp2 -Xmx310m -

Xms103m -XX:+UseParallelGC -Xss128k -Xrs -

Desecurity.dataobjects.config.file=/xml/Bas eMetaData.xml -

Djava.util.logging.config.file=../config/da s_rt_log.prop -

Dcom.esecurity.configurationfile=../../conf

Best Practices 2-15

iguration.xml -

Djava.security.auth.login.config=../config/ auth.login -

Djava.security.krb5.conf=../../lib/krb5.con

f -jar ../../lib/ccsbase.jar

..//config//das_rt.xml" min_instances="1" post_startup_delay="5" shutdown_command="cmd //C

&quot;$(ESEC_HOME)/bin/stop_container.bat&q uot; localhost DAS_RT" working_directory="$(ESEC_HOME)/bin"/> e. To make this change to the DAS_Query process, look for the line containing the text

-Dsrv_name=DAS_Query and add the argument mentioned below next to it.

-Djava.io.tmpdir=<tmp_directory>

An example of what the line should like (your –Xmx, -Xms, and –XX args might look different) is:

<process component="DAS" image="&quot;$(ESEC_JAVA_HOME)/java&quot; server -Dsrv_name=DAS_Query -

Djava.io.tmpdir=/opt/Temp2 -Xmx256m -Xms85m

-XX:+UseParallelGC -Xss128k -Xrs -

Desecurity.dataobjects.config.file=/xml/Bas eMetaData.xml,/xml/WorkflowMetaData.xml -

Djava.util.logging.config.file=../config/da s_query_log.prop -

Djava.security.auth.login.config=../config/ auth.login -

Djava.security.krb5.conf=../../lib/krb5.con

f -

Desecurity.execution.config.file=../config/ execution.properties -

Dcom.esecurity.configurationfile=../../conf iguration.xml -jar ../../lib/ccsbase.jar

..//config//das_query.xml" min_instances="1" post_startup_delay="5" shutdown_command="cmd //C

&quot;$(ESEC_HOME)/bin/stop_container.bat&q uot; localhost DAS_Query" working_directory="$(ESEC_HOME)/bin"/>

2-16 Sentinel Installation Guide