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

Hide thumbs Also See for SENTINEL 6.1 SP2 - INSTALLATION GUIDE 02-2010:
Table of Contents

Advertisement

copies of the DAS_Binary service entry. Delete the uuid attribute for each of the service entries
(the uuid attribute will automatically be regenerated when Sentinel is started). The following is
an example of one DAS_Binary service entry.
<service name="DAS_Binary" plugins="" strategyid="sentinel_client"
uuid="4DA52BE0-E7A4-1029-BB2F-00132168CBDF"/>
3 In the
configuration.xml
xml for every instance of DAS_Binary you want to run. This service does not
service entry
exist in the
configuration.xml
example, to run two DAS_Binary processes, make two copies of the following
DAS_Binary_EventStore service entry:
<service name="DAS_Binary_EventStore" plugins=""
strategyid="sentinel_client" subscriptiongroup="dasbin" />
4 Give each copy of the DAS_Binary and DAS_Binary_EventStore service entry a unique name.
For example, the service names might be DAS_Binary1, DAS_Binary_EventStore1,
DAS_Binary2, and DAS_Binary_EventStore2.
5 Locate the section of the
example below). Make a copy of the DAS_Binary process entry for every instance of
DAS_Binary you want to run. For example, to run two DAS_Binary processes, make two
copies of the DAS_Binary process entry. For each DAS_Binary process entry, modify sections
of the entry as described below:
DAS_Binary Dsrv_name: Change to match the DAS_Binary service names defined in
step 4, such as DAS_Binary2.
DAS_Binary communication service name: Insert the following text into the process
entry's image attribute at the location shown in bold in the process entry example below.
For each DAS_Binary process entry, replace the DAS_Binary part of the text below with
the associated service name, such as DAS_Binary2.
-Desecurity.communication.service=DAS_Binary
 das_binary.xml
These names are used in a later step.
das_binary_log_prop file name: Use any unique name(s), such as
das_binary_log_2.prop
das_binary.cache directory name: Use any unique name(s), such as
das_binary2.cache
das_binary.cache
DAS_Binary process name: Change the value of the process entry's name attribute to
match the DAS_Binary service names defined in step 4, such as DAS_Binary2.
The following xml is an example of a process entry as discussed in the instructions above:
file, create a copy of the following
file, so you should copy it from the example below. For
file that defines the processes entries (see
configuration.xml
file name: Use any unique name(s), such as
. These names are used in a later step.
. Each instance of DAS_Binary must use a different
directory.
DAS_Binary_EventStore
das_binary_2.xml
Adding Sentinel Components
.
87

Advertisement

Table of Contents
loading

This manual is also suitable for:

Sentinel 6.1 sp2

Table of Contents