Improved method to process WebSphere MQ messages in CICS, CKTI (Task Initiation)
KailasV.Shetye 270001QGDN Visits (3978)
TXSeries for Multiplatforms v8.1 Open Beta has introduced CKTI (Task Initiation) that spawns a task in TXSeries upon receiving a WebSphere MQ trigger. This improves upon existing conventional methods in that it brings enhanced integration with better control and management for handling trigger conditions.
The way it works is, CKTI starts a CICS transaction when a WebSphere MQ trigger message is read. When a message is put onto an application message queue, a trigger is generated by WebSphere MQ upon meeting trigger conditions. Queue Manager writes a trigger message in the Initiation queue defined for the application queue in DEFINE PROCESS command. User data defined on trigger queue is also included. CKTI starts a CICS transaction specified in WebSphere MQ using DEFINE PROCESS (that connects triggers to application queues in WebSphere MQ). CKTI passes important information related to WebSphere MQ queues along with user data to the application as it initiates the transaction, which allows applications to identify which queue has generated a particular trigger etc. A single application program can also handle multiple queues as well as all the data comes in through CKTI.
Following picture narrates the working of CKTI in a pictorial manner:
Overall, CKTI improves TXSeries integration with WebSphere MQ. Some of the benefits it brings along are,