Event Notification functionality supports the generation of XML messages that reflect specific Events in Transportation Manager. If these XML messages are generated by the CISFlatFileAdapter using CIS-XML Format, publication to CIS is also supported. This allows events that have occurred in Transportation Manager to be shared with other applications.
By default, the content of the XML messages is extensive.
The Define Event Content for CIS function allows administrators to customize the content of messages in CIS-XML Format. This is accomplished by exposing the structure of each XML Message as maintained in Event Attributes table and allowing message components to be included / excluded by the CIS-XML Format as needed.
The revised XML messages (CIS-XML Format) must remain valid with reference to the published XML Schemas (xsds). This means that the structure of these messages must not be altered (that is, parent-child relationships must remain intact).
The content of messages in XML Format are not configurable.
The Event Content proposed using the Define Event Content for CIS function can only be activated via a "refresh" of the eventdeflist.xml file. See the Event Notification Guide for more information.
Servers need to be re-started in order for the revised contents of eventdeflist.xml to be used in Event Notification Message construction.
Configuring the CIS-XML Format of Event Notification Messages serves only to reduce the volume of Transportation Manager data that will be sent to other applications. From a strictly functional point of view, it is unnecessary.
Furthermore, only a single CIS-XML Format will be supported and if multiple subscribers exist it will be necessary to ensure that the final CIS-XML format can satisfy all of them. Under these circumstances it may be necessary to use the original CIS-XML Format (Long Format) or to groom the format so that this includes the specific event attributes required by all subscribers.