Transaction Server Event Handler Configuration
To automate outbound billing processing as batches are sent from the system, configure the Transaction Server to alert the outbound billing task of specific events. The example shows a typical
configuration using the Transaction Server
Scheduler.xml file to set up the requisite event reporting:
<EVENT>
<NAME>Outbound Billing</NAME>
<TYPE>OutPresentmentGroupState</TYPE>
<EXEC>
com.ibm.paydir.ima.txsvr.event.appbridge.OutPresentmentGroupStatesEventHandler
</EXEC>
<PARAMETER name="msgType">TaskInitiation</PARAMETER>
<PARAMETER name="presStates1">SENT</PARAMETER>
<PARAMETER name="destinationID">Outbound Billing</PARAMETER>
<PARAMETER name="jmsQmgrHostname">localhost</PARAMETER>
<PARAMETER name="jmsQmgrChannel">SYSTEM.DEF.SVRCONN</PARAMETER>
<PARAMETER name="jmsUserId">pduser</PARAMETER>
<PARAMETER name="jmsPassword">pduser10</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>
</EVENT> The event configuration is given the name Outbound Billing. Any
unique event name can be used. The event is started by specific event
types:
- Outbound presentment group state
The executed event handler relays the events to the target queue
using a Messaging
API message:
com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentGroupStatesEventHandlerThe remaining parameters are used to send a message to a specified message queue on which Services Framework is listening. Table 1 describes the parameters.