Getting started with a CICS test scenario
It is recommended that you start with this basic test scenario to get the core components in place and working.
Before you begin
About this task
In this example, the Tomcat Enterprise Edition (TomEE) web server sends HTTP requests to the CICS subsystem to access the application.
Validate the distributed trace flow
- (Prerequisite) Install and configure AppDynamics Controller and the user interface
- Verify distributed application on the AppDynamics user interface Verify that the application is showing up on the AppDynamics user interface.Note: Before you deploy IBM Z® APM Connect , the AppDynamics user interface does not know which z/OS systems and subsystems the transactions are calling out. Only a node is displayed with the hostname of the IBM zSystems that the CICS is running on.
- Install and configure Z APM Connect Distributed Gateway Follow the instructions in Installing, configuring, and managing Z APM Connect Distributed Gateway to install and configure Z APM Connect Distributed Gateway.
- Install and configure Z APM Connect Base Follow the instructions in Installing and configuring Z APM Connect Base to install and configure Z APM Connect Base.Note: Make sure Z APM Connect Base is started successfully and connected to Z APM Connect Distributed Gateway. See Validating Z APM Connect Base installation and configuration to validate the status.
- Install and configure the Z APM Connect tracing component For this test scenario, only the Z APM Connect CICS Data Producer is required. Follow the instructions in Installing and configuring Z APM Connect CICS TS Data Producer to install and configure Z APM Connect CICS Data Producer.
Your application is successfully instrumented with IBM Z APM Connect. What was previously a mainframe black box, surfaces one more layer of visibility as transactions hop between the web server and the CICS subsystem. You can also view the key details for individual transactions like response time, call count, ABEND codes, and more.