Welcome
Reference Guide
This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
Recording Studio
With Test Integrations and APIs, you can record events (messages or database interactions) sent to and from the system under test. Use Recording Studio to control what parts of the system should be recorded. These parts could be specific parts of the system infrastructure or specific services using that infrastructure. You can then use the recorded events as a source of tests and other interactions with the system. In Recording Studio, you can record the traffic over a number of different transports.
Using the Recording Studio
Use the Recording Studio to monitor and capture events, and use captured events for tests and other artifacts for use within your Test Integrations and APIs project.
Playing back recorded events
You can select recorded events and replay them in the Recording Studio perspective. You can specify the pacing speed with which the messages are published (as-fast-as-possible, defined interval, or as-original). Rules and functions in the Rule Cache can be used to make basic modifications to message contents as they are published. Playback works on events that have been exported and re-imported.

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test Integrations and APIs (Test Integrations and APIs). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System requirements
This document includes information about hardware and software requirements for HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 2024.03 (11.0.1).
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
Administrator Guide
This guide describes how to install HCL DevOps Test Integrations and APIs (Test Integrations and APIs). After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
Test Manager Guide
This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
Troubleshooting
While working with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), you might encounter some problems that you can easily troubleshoot.
Reference Guide
This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
- DevOps Test Integrations and APIs overview
  This section provides an overview of HCL DevOps Test Integrations and APIs (Test Integrations and APIs), including information about projects and files, the Test Integrations and APIs user interface, environments, and project settings and preferences.
- Architecture School
  Use the Architecture School perspective to build a system under test by using the logical, physical, and synchronization views. You can also use this perspective to manage the schemas available in your project.
- Recording Studio
  With Test Integrations and APIs, you can record events (messages or database interactions) sent to and from the system under test. Use Recording Studio to control what parts of the system should be recorded. These parts could be specific parts of the system infrastructure or specific services using that infrastructure. You can then use the recorded events as a source of tests and other interactions with the system. In Recording Studio, you can record the traffic over a number of different transports.
  - Monitor Configuration view
    After you set up the system under test for recording, you can choose what you want to record in the Recording Studio. You can do this by selecting Monitor Configuration (in the upper-left portion of the Recording Studio perspective) that specifies what you want to record. It shares space with the Triggers view. To show the Monitor Configuration view, click the Monitor Configuration tab at the bottom of the view.
  - Events Monitors Properties view
    The Event Monitor Properties view, located directly below the Event Monitors and Triggers view, displays information about the operation that is selected in the Event Monitors view.
  - Events view
    The Events View displays events that are captured by enabled event monitors. The perspective at the right of Recording Studio is divided into two views: a list of captured events on top and details for the selected event at the bottom. Within the view, you can send a response to selected events or run and manage triggers.
  - Triggers view
    A trigger is essentially a publisher that is used to send an event to the system under test. Existing triggers are displayed in the Triggers view, which is in the upper-left portion of the Recording Studio perspective. It shares space with the Event Monitors view. To show the Triggers view, click the Triggers tab at the bottom of the view.
  - Using the Recording Studio
    Use the Recording Studio to monitor and capture events, and use captured events for tests and other artifacts for use within your Test Integrations and APIs project.
    - Capturing events
      You can use the Recording Studio to capture events. The Events View can be used with the Event Monitors view to select events and record them. You can define the destination for recorded events by using tags in the message header properties of selected operation.
    - Recording from an ad hoc monitor
      Create an ad hoc monitor to record events from a transport rather than from an operation.
    - Creating an operation from recorded events
      You can save events, including information from the monitor on which they were recorded, as a new operation.
    - Recording HTTP and HTTPS traffic
      Use the HTTP proxy in the HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to record all HTTP and HTTPS traffic that is routed through the proxy.
    - Recording TCP traffic
      The enables Test Integrations and APIs to record general TCP traffic that is routed through the proxy or to route TCP traffic to stubs automatically when they start instead of routing traffic through the live system.
    - Recording Java™ Message Service (JMS) traffic
      You can use Test Integrations and APIs to record JMS Traffic.
    - Recording MQ telemetry traffic
      You can use Test Integrations and APIs to record MQ telemetry transport traffic by connecting to the MQ telemetry transport broker that you want to use and subscribing directly to topics communicated from that broker.
    - Recording RabbitMQ transport traffic
      The RabbitMQ proxy recording feature (this is not HTTP based) enables HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to record RabbitMQ transport traffic that is routed through the proxy.
    - Recording WebSphere® MQ and TIBCO EMS Server events
      Recording for WebSphere® MQ transports is carried out in a different way than other transports. The WebSphere MQ transport does not provide a native method for watching a queue in a non-destructive manner. In other words, events cannot be captured without taking them off the queue.
    - Recording and virtualizing RFCs
      You can record and virtualize SAP application resources. If you are testing a Java™ application that uses the SAP Java Connector (JCo) to make remote function calls (RFCs) to an SAP application server, use Test Integrations and APIs to record and virtualize those calls.
    - Configuring the Recording Studio settings of logical SAP application servers
      You can record SAP application resources by configuring a logical SAP application server to record IDocs. Use the Recording Studio perspective of Test Integrations and APIs to record incoming and outgoing intermediate documents (IDocs).
    - Configuring subscribe operations to record IDoc types
      You can record and virtualize SAP application resources by creating a subscribe operation for a logical SAP application server and configuring it to record a specific IDoc type.
    - Creating event monitors for SAP recordable resources
      Before you can start a recording session, you must create an event monitor in Recording Studio. Do this task after specifying the Recording Studio settings of a logical SAP application server to record intermediate documents (IDocs), or after configuring a subscribe operation for a logical SAP application server to record IDoc types.
    - Recording SQL events
      When the Test Integrations and APIs JDBC proxy is installed, you can use Test Integrations and APIs and Test Virtualization to record SQL events that are executed against databases from applications that use JDBC. There are two methods of selecting a database for recording: Architecture School method and Recording Studio method. Both methods achieve the same result but the Architecture School method is a more direct method.
    - Recording FIX traffic
      You can use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) and an HTTP/TCP proxy to record FIX traffic.
    - Recording Java™ method calls
      To record Java™ method calls, you use the Java application that you want to record, an instance of the Java virtualization agent as applicable installed into the application, and a Java method transport in Test Integrations and APIs.
    - Playing back recorded events
      You can select recorded events and replay them in the Recording Studio perspective. You can specify the pacing speed with which the messages are published (as-fast-as-possible, defined interval, or as-original). Rules and functions in the Rule Cache can be used to make basic modifications to message contents as they are published. Playback works on events that have been exported and re-imported.
  - Data masking concepts, methods, and types
    Use Test Integrations and APIs to add a data mask to particular fields in recorded messages that may contain sensitive data. When you add a mask, you prevent that sensitive data from appearing in any assets created from those messages, such as tests, test data, stubs, and data models.
