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.
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.
PL/I source file overview
Use PL/I source files in Test Integrations and APIs to test PL/I data files or the applications that produce and use them.

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.
- 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.
  - Adding a schema
    You can add a single schema or a directory that contains multiple schemas to the Schema Library view after which you can apply the schema to messages in your tests. You can specify the type of schema to add or use Test Integrations and APIs to determine the type.
  - ISO 8583 schemas: Overview and structure
    Test Integrations and APIs supports the ISO 8583 standard for messages that originate in financial transaction cards.
  - Adding SWIFT schemas
    When you want to apply SWIFT schema to messages in your tests, you can add additional SWIFT schemas to the Schema Library in the Architecture School perspective of Test Integrations and APIs.
  - COBOL Copybooks overview
    Use COBOL Copybooks in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to test COBOL data files or the applications that produce and consume them.
  - PL/I source file overview
    Use PL/I source files in Test Integrations and APIs to test PL/I data files or the applications that produce and use them.
    - Adding PL/I source file schemas
      You can add a PL/I source file schema to the Schema Library in Test Integrations and APIs Architecture School perspective.
    - Applying PL/I source file schemas to messages
      After you add a PL/I source file schema to Test Integrations and APIs, you can apply the schema to messages in applicable test actions.
  - Creating a DFDL schema
    You can use the DFDL schema utility that is provided with Test Integrations and APIs to create a DFDL schema file and apply it to messages. This utility helps you to quickly create a schema with valid format and to specify elements and values by using the DFDL editor.
  - ISO 20022 schema overview
    Test Integrations and APIs supports the ISO 20022 standard, which is the next generation messaging standard for the Society for Worldwide Interbank Financial Telecommunication (SWIFT).
  - Protocol Buffer overview
    Protocol Buffer (also known as protobuf) is a Google framework for efficiently serializing objects for transfer, typically between network endpoints.
  - Creating a Web URL schema
    You can create a Web URL schema to use with REST services by adding URLs to the Schema Library.
  - Creating file schemas
    File schemas can be used to define the contents of one or more files that you intend to write to (publish) or read from (subscribe) in Test Integrations and APIs tests.
  - Applying schemas and formats to messages
    Built-in or custom message formats can be applied to any message within Test Integrations and APIs in the same way that schemas can be applied.
  - Applying Integra message handlers
    If you migrated to Test Integrations and APIs from Solstice Integra Suite, you can apply Integra message handlers to Test Integrations and APIs messages.
  - GraphQL schema overview
    Test Integrations and APIs supports the use of either the built-in GraphQL schemas or the GraphQL schemas that you import into Test Integrations and APIs when you want to test a GraphQL endpoint.
  - SWIFT messages
    At any given time, Test Integrations and APIs uses a single version of the Society for Worldwide Interbank Financial Telecommunication (SWIFT) message format standard.
  - Changing schemas
    Over time, it is likely that a schema in use for message construction will change. To update the schema in the Test Integrations and APIs project, use the Synchronization view in Architecture School.
  - Analyzing schemas
    You can analyze certain schema resources, such as XSD or WSDL documents, after they are imported into Test Integrations and APIs.
  - Record layouts
    You can use record layouts in Test Integrations and APIs to define a file schema to process and validate messages that use a customized schema or format.
- 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.

PL/I source file overview

Use PL/I source files in Test Integrations and APIs to test PL/I data files or the applications that produce and use them.

You can add PL/I source files to Test Integrations and APIs and apply them to messages. PL/I source files provide a format that is meaningful to the system under test.

PL/I data files do not contain information about their own organization and record structure. If you have a PL/I data file, but no program capable of writing or reading this file, you cannot correctly interpret the data that the file contains.

The information that describes the physical layout of program data, that is, how the records and fields relate to each other, is stored in a PL/I source file. This file is included in all of the applications that process the file.

PL/I source files are named with .pli and .inc extensions, and typically include one or more DCL structures. These structures can be made available within Test Integrations and APIs as message schemas that can be used to create or parse the data in files or messages.

PL/I source file schemas can be applied to any of the following fields:

Byte array fields, in messages where you can use the Byte Array formatter
Bytes message types, set within the message body when you are using any of the JMS providers
Text messages, which you can format according to the applied schema.

Supported PL/I statements

The following DCL types are supported:

String types, including BIT, CHAR, WIDECHAR, GRAPHIC
Arithmetic types, including (SIGNED/UNSIGNED) (FIXED/FLOAT) BIN/DEC REAL/COMPLEX
Picture string type
Array (multi-dimensioned)
Structure
Union