What's new for CICS and CICS TG users in ITCAM for Transactions V7.3 FP1
ChrisWalker 270003FTW2 Visits (2179)
Note: this entry was cross-posted in the System z community of Service Management Connect.
December 2012 saw the release of ITCAM for Transaction V7.3 FP1. This release contains a number of significant enhancements for users of CICS Transaction Server (CICS) and CICS Transaction Gateway (CICS TG) to extend the transaction tracking capability. ITCAM for Transactions provides an end-to-end view of your transaction flows with response times. For some monitored components, such as CICS, you can link directly into OMEGAMON workspaces once a bottleneck has been identified to quickly resolve the issue.
The following is a brief overview of the new capabilities with respect to CICS and CICS TG:
WebSphere HTTP client to CICS Web Support trackingTracking of inbound HTTP traffic handled by CICS Web Support originating from a WebSphere Application Server is now supported. Provided the HTTP traffic flows through the CICS transaction CWBA no further configuration is required for upgrading ITCAM for Transaction users within CICS.
IPIC-based transaction tracking between CICS TG and CICSIP Interconnectivity (IPIC) was introduced in CICS V3 and CICS TG V7 as a protocol for connecting to CICS and between CICS regions via a TCP/IP connection that overcomes the limitations of the existing COMMAREA-based protocols. ITCAM for Transactions V7.3 FP1 provides the support for flows using IPIC connections for any transaction type.
Support is provided for both 3-tier “remote mode” (for example, WebSphere Application Server or stand-alone application to a Gateway daemon to CICS) and 2-tier “local mode” (For example, WebSphere Application Server or stand-alone application to CICS) deployments of CICS TG if the connection is made over IPIC.
Transaction tracking through CICS TG Gateway daemons on multiplatforms
As a result of adding the IPIC support to ITCAM's CICS TG data collector, full transaction tracking in now possible for users that have CICS TG Gateway daemons deployed on multiplatforms (that is, non-z/OS operating systems). The CICS TG data collector is a small installable component that is deployed on every machine running a CICS TG and generates transaction tracking data to be correlated with similar events generated by other data collectors, such as CICS and, if you are monitoring WebSphere Application Server instances, from ITCAM for Application Diagnostics.
Pseudo-node interaction support for flows that cannot be trackedWhere flows cannot be correlated, either because the interaction between the domains is not supported (for example, a flow between CICS TG and CICS over SNA protocol) or one part of the interaction has not been instrumented (for example, the CICS TG Transaction Tracking data collector is enabled but the CICS data collector is disabled), details of the connection can be displayed using pseudo nodes.
Pseudo-nodes can play an important part in providing aggregated flow response times and identify flows to or from clients that cannot be instrumented (for example non-Java ECI V2 clients) and flows between CICS TG components and TXSeries server instances.
Support for latest levels of CICS and CICS TGAll of the above enhancements are available on all supported levels of CICS, CICS TG and WebSphere Application Server, including the recently released CICS Transaction Server V5.1 and CICS TG V9.0. For CICS TG V9.0 support is also available for users that now chose to deploy their Gateway daemons within a 64-bit JVM.
Full details of how to configure and deploy can be found in the Information Center.