- Test Factory
  The Test Factory perspective is one of the main areas in Test Integrations and APIs. You can create all the tests and the required artifacts/data to support them.
- Test Lab
  You use the Test Lab to execute test assets, repair tests, and open test assets for editing directly from this perspective. You can execute all of the tests, test suites, and stubs that are created in Test Factory.
- Results Gallery
  You use the Results Gallery perspective to view an execution summary and detailed coverage, and error reports for executed test suites and for test cases that were executed within a suite or as part of a test cycle.
- Messages
  Test Integrations and APIs can publish and subscribe to messages as part of a test. A message normally consists of two parts: a header and a body. The header usually adheres to a predefined logical construction, while the structure of the body can be more arbitrary.
- Schemas
  Test Integrations and APIs can handle many types of content. For the product to be able to interpret the variety of content types, it must associate a content format description, or schema with the content.
- Database resources, connections, and bindings
  Test Integrations and APIs can interact with any database that supports connectivity through the JDBC specification. These interactions can be used to extract or update data where necessary, and test data sets can be taken directly from database table content.
- Identity stores and SSL
  An identity store can group a collection of one or more certificates that can be used in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to validate and authenticate connections that use SSL. After you create an identity store, you can use it to enable SSL communications in various messaging transports.
- Scripting within tests and stubs
  You can use scripts in Test Integrations and APIs that include the Test Integrations and APIs legacy scripting language, ECMAScript (such as JavaScript™), Chai, or any third-party scripting language that you install.
- External tools
  Test Integrations and APIs is primarily GUI-based, but you can also run or view tests, suites, and stubs outside of the Test Integrations and APIs.
- Test actions
  Actions are the building blocks of a test. A test consists of a series of steps and each step is an action. Actions can be defined for tests and stubs.
- Formatting and parsing date-time patterns
  For some fields in Test Integrations and APIs, you can define patterns for date-time formatting. Pattern letters are repeated, as their number determines the exact presentation of the date-time information that they represent.
- The Add Numbers service
  The Add Numbers service, included with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), provides a simple way to generate messages that you can observe with topology discovery or capture in Recording Studio.
Security Considerations
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for product documentation.

Playing back recorded events

You can select recorded events and replay them in the Recording Studio perspective. You can specify the pacing speed with which the messages are published (as-fast-as-possible, defined interval, or as-original). Rules and functions in the Rule Cache can be used to make basic modifications to message contents as they are published. Playback works on events that have been exported and re-imported.

Procedure

In Test Integrations and APIs, open the Recording Studio perspective.
In the Event Monitors view, select the events to be played back.

Note: Only the request and publish events (that is, outbound events) in the selection are replayed. Reply and subscribe events are ignored.
Click Playback button on the toolbar of the Events View window.
In the Playback dialog:
1. Select an environment from the llist.
2. Optional: To terminate the playback when an error occurs, select Stop on error.
3. Optional: To configure the speed at which you want the events to play back, select Enable pacing. You can either set the Pacing mode to the same gaps with which the events were originally recorded or specify an interval (in seconds) according to your needs.
4. Optional: To run rules from the Rule Cache on the selected events, select Run rules on events.

Results

The selected events are played back.