Process Work Request
The Transaction Server scheduler must be configured to notify Payment Repair when batches are available to process. When configuring the scheduler event, the user specifies the state, or states, a batch must be in for it to be processed by Payment Repair. When a batch reaches the specified state(s), Transaction Server sends a presentment has validation errors message to the WebSphere® MQ queue on which Payment Repair is configured to listen.
The scheduler causes Payment Repair to be notified of each batch that is loaded. Payment Repair checks to see if there are any repairable payments in the batch and, if there are, the work is ingested for operator repair. If there are no repairable payments, Payment Repair places the batch in the repaired state.
Sample scheduler XML
Configure a PresentmentStateChange event in the Transaction Server to send a presentment has validation errors message to Payment Repair. For more information about configuring the Transaction Server scheduler, see Events and communication with external applications.
The events differentiate between the forward and return work type. In the event stanza, the bruleWorkflow parameter is used to distinguish between forward and return batches. When Gateway calls the Business Rules Server, it passes in the Business Rules workflow name to use. This workflow name is stored with the batch, and is used to distinguish between the forward and return work event stanzas in the event definition. If more than one workflow name may apply, specify them as a list of workflow names separated by commas.
<EVENT>
<NAME>Payment Repair - Forward Presentment</NAME>
<TYPE>PresentmentStateChange</TYPE>
<TYPE>PresentmentColumnChange</TYPE>
<TYPE>PresentmentGroupColumnChange</TYPE>
<EXEC>
com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler
</EXEC>
<PARAMETER name="workType">Repair</PARAMETER>
<PARAMETER name="msgType">Presentment_Has_Validation_Errors</PARAMETER>
<PARAMETER name="presStates1">LOADED</PARAMETER>
<PARAMETER name="destinationID">Fwd_Payment_Repair</PARAMETER>
<PARAMETER name="bruleWorkflow">ChkFwdWorkflow</PARAMETER>
<PARAMETER name="condition">ACCEPTED</PARAMETER>
<PARAMETER name="pending">N</PARAMETER>
<PARAMETER name="group.sourceId">2</PARAMETER>
<PARAMETER name="presLevel">PROC</PARAMETER>
<PARAMETER name="jmsQmgrHostname">localhost</PARAMETER>
<PARAMETER name="jmsQmgrChannel">SYSTEM.DEF.SVRCONN</PARAMETER>
<PARAMETER name="jmsQmgrPort">1414</PARAMETER>
<PARAMETER name="jmsQmgrName">FTM.QMANAGER</PARAMETER>
<PARAMETER name="jmsSendQueue">FXH.PAYMENTREPAIR.INPUT.QUEUE</PARAMETER>
<PARAMETER name="jmsReplyQueue">FXH.TRANSSERVER.INPUT.QUEUE</PARAMETER>
</EVENT>
<EVENT>
<NAME>Payment Repair - Return Presentment</NAME>
<TYPE>PresentmentStateChange</TYPE>
<TYPE>PresentmentColumnChange</TYPE>
<TYPE>PresentmentGroupColumnChange</TYPE>
<EXEC>
com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler
</EXEC>
<PARAMETER name="workType">Repair</PARAMETER>
<PARAMETER name="msgType">Presentment_Has_Validation_Errors</PARAMETER>
<PARAMETER name="presStates1">LOADED</PARAMETER>
<PARAMETER name="destinationID">Rtn_Payment_Repair</PARAMETER>
<PARAMETER name="bruleWorkflow">ChkRtnWorkflow</PARAMETER>
<PARAMETER name="condition">ACCEPTED</PARAMETER>
<PARAMETER name="pending">N</PARAMETER>
<PARAMETER name="group.sourceId">2</PARAMETER>
<PARAMETER name="presLevel">PROC</PARAMETER>
<PARAMETER name="jmsQmgrHostname">localhost</PARAMETER>
<PARAMETER name="jmsQmgrChannel">SYSTEM.DEF.SVRCONN</PARAMETER>
<PARAMETER name="jmsQmgrPort">1414</PARAMETER>
<PARAMETER name="jmsQmgrName">FTM.QMANAGER</PARAMETER>
<PARAMETER name="jmsSendQueue">FXH.PAYMENTREPAIR.INPUT.QUEUE</PARAMETER>
<PARAMETER name="jmsReplyQueue">XH.TRANSSERVER.INPUT.QUEUE</PARAMETER>
</EVENT>