Echelon IzoT Commissioning Tool - Manual (Page 254)

While it is possible for multiple users to be modifying the same page of an OpenLNS CT drawing at
the same time, if the users are working in the same subsystem, it is possible for one user to delete an
IzoT Commissioning Tool object that the other user is trying to modify at the same time. As a result,
multiple users will typically be more productive if they are working in different subsystems.
OpenLNS Event Tracking
IzoT Commissioning Tool uses OpenLNS events to detect changes to an OpenLNS CT drawing made
by OpenLNS applications other than IzoT Commissioning Tool, as well as changes in the status of
devices as reported by the OpenLNS server. Actions tracked exclusively by OpenLNS events consist
of detecting and commissioning application devices and routers. OpenLNS events track other actions
that are also tracked in the IzoT Commissioning Tool event log described in the next section. These
actions include upgrading application devices; creating application devices, routers, subsystems, and
connections; deleting application devices, routers, and connections; and renaming application devices,
routers, functional blocks, and subsystems. IzoT Commissioning Tool can only process OpenLNS
events if it is active when the events are generated.
IzoT Commissioning Tool Event Log
IzoT Commissioning Tool stores every change made to an OpenLNS CT drawing by every user in a
log called the IzoT Commissioning Tool event log. The IzoT Commissioning Tool event log is kept
in the OpenLNS database so that all IzoT Commissioning Tools on a network can view the events
logged by all other IzoT Commissioning Tools on the same network—including tools that are not
active at the same time. All IzoT Commissioning Tools check the log when they open an OpenLNS
CT drawing and periodically thereafter (every 10 seconds by default), and update their copies of the
OpenLNS CT drawing based on the log entries. The IzoT Commissioning Tool event log stores up to
a fixed number of entries per drawing file (100 by default). Once the limit is reached, older entries
will be deleted to enable new entries to be added.
You can change the defaults for how frequently your IzoT Commissioning Tool checks the IzoT
Commissioning Tool event log, and the maximum number of entries it stores in the log. To change the
default synchronization settings, select the Network Properties: Synchronization options category.
Additional benefits of the IzoT Commissioning Tool event log are that it can be used by IzoT
Commissioning Tool to restore your work if you computer fails while you are updating a drawing, and
it can reduce the number of times that you need to resynchronize an OpenLNS CT drawing. You may
still need to resynchronize if applications other than IzoT Commissioning Tool make changes to the
OpenLNS database that affect an OpenLNS CT drawing but are not reported by OpenLNS events, or if
log entries are deleted.
You can view the IzoT Commissioning Tool event log, and you can export it to an XML file.
Viewing the IzoT Commissioning Tool Event Log
You can view the IzoT Commissioning Tool event log to see a summary of the changes made by IzoT
Commissioning Tool users to the objects and subsystems in an IzoT Commissioning Tool network. To
view the IzoT Commissioning Tool event log, click Add-ins, point to Synchronization, and then click
Display Event Log.
238 Maintaining Networks