User's Manual
The eTM_HA software must be installed on both the Publisher and the Subscriber site. Based
upon configuration settings in the registry, the instance behaves as Publisher or as
Subscriber.
The following functionality is available:
• eTM functionality
- Launch tasks associated with an environment
- Keep track of running processes of an environment
- Restart tasks that are missing
• eTM_HA specific functionality on Publisher
- TCP server, listening on an administration port (default 7000)
- Handling KeepAlive requests from Subscriber
- Handling GetImage requests from Subscriber
- Keeping track of state of Publisher and Subscriber
- Changing the environment depending on the Publisher and Subscriber states
• eTM_HA specific functionality on Subscriber
- TCP client, connecting to Publisher administration port
- Sending KeepAlive requests to Publisher
- Sending GetImage requests to Publisher
- Keeping track of state of Publisher and Subscriber
- Changing the environment depending on the Publisher and Subscriber states
During a change of environment, all running tasks of a previous environment are ended, and
new tasks of the new environment are launched. During such an event, the Subscriber applies
the last database image received from the Publisher and optionally applies changes defined
in an SQL Script.
Registry settings eTM
The configuration of environments and tasks is stored in the following section:
[HKEY_CURRENT_USER\Software\Philips\SOPHO Messenger@Net\eTM]
This section contains definitions of environments and tasks, as described in the documentation
of module eTM, Module - eTM on page 51. These settings can be entered manually of can be
generated by the eCONFIG or eGRID modules.
Module - eTM_HA
68 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? infodev@avaya.com