Enabling IPIC recording and virtualizing in a CICS® client application

You can enable HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to record and test flows by modifying the IBM® Integration Bus CICSRequest node or the Java™ application.

About this task

A Java™ application that uses the CICS® External Call Interface (ECI) or a IBM® Integration Bus CICSRequest node can communicate directly with the CICS® Transaction Server over IP interconnectivity (IPIC).

Consider a forward bind line in the registration.xml file. For example:

   <forward bind="ritserver01.com:1234" destination="cicsserver.companyname.com:7425" type="ipic"/>

Procedure

  1. For IBM® Integration Bus CICSRequest node:
    1. Modify the CICSRequest node to refer to the Test Integrations and APIs HTTP/TCP Proxy bind address, instead the address of the actual CICS® Transaction Server.
      Using the forward bind information in the example, the URL specified in the CICSRequest node must be changed from tcp://cicsserver.companyname.com:7425 to tcp://ritserver01.com:1234
    2. Save and rebuild the flow.
    3. Start the HTTP Proxy.
    4. Rerun the application that uses the flow.
  2. For an ECIRequest
    1. Modify the ECIRequest calls to refer to the Test Integrations and APIs HTTP/TCP Proxy bind address, instead the address of the actual CICS® Transaction Server.
      Using the forward bind information in the example, the URL specified in the ECIRequest calls must be changed from tcp://cicsserver.companyname.com:7425 to tcp://ritserver01.com:1234
      Note: When using SSL based IPIC communications (when the type is specified as ipics), the URL must be specified in the form ssl://ritserver01.com:1234.
    2. Save and rebuild the application.
    3. Start the HTTP Proxy.
    4. Run the application again.