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

11 Locate the
das_binary_log.prop
on Windows) directory.
12 Create a copy of the
das_binary_log.prop
run. For example, to run two instances of DAS_Binary, create two copies of
das_binary_log.prop
13 Rename the
das_binary_log.prop
14 Delete the unneeded durable subscription.
After the system is restarted, the multiple DAS_Binary processes share a new, single, durable
shared subscription to the Sentinel message bus event channels. In order to avoid the message
bus cache from growing indefinitely and filling up the hard drive, the durable subscription that
was initially created by the primary DAS_Binary must be deleted.
14a Open the Sonic Management Console.
14b Windows: Select Start > Programs > Sentinel > SonicMQ > SonicMQ 7.0 >
Management Console
Unix: Open a terminal console and run the following command:
$ESEC_HOME/3rdparty/SonicMQ/MQ7.0/bin/startmc.sh
14c Specify the following to log in to the management console:
Connection Name
Domain Name
Connection URL
User Name
Password
14d In the management console, select Manage tab >Containers > esecContainer >
esecBroker > Durable Subscriptions.
14e Select the first empty row in the Users & Groups table on the right side of the GUI.
file in the
$ESEC_HOME/config
file for each instance of DAS_Binary you want to
.
files to match the names selected in step 5.
(
%ESEC_HOME%\config
Leave as default
esecDomain
tcp://localhost:10012
Leave as default
Leave as default
Adding Sentinel Components 89