Getting started with an IMS test scenario

Edit online

It is recommended that you start with this basic test scenario to get the core components in place and working.

Before you begin

Review the Prerequisites and system preparation.

About this task

Complete the following installation and configuration tasks to instrument the IMS MQ application.

In this example, the client MQ application puts a message to an IBM Message Queue (MQ). The IBM MQ then sends the message to IMS MQ Bridge, which is responsible for delivering the message to the IMS MQ application for processing. To trace the IMS MQ application, you need to make sure the MQ messages contain the trace correlation data in the MQRFH2 header.

Procedure

  1. Validate the distributed trace flow
    1. (Prerequisite) Install and configure Instana backend and the user interface
      You need an Instana backend before you trace distributed flows. If you have not already set up Instana backend and the user interface, choose the type of backend that suit your needs and install it based on instructions of IBM Instana Observability documentation.
    2. (Prerequisite) Install the Instana Host Agent
      Install the Instana Host Agent on the machine where your distributed test application is running. For more detailed instructions, see IBM Instana Observability documentation.
    3. Install and enable IBM MQ Tracing on IBM MQ hosts
      Install IBM MQ Tracing user exits. For more detailed instructions, see IBM Instana Observability - IBM MQ tracing and Optional IMS MQ Bridge Configuration.
      Note: To trace the IMS application, the MQ messages must contain trace correlation data in the MQRFH2 header of the IBM MQ message.
    4. Verify distributed application on the Instana user interface
      Verify that the application is showing up on the Instana user interface (application dependency map). Verify the host machine where the application is running has an agent reporting.
      Note: Before you deploy IBM Instana Observability for z/OS, the Instana 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.
  2. 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.
  3. 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.
  4. Install and configure the Z APM Connect tracing component
    For this test scenario, only the Z APM Connect IMS Data Producer is required. Follow the instructions in Installing and configuring Z APM Connect IMS Data Producer to install and configure Z APM Connect IMS Data Producer.

Results

Your application is successfully instrumented with Instana for z/OS. 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.

What to do next

Follow instructions in Installing and configuring Z APM Connect components to complete further installation and configuration.