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

process component="DAS" depends="UNIX Communication Server,Windows
Communication Server" image=""$(ESEC_JAVA_HOME)/java" -server -
Dsrv_name=DAS_Binary -Xmx160m -Xms64m -XX:+UseParallelGC -
XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=../log/DAS_Binary.hprof -
Xss136k -Xrs -Desecurity.communication.service=DAS_Binary -
Duser.language=en
Desecurity.cache.directory=../data/das_binary.cache -
Desecurity.dataobjects.config.file=/xml/BaseMetaData.xml -
Djava.util.logging.config.file=../config/das_binary_log.prop -
Dcom.esecurity.configurationfile=../config/configuration.xml -
Djava.security.auth.login.config=../config/auth.login -
Djava.security.krb5.conf=../config/krb5.conf -jar ../lib/ccsbase.jar ..//
config//das_binary.xml" min_instances="1" name="DAS_Binary"
post_startup_delay="20" type="container" working_directory="$(ESEC_HOME)/
data"/>
6 Save the
7 Locate the
Windows) directory.
8 Create a copy of the
For example, to run two instances of DAS_Binary, create two copies of
9 Rename the copied
10 Make the following changes to each of the
 Make a copy of the entire
component's id from
making this change, you should have one component with the id
another component with the id
 Update the value of the property named
DispatchManager
as DAS_Binary2.
Update the value of the property named

EventStoreDispatchManager
DAS_Binary_EventStore, such as DAS_Binary_EventStore2.
 Remove the property with name
DispatchManager
Remove all properties with a name that starts with "

handler:esecurity.event.create
component. The handler
handler defined in the
Add the following XML element to the

<obj-component-ref>
</obj-component-ref>
The

das_binary.xml
EventAggregationService component of the
DAS_Aggregation to pick up the event files from a secondary DAS_Binary.
Save the

88 Sentinel 6.1 Installation Guide
-Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF8 -
file.
configuration.xml
file in the $ESEC_HOME/config (%ESEC_HOME%\config on
das_binary.xml
das_binary.xml
das_binary.xml
DispatchManager
DispatchManager
component with the appropriate unique name for DAS_Binary, such
component.
handler:esecurity.event.create
EventStoreDispatchManager
<name>DispatchManager</name>
<ref-id>EventStoreDispatchManager</ref-id>
property in the EventFileRedirect component of the
outputDirectory
file must have the same value as the
file.
das_binary.xml
file for each instance of DAS_Binary you want to run.
files to match the names selected in step 5.
das_binary.xml
component and change the new
to
EventStoreDispatchManager
EventStoreDispatchManager
esecurity.communication.service
esecurity.communication.service
component with the appropriate unique name for
handler:esecurity.event.create
handler:*
from the
EventStoreDispatchManager
component.
EventStoreService
directory
das_aggregation.xml
das_binary.xml
files:
. After
DispatchManager
.
of the
of the
from the
" except
for
should be the only
component.
property in the
file. This allows the
.
and