Transaction Server Event Handler Configuration

To automate transmission acknowledgment processing as transmissions enter the system, configure the Transaction Server to alert the transmission acknowledgment task of specific events. The following example shows a typical configuration using the Transaction Server Scheduler.xml file to set up the requisite event reporting: 
<EVENT>
  <NAME>Transmission Acknowledgment</NAME>
  <TYPE>PresentmentGroupStateChange</TYPE>
  <TYPE>PresentmentGroupColumnChange</TYPE>
  <EXEC>com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentGroupEventHandler</EXEC>
  <PARAMETER name="msgType">TaskInitiation</PARAMETER>
  <PARAMETER name="states">LOADED,!NOTIF_SENT</PARAMETER>
  <PARAMETER name="condition">ACCEPTED,REJECTED</PARAMETER>
  <PARAMETER name="notifRequest">TRANSACK</PARAMETER>
  <PARAMETER name="destinationID">Transmission Acknowledgment</PARAMETER>
  <PARAMETER name="jmsQmgrHostname">localhost</PARAMETER>
  <PARAMETER name="jmsQmgrChannel">SYSTEM.DEF.SVRCONN</PARAMETER>
  <PARAMETER name="jmsQmgrPort">1414</PARAMETER>
  <PARAMETER name="jmsClient">true</PARAMETER>
  <PARAMETER name="jmsQmgrName">FTM.QMANAGER</PARAMETER>
  <PARAMETER name="jmsSendQueue">FXH.SERVICESFRAMEWORK.INPUT.QUEUE</PARAMETER>
</EVENT>
The event configuration is given the name Transmission Acknowledgment. Any unique event name can be used. The event is started by specific event types:
  • Presentment group loaded events
  • Presentment group column change events
The executed event handler relays the events to the target queue using a messaging API message: 
com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentGroupEventHandler

The remaining parameters are used to send a message to a specified message queue on which Services Framework is listening. Table 1 describes the parameters.

Table 1. Transmission Acknowledgment Properties
Property Description Values from the Example
msgType Messaging API message type ID TaskInitiation is required by Services Framework
destinationID Transmission acknowledgment task configuration name Use the value specified for the configuration setting during task configuration
loaded Batch (ICL) loaded state must be set before an alert is caused True indicates transmission acknowledgment is not done until the transmission is completely loaded. It filters any condition column changes that may occur during the load process.
condition Transmission condition column transitions that cause an alert Accepted, Rejected specifies an acknowledgment alert is sent when the transmission condition reaches either of the values
notifRequest Acknowledgment request type required to cause an event. For transmission acknowledgment, this value must be set to TRANSACK Specifies that acknowledgments are sent only for outbound transmissions with a value of TRANSACK in the NOTIF_REQUEST column of the database
jmsQmgrHostname Host name where the target JMS event queue manager is listening URL of the machine where the target Services Framework is running
jmsQmgrChannel Target server JMS channel name JMS channel on the target Services Framework machine
jmsQmgrPort JMS port JMS port on which the target JMS system is listening
jmsClient Target JMS system is a client system Always true unless Services Framework is running where the main WebSphere® MQ server is installed
jmsQmgrName Target JMS queue manager name JMS queue manager on the target Services Framework machine
jmsSendQueue Target JMS queue Target JMS queue where Services Framework is listening
A Transaction Server XML code sample to use as a starting point for setting up the event handler is supplied with transmission acknowledgment. It is located in the install_directory\shared\v300\pfs\Gateway\tasks\transmissionacknowledgment\samples directory.
Note: The sample must be modified to have the correct transmission acknowledgment and WebSphere MQ configuration set up before using it.