User's Manual

the database at startup. Therefore, after applying a new version of eKERNEL, you must first
start eKERNEL, and then copy the Messenger_CFG.mdb database.
If you install new versions of eKERNEL, you must synchronize the eKERNEL modules on all
systems. Also the latest layout of Messenger_CFG of publisher (after automatic upgrade
changes at first run) must be manually placed in the directory of the Subscribers.
GetImage puts a file Messenger_CFG.xml in the same directory, and replaces this file on
receipt of a GetImage result.
If you want to review this file, make a copy in another location before doing so, for example,
C:\Temp. You can, for example, launch the Internet Explorer and associate XML files to this
program, as Internet Explorer has built-in functionality to parse XML documents.
Warning:
Do not open the file in the C:\SOPHO Messenger@Net\Xml, because the file can be
allocated by the viewer, and must be replaced when the next KeepAlive result is received.
SQL script
When a Subscriber detects a change between P:1 and P:0:
1. The Subscriber ends all running tasks associated with the current environment.
At this time, Messenger functionality is disrupted, and pending and new alarms can
be lost.
2. The SQL image in C:\SOPHO Messenger@Net\Xml repository
Messenger_CFG.xml is imported to the workspace C:\SOPHO Messenger@Net
\Xml access database Messenger_CFG.mdb. For this reason, the
Messenger_CFG.mdb on Publisher and Subscriber sites must always use the same
layout.
Thus the following repositories exist:
• (original database on publisher)
C:\SOPHO Messenger@Net\Mdb\Messenger_CFG.mdbat publisher
• (transferred as XML images through HTTP)
C:\SOPHO Messenger@Net\Xml\Messenger_CFG.xmlat subscriber
• (converted into MDB on subscriber)
C:\SOPHO Messenger@Net\Xml\Messenger_CFG.mdbat subscriber
• (processed through optional SQL script, described in Figure 96: Sample SQL script on
page 92)
Keeping track of states
DECT Messenger Installation and Commissioning — Book 2 March 2012 91