Configure the Transaction Server for the Sample Task

The configured PresentmentGroupEventHandler sends the sample task the unique ID associated with any file that was successfully loaded through the Gateway Server.

The unit of work information sent by the handler contains the following information:
  • Unit of work type, which is PRESENTMENT_GROUP_ID
  • Unit of work value, which is the unique key assigned to the file loaded

The definition is one of many different ways to post work to a configured task in the Services Framework.

Configuration Steps

  1. Modify the Transaction Server Scheduler.xml file by adding the event definition. A sample is shown here:
    <EVENT>
      <NAME>Transmission Acknowledgment - Presentment Group Condition Changed</NAME>
      <TYPE>PresentmentGroupLoaded</TYPE>
      <TYPE>PresentmentGroupColumnChange</TYPE>
      <EXEC>
        com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentGroupEventHandler
      </EXEC>
      <PARAMETER name="msgType">TaskInitiation</PARAMETER>
      <PARAMETER name="destinationID">Sample Task</PARAMETER>
      <PARAMETER name="condition">accepted,rejected</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>
      <PARAMETER name="jmsReplyQueue">FXH.TRANSSERVER.INPUT.QUEUE</PARAMETER>
      <PARAMETER name="jmsReplyTimeout">2500</PARAMETER>
      <PARAMETER name="jmsPriority">9</PARAMETER>
    </EVENT>
  2. Save the Scheduler.xml file
  3. Start the Transaction Server.
  4. Start the Gateway Server.
    Note: It is assumed the components that perform ingestion are already installed and configured to receive inbound transmissions.
  5. Load a transmission.
After the transmission is ingested and accepted, the Transaction Server sends a message to the Services Framework queue with the unit of work information about the transmission loaded. The message posted requests to initiate a configured task called sample task. The information is known by the Transaction Server from the following parameters:
<PARAMETER name="msgType">TaskInitiation</PARAMETER>
<PARAMETER name="destinationID">Sample Task</PARAMETER>
Note: The parameter destinationID value of "Sample Task" must exactly match the task configuration's configuration value to prevent the Transaction Server from sending messages to Services Framework that are not properly delivered to the sample task.

For more information about the handler, see Transaction Server User's Guide.