Choosing the correct ITCAM for Transactions - CICS TG data collector to install
ChrisWalker 270003FTW2 Visits (1650)
ITCAM for Transactions provides comprehensive coverage for transaction tracking using CICS Transaction Gateway (CICS TG). If you aren't aware of the latest level of support – including the tracking of flows over IPIC protocol – have a read
If are are looking to install the data collector to monitor transactions through CICS TG for Multiplatforms, you will find there are two versions to choose from, depending on if you are planning to run in 32 bit or 64 bit mode. For the current release (V7.3 fixpack 1) on Windows, for example the images to choose from are:
So, which one should you choose to install? This depend on what CICS TG components you are tracking in your environment. If you are running in the 3-tier “remote” mode with a Gateway daemon on your non-z/OS machine, you will definitely need the 32 bit version to track transactions through the Gateway daemon, even if you are running on 64 bit hardware. This is because the CICS TG on all operating systems except V9.0 on z/OS runs under a 32 bit JVM and this, not the hardware determines the version to install.
If you have deployed the CICS Resource Adapters into a WebSphere Application Server (WAS) then the choice is dependent on the JVM you have chosen to run WAS under. Since WAS V6.1, you have been able to choose to run under a 32 bit or 64 bit JVM. If you are unsure which mode your server is running, check using the WAS Admin Console. Look under the properties of the server instance and you will see a check-box called “Run in 64 bit JVM mode”.
What if, for example, you have a test system with both a WAS instance running under a 64 bit JVM and a Gateway daemon (which must run under a 32 bit JVM). You will need to install both version but beware that the default install path for both versions are the same. So, choose appropriate alternatives to ensure they don't conflict or overwrite each other.
If you are running your CICS TG or WAS on z/OS then both the 32 bit and 64 bit libraries are delivered as part of the same FMID so all that is needed to do is ensure all steps in the documented instructions are followed so that external links are created to access the libraries provided for both addressing modes.
Full details of how to configure and deploy can be found in the Information Center.