Notification messages properties

The user has the ability to generate notification messages that can be sent to a monitoring system as confirmation of transmission status. Gateway generates two versions of notification messages, versions 1.0.0 and 2.0.0. Both versions are in XML format. Version 1.0.0 adheres to notification.xsd schema, which is in the install_directory\shared\v409\pfs\Gateway\xml directory. Version 2.0.0 is richer in content and adheres to the notification200.xsd schema, which is in the same folder. The notificationMsgLvl configuration parameter determines the version of notification message to generate. Depending on the type of transmission processing and the version of the notification message, a notification message is sent on transmission pull, transmission receipt, transmission begin, transmission complete, transmission send, transmission error, batch (ICL) begin, and batch (ICL) end.

Table 1 shows the properties that control the generation and distribution of the notification message.

Table 1. Notification messages properties
Keyword	Values/Example	Description
notificationMsgMode	blank or FILE or MQ or BOTH	Mode to use for transmitting the notification message. The value can be: Blank - Notification message is not generated File - Notification message is placed in the folder specified by the notificationMsgPath keyword with the same name as the incoming transmission and with an extension equal to the value specified by the notificationMsgExt keyword MQ - When the notification message level is version 2.0.0, notification messages are published to the WebSphere® MQ queue manager for notification using the publish and subscribe model. The topic that the messages are published to is IBMPayDir/Event. The user must create the topic and the subscription. For more information about configuring WebSphere MQ, see WebSphere MQ Configuration Properties. When the notification message level is version 1.0.0, the message is sent on the queue defined in the notifMqSendQueue property. Both - File and MQ are used as delivery methods
notificationMsgPath	/opt/ibm/ftm/runtime-processing/inbound/dta/notifications	The path in which to place the notification messages. When end of day processing runs, Gateway Server deletes all files in this path which are older than fileKeepDays.
notificationMsgExt	.msg	The extension to put on the file containing the notification message.
notificationMsgLvl	2.0.0	Determines the version of the notification message to generate. Valid values are: 2.0.0 - default; adheres to the notification200.xsd schema 1.0.0 - for backward compatibility; adheres to the notification.xsd schema When the notification message mode is MQ, this property also determines the method that is used by MQ to send the notification.