Milestone XProtect Transact - Manual (Page 38)

Milestone XProtect
®
Transact
Administrator's Guide
www.milestonesys.com 38 Administration
Update slave information
To send a slave server's server service settings to its master servers, click the Update button on the
Masters tab.
When you change a slave server's server service settings information, it is immediately sent to the
server's master servers. If, for some reason, a master server is not running when this happens, you
are notified. When the master server is running again, you can click the Update button to resend the
slave server's updated server service settings to its masters.
Master setup dialog elements
The MasterInformation window contains the following fields:
Name Description
Administration service name The administration service name of the master server.
Host The IP address or host name of the master server.
Port The port number of the master server.
Protocol The protocol used by the master server.
Tip: You can find all of the information about the master server's server service settings on the
master's Server Service Setting window in the right-click menu of the XProtect Transact Server
Service Taskbar icon.
Define a master server
Prerequisites: When defining a master server for the XProtect Transact server you are configuring,
you need to enter the master server's server service settings. Have information about the master
server's server service settings ready when defining the master/slave setup.
To define a master server, do the following:
1. On the XProtect Transact server that is going to be configured as slave, open the XProtect
Transact Administrator.
2. On the Masters tab, click Add New....
3. Specify the administration service name, host name and port number of the master server, and
click OK.
Events and event groups
Through XProtect Transact's event and event group features you can get XProtect Transact to listen
for occurrences of specific words, numbers, characters etc. in the transaction data and generate
events when the specified occurrences are found. When an occurrence is found a transaction event is
triggered.
For easy and flexible usage of transaction events, you can group events in event groups. Each
transaction event can be member of several groups. With event groups you also specify how
transaction data is send to your surveillance system, and you can associate sources to an event
group.