User's Manual

C:\SOPHO Messenger@Net\Xml\Messenger_CFG.mdbat subscriber
• (activated on subscriber)
C:\SOPHO Messenger@Net\Mdb\Messenger_CFG.mdbat subscriber
Figure 96: Sample SQL script
Use this (optional) SQL script to modify the contents of the database, as arrived from the
operational publisher system. In some environments no changes are required; in more
demanding customer environments complex scenarios can be set up to allow applying
changes to the database. This can include changing .COM ports, IP address, group members,
and so on. Review your SQL changes carefully.
Switch back
When Publisher or Subscribers detect a change in the availability image, a switch to another
environment – or switch-back to the original environment – can be appropriate.
Conclusion
Careful planning and testing is required. Avaya recommends you simulate every configured
scenario, and analyze in detail the possible impact of every scenario. An off-site testing
procedure in a lab environment is usually appropriate, to prevent loss of alarms (during change
in image, eKERNEL and other modules are stopped and all alarms can be lost).
Also, take into account that having a high-availability solution in place affects change
management. Changes applied to eKERNEL must be synchronized, and (automatic) database
upgrade changes to Messenger_CFG.MDB must be handled manually by the system
administrator.
Finally, note that configuration changes with eCONFIG, eGRID, eWEB, or another
configuration tool can affect the total environment. For example, a divert to another device
does not work in a backup environment if the destination device in not available, or the module
is unavailable. Therefore, due to the nature of such an architecture, and maintenance issues
Module - eTM_HA
92 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]