Glossary

This glossary provides definitions of commonly used terms found throughout the product documentation.

Basic Authentication

Basic Authentication is a method for an HTTP user agent (e.g., a web browser) to provide a username and password when making a request. When Basic Authentication is set up for Xtract Universal.iQ services, users are required to provide credentials before executing the service.

Connections

Connections define how Xtract Universal.iQ connects to external systems. There are two types of connections:

• Sources: SAP systems from which data is retrieved, e.g., SAP S/4HANA, SAP BW, etc.
• Destinations: Systems where data is sent, e.g., http-json and Amazon S3.

Connection Type

The connection type refers to the source or destination of the connection. Example: SAP source connections use the connection type SAP RFC, connections to an Amazon S3 destination use the connection type Amazon S3, etc.

Destination

A destination represents a connection to a target environment. Xtract Universal.iQ allows you to write data directly into various supported target environments. For more information, see Destinations.

Image

In a container context, an image is a lightweight, standalone, executable package that contains everything needed to run Xtract Universal.iQ, including the application code, runtime, system libraries, and dependencies. Container images are used to create and run container instances.

Body Parameters

Body Parameters are used in the HTTP request body of a service call to pass structured data to services that accept body payloads. For more information, see Parameter Types.

Custom Parameters

Custom Parameters are user-defined parameters that can be used to filter SAP data before writing the data to the destination. They are used in Table, Function Module / BAPI, and Transaction services. Custom parameters are be passed to services at runtime.

MCP Server

The MCP Server exposes Xtract Universal.iQ services to AI agents and automation tools through the Model-Context-Protocol (MCP) endpoint. By enabling the MCP Server, you can trigger service runs using natural language. For more information, see MCP Server.

Query Parameters

Query Parameters are appended to the service URL. Xtract Universal.iQ uses them to pass input values to services without a request body. For more information, see Parameter Types.

Request Body

The Request Body is the payload sent in the HTTP body of a service call. They are used to pass structured data to services when running them.

Response Body

The Response Body is the payload returned by an Xtract Universal.iQ service in the HTTP response. It contains the data or status information from the service run.

Services

Services are the main entities in Xtract Universal.iQ. When called, Xtract Universal.iQ services query the data defined in the service type of the service from the assigned SAP source. The data is then returned to the caller in the HTTP response of the service. A list of all services is displayed in the Services menu of Xtract Universal.iQ.

Service Type

Service Types define what data Xtract Universal.iQ accesses in SAP and how to retrieve it. Xtract Universal.iQ offers multiple service types to cover a wide range of scenarios, see Services.

Source

A source represents a connection to an SAP system. For more information, see SAP Connection.

Swagger/OpenAPI

OpenAPI is the specification used by Xtract Universal.iQ services. The services are implemented in the Swagger 2.0 format. For more information, see OpenAPI Specification.

Transactions

Transaction is the name of an service type supported by Xtract Universal.iQ, see Transactions. In this context, transactions refer to SAP transaction codes that can be executed via Xtract Universal.iQ.

Transport Layer Security (TLS)

TLS is a security protocol to ensure a safe data transfer when calling Xtract Universal.iQ services via an HTTPS connection. For more information, see Settings - Transport Layer Security.

Volume

In a container context, a volume stores persisting data outside of a container. Data inside volumes are stored on the host machine of the container and remain available even after the container is stopped or removed. Multiple containers can share volumes for data exchange. For information on directories used in Xtract Universal.iQ containers, see Container Directories.