Glossary

Look up terms and definitions that you find in IBM® WebSphere® Transformation Extender products and documentation.

This glossary includes terms and definitions for IBM WebSphere Transformation Extender.

The following cross-references are used in this glossary:

See refers you from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
See also refers you to a related or contrasting term.

A B C D E F G H I J L M O P R S T U V W

A

A2A: See application to application.
activity: An action designed to achieve a particular business process. An activity is performed on a set of targets on a specific schedule.
adapter: An intermediary software component that allows two other software components to communicate with one another.
adapter object: An object used in the TX Programming Interface that represents a resource adapter.
API: See application programming interface.
Applicability Statement 2 (AS2): An EDI protocol for securely exchanging data over the Internet, by using HTTP as a transport.
application programming interface (API): An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program.
application to application (A2A): A data transformation from the output of one application to the input of another application.
AS2: See Applicability Statement 2.
audit log: A log file containing a record of system events and responses.

B

BAPI: See Business Application Programming Interface.
big endian: A format for storage or transmission of binary data in which the most significant value is placed first. See also little endian.
Boolean: Characteristic of an expression or variable that can only have a value of true or false.
bound component: In the Type Designer, a component for which each occurrence of the data can be identified without considering the context in which that occurrence is placed.
bound type: In the Type Designer, a type whose data object can be identified without considering the context in which that data object is placed.
BPML: See Business Process Modeling Language.
BPML activity: A step in a business process that provides directions for how data should be handled.
Business Application Programming Interface (BAPI): A programming interface that is used to access SAP databases from with SAP or other development platforms. BAPI is used to achieve integration between the R/3 System and external applications and legacy systems.
Business Process Modeling Language (BPML): An XML-based language that describes business processes designed by the Business Process Management Initiative (www.bpmi.org).

C

card: In the Map Designer, a data object. There are two types of map cards: input and output.
card object: An object used in the TX Programming Interface that represents an input or output card of a map in program memory.
category: A type class that is used to organize types in a type tree in the Type Designer. Categories organize types that have common properties.
certificate: In computer security, a digital document that binds a public key to the identity of the certificate owner, thereby enabling the certificate owner to be authenticated. A certificate is issued by a certificate authority and is digitally signed by that authority.
choice type: A group type with a subclass equal to choice that is used to define a selection from a set of components. A choice type defines a choice group, which is valid when the data matches one of the components in the choice group.
class: A basic unit of the classification hierarchy used in the Type Designer. There are three classes: item, group, and category.
classification hierarchy: The hierarchy of a type tree in the Type Designer. The deeper the subtype, the more specific the data characteristics are. See also compositional hierarchy.
cloud: See cloud computing.
cloud computing (cloud): A computing platform where users can have access to applications or computing resources, as services, from anywhere through their connected devices. A simplified user interface and application programming interface (API) makes the infrastructure supporting such services transparent to users.
code list: One or many dynamic pairs of code values that contains sender code and receiver code. Each code pair has one description and up to four additional codes relating to the pair.
code list table: A repository for lists of codes that can further define fields.
compiled map component: An Integration Flow Designer object that references an executable map in compiled file format.
complete type name: The name of a type that represents its hierarchical structure within a type tree, which includes the names of all the types in the path from the root type down.
component rule: An expression about one or more components, which is defined in the Type Designer. A component rule is used for validating data and specifies what must be true for the data that is defined by that component to be valid.
composite: A group of related data elements used in EDI transactions.
compositional hierarchy: A hierarchy in which the composition of the data is reflected in the structure of the group type in the group window. See also classification hierarchy.
contracted component: In the Integration Flow Designer, a component that does not display the sources and targets associated with it. See also expanded component.
correlation: Data that enables a user to record document-specific correlation parameters generated during translation, by the correlation service, or by document tracking functions.

D

data element

A unit of data that cannot be divided. An example is the data element "age of a person" with values consisting of all 3-decimal digit combinations.

data object

A portion of data in a data stream that can be recognized as belonging to a specific type.

data structure

The composition of the data, including repeating sub-structures, nested groupings, sequences, and choices.

decode

To convert data by reversing the effect of some previous encoding.

de-enveloping

The process of removing one or more envelopes from a document or a set of documents.

delimited format

Data that has data objects that are separated by delimiters.

delimiter

A character, such as comma or tab, used to group or separate units of text by marking the boundary between them.
A flag that is formed by a character or a sequence of characters to group or separate items of data by marking the beginning and end of a unit of data. The delimiter is not a part of the flagged unit of data.

dequeue

To remove items from a queue. See also enqueue.

distinguishable types

Types that do not have common data objects.

document envelope

A structure that is applied to a document to prepare it for exchange between trading partners.

document type definition (DTD)

The rules that specify the structure for a particular class of SGML or XML documents. The DTD defines the structure with elements, attributes, and notations, and it establishes constraints for how each element, attribute, and notation can be used within the particular class of documents.

DTD

See document type definition.

E

EDI: See electronic data interchange.
EDI loop: A group of consecutive EDI segments that repeat together in an EDI document definition. There is no object type in Data Interchange Services that defines an EDI loop on its own. EDI loops are logically defined within an EDI document definition.
EDI message: See EDI transaction.
EDI transaction: In X12 EDI Standards, a group of logically related data that makes up an electronic business document, such as an invoice. The layout of an EDI transaction is described by an EDI Document Definition in Data Interchange Services.
electronic data interchange (EDI): The exchange of structured electronic data between computer systems according to predefined message standards.
element: A component of a document, such as an EDI, XML, or ROD record. An element can be a simple element or a compound element.
encode: To convert data by the use of a code in such a manner that reconversion to the original form is possible.
enqueue: To put a message or item in a queue. See also dequeue.
envelope: A combination of header, trailer, and control segments that define the start and end of an individual EDI message. Each envelope contains a header segment and a trailer segment, which separate the envelope from other envelopes and provide information about the contents of the envelope.
executable map: A compiled map.
execution settings: Settings that influence how a component behaves at execution time. These settings are compiled into the map file or system file. Many of these settings compiled into the map can be overridden (or partially overridden) using execution commands and options.
expanded component: A component that displays the sources and targets that are associated with it in the Integration Flow Designer. See also contracted component.
explicit format: A format that relies upon syntax to separate data objects. Each data object can be identified by its position or by a delimiter in the data. Delimiters will also appear for missing data objects. See also implicit format.
expression: A statement about data objects. Expressions are a combination of literals, object names, operators, functions, and map names. Component rules are expressions that evaluate to either TRUE or FALSE. Map rules are expressions that evaluate to data to produce the desired output.
external link: In the Integration Flow Designer, solid lines displayed in a system definition diagram that visually represent the data flow between two map components.

F

fixed syntax: A group whose components have a fixed size. Each component is padded to a fixed size or its minimum and maximum content size values are equal.
functional acknowledgment: An electronic acknowledgment returned to the sender to indicate acceptance or rejection of EDI documents.

G

global transaction management (GTX): The monitoring of transactions that can include operations on two or more different data sources. This feature enables databases or servers to be returned to a pre-transaction state if an error occurs. Either all databases and servers are updated or none are. The advantage of this strategy is that databases and servers remain synchronized and data remains consistent.
GPM: See Graphical Process Modeler.
Graphical Process Modeler (GPM): A stand-alone graphical interface tool that is used in Sterling B2B Integrator to create and modify business processes. The GPM converts the graphical representation of business processes to well-formed BPML (source code) and saves the effort of writing code.
group: A complex data object that consists of components.
GTX: See global transaction management.

H

hypervisor: Software or a physical device that enables multiple instances of operating systems to run simultaneously on the same hardware.

I

identifier attribute

An attribute that can be assigned to one component to identify a collection of components, when creating type trees and defining components of a group. An identifier attribute is used during data validation to determine whether a data object exists.

image

See virtual image.

implicit format

A format that defines a group type whose data objects are distinguishable by content, not syntax. Implicit format relies on the properties of the component types. Unlike explicit format, if delimiters separate data objects, they do not appear for missing data objects. See also explicit format.

initiator

A syntax object in a data stream that signals the beginning of a data object. For example, if a record begins with an asterisk (*), the asterisk would be the record’s initiator.
In distributed queueing, a program that requests network connections on another system.

input card

In the Map Designer, a component that contains the complete definition of input for the map, including information such as source identification, retrieval specifics, and the behavior that should occur during processing.

interchange

The exchange of information between trading partners. Also a set of documents grouped together, such as EDI documents enclosed within an EDI envelope.

internal link

In the Integration Flow Designer, a solid line displayed by an expanded map component that visually represents the source and target of the map.

item

A simple data object that does not consist of other objects. An item type is represented by a blue dot next to the type name in the type tree.

J

Java: An object-oriented programming language for portable interpretive code that supports interaction among remote objects. Java was developed and specified by Sun Microsystems, Incorporated.
Java Database Connectivity (JDBC): An industry standard for database-independent connectivity between the Java platform and a wide range of databases. The JDBC interface provides a call level interface for SQL-based and XQuery-based database access.
Java EE: See Java Platform, Enterprise Edition.
Java Message Service (JMS): An application programming interface that provides Java language functions for handling messages.
Java Platform, Enterprise Edition (Java EE): An environment for developing and deploying enterprise applications, defined by Oracle. The Java EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multitiered, web-based applications. (Oracle)
Java runtime environment (JRE): A subset of a Java developer kit that contains the core executable programs and files that constitute the standard Java platform. The JRE includes the Java virtual machine (JVM), core classes, and supporting files.
Java Secure Socket Extension (JSSE): A Java package that enables secure Internet communications. It implements a Java version of the Secure Sockets Layer (SSL) and Transport Layer Security (TSL) protocols and supports data encryption, server authentication, message integrity, and optionally client authentication.
Java SE Development Kit: The name of the software development kit that Sun Microsystems provides for the Java platform.
Java virtual machine (JVM): A software implementation of a processor that runs compiled Java code (applets and applications).
JDBC: See Java Database Connectivity.
JMS: See Java Message Service.
JRE: See Java runtime environment.
JSSE: See Java Secure Socket Extension.
JVM: See Java virtual machine.

L

literal: A symbol or a quantity in a source program that is itself data, rather than a reference to data.
little endian: A format for storage or transmission of binary data in which the least significant value is placed first. See also big endian.
local server: A predefined server that designates the current computer to run the Integration Flow Designer.

M

map component: An Integration Flow Designer object that encapsulates a reference to an executable map, along with its execution settings. There are three types of map components: source, compiled, and pseudo.
map object: An object used in the TX Programming Interface that represents an instance of a map in the program memory.
map rule: An expression that evaluates to data and produces the required output. A map rule is entered on an output card in the Map Designer and cannot be longer than 32KB.
member: In the Type Designer, a single occurrence of a component in a group in a type tree. If a component has a range, each occurrence of that component might be referred to as a member of a series.
message header: The part of a message that contains control information such as a unique message ID, the sender and receiver of the message, the message priority, and the type of message.
message queue: A named destination to which messages can be sent until they are retrieved by programs that service the queue.
messaging API: A programming interface that enables an application to send and receive messages and attached files over a messaging system.
messaging middleware: Software that provides an interface between applications, allowing them to send data back and forth to each other asynchronously. Data sent by one program can be stored and then forwarded to the receiving program when it becomes available to process it.
messaging system: Software used to deliver electronic messages.
metadata: Data that describes the characteristics of data; descriptive data.

O

optional component: Within a group type, a component that can be defined to represent a data object that is not required to be present in the data. The component range maximum specifies how many occurrences of the data object might optionally exist.
output card: In the Map Designer, a card that contains the complete definition of an output for the map including information such as target identification, destination specifics and the behavior that should occur during processing.
override: An execution setting that overrides default source and target settings of a map.

P

pad character: A character used to fill empty space. For example, in a database application, a field that is ten characters in length that has the word "file" in it contains four text characters and six pad characters
partition: To divide a type into subtypes that are mutually exclusive.
partitioned type: A type whose subtypes are distinguishable or mutually exclusive.
pattern: A reusable solution that encapsulates a tested approach to solving a common architecture, design, or deployment task in a particular context.
persistence level: A level that determines the degree of detail written to the database as a business process runs. Decreasing the persistence level increases the business process performance at the cost of full tracking for each step of the business process.
predefined business process: A business process that is ready to use upon installation of Sterling B2B Integrator.
primary document: A document that the services in a business process act on or in relation to. A primary document is usually the document passed to a business process by the initiating adapter.
process control information: Map component settings that can be changed at run time by specifying overrides at the command line, in a command file, or by configuring the Launcher.
process data: Data that is accumulated in an XML document about a business process during the life of the process. Activities in the process add elements to the process data and use components of the process data to complete configured processing tasks.
propagation: The point at which the properties of a type are inherited by its subtypes.
property: A characteristic of an object that describes the object. A property can be changed or modified. Properties can describe an object name, type, value, or behavior, among other things.
pseudolink: In the Integration Flow Designer, dotted lines manually drawn in a system definition diagram that visually represent a data flow relationship between two map components that has not yet been determined precisely.
pseudomap component: An Integration Flow Designer object that is a placeholder for an executable map that has not yet been implemented.

R

range

The number of consecutive occurrences of the component in the data stream. The range is composed of two numbers separated by a colon.
The categorization of an attribute into different segments.

relative type name

The name of a type relative to another type. Relative type names are used when defining components, syntax items, and comment types.

release character

The character that indicates that a separator or delimiter is to be used as text data instead of as a separator or delimiter. The release character must immediately precede the delimiter.

required component

A component that can be defined within a group type to represent a data object that must be present in the data. The component range minimum specifies how many occurrences of the data object are required.

resource adapter

Map input and output data sources that are used to retrieve and route data. Resource adapters provide access to databases, files, messaging systems, and other data sources and targets. Each adapter includes a set of adapter commands that can be used to customize its operation.

restart attribute

An attribute that specifies that processing of the input data should continue even though a data object of the component is invalid. The restart attribute provides instructions for handling errors encountered in a data stream and can be assigned to a component within a group type.

role-based security

Security that provides access rights to certain files, business processes, web templates, and features, according to the permissions associated with the user account.

rollback

The process of restoring data that was changed by an application program or user.

root type

The type from which all other types stem. The root type represents the data objects of all the types in the tree.

row

The horizontal component of a table, consisting of a sequence of values, one for each column of the table.

run map

An executable map that is called using the RUN function.

S

SDK

See software development kit.

Secure FTP

An FTP protocol that uses Secure Sockets Layer (SSL) protocol.

segment

A portion of a profile. The format of each segment is defined by a template.
An EDI logical unit of information. EDI segments are made up of data elements and composites. Segments are delimited; their components are separated by a delimiter.

series

The consecutive occurrences of a component. In map rules, the [ ] characters denote an indexed member of a series.

server definition

A definition for a computer that hosts a command server, to which systems under development in the Integration Flow Designer can be assigned as the intended execution server.

service-oriented architecture (SOA)

A conceptual description of the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services and connections between components.

simple type name

The type name that appears next to the type icon in the type tree.

sized attribute

An attribute that can be assigned to one or more components within a group type, whose value specifies the size, in bytes, of the component immediately following it.

SOA

See service-oriented architecture.

SOAP

A lightweight, XML-based protocol for exchanging information in a decentralized, distributed environment. SOAP can be used to query and return information and invoke services across the Internet. See also web service.

software development kit (SDK)

A set of tools, APIs, and documentation to assist with the development of software in a specific computer language or for a particular operating environment.

source map component

An object that references an executable map within a source map file.

stream object

An object used in the TX Programming Interface that permits overrides to the loaded map input and output specifications.

subflow

A sequence of processing steps, implemented using message flow nodes, that is designed to be embedded in a message flow or in another subflow. A subflow must include at least one Input or Output node. A subflow can be executed by a broker only as part of the message flow in which it is embedded, and therefore it cannot be deployed.

subsystem component

An Integration Flow Designer object that references another system which a user has defined.

subtree

A branch of a type tree that includes a type and all of the subtypes that stem underneath it.

subtype

A type that extends or implements another type; the supertype.

supertype

In a type hierarchy, a type that subtypes inherit attributes from.

syntax object

One or more characters used as separators between portions of data. A syntax object can be a number separator, a delimiter, a terminator, an initiator, or a release character.

system

A collection of referenced executable maps that are organized into a unit.

system definition diagram

The graphical representation of a system viewed within a system window in the Integration Flow Designer. A user can interact with system definition diagrams to design systems.

system window

A window in the Integration Flow Designer in which system definition diagrams are created, maintained, and displayed.

T

terminator: A syntax object that signifies the end of a data object. For example, a carriage return or line feed at the end of a record might be the record's terminator.
transaction set: The basic business document in EDI data. Transaction sets are enclosed in an envelope that separates one transaction set from another. Groups of transaction sets that are functionally related are enclosed in a functional group envelope.
translation object: A source map that has been compiled to provide instructions for translating from one format to another in a way that can be interpreted by the translator.
transmission type: The largest object in an EDI type tree. A transmission might include many interchanges from or to many trading partners.
transport adapter: An adapter (such as an HTTP Adapter) that is used with an encoding/decoding adapter to support various protocols (for example, SOAP) in a transport-independent way. The transport adapter is used to transport the data either from the source or to the destination.
transporting: A method of conveying data using a specified adapter following either an encode or decode command.
trigger: A mechanism that detects an occurrence and can cause additional processing in response.
tuple: See row.
type: The definition of a data object or set of data objects that is graphically represented in a type tree in the Type Designer.
type tree: In the Type Designer, the graphical representation of the definition and organization of data objects.

U

unbound set: The set of all possible types of data that might be listed last in a group.
Unicode: A character encoding standard that supports the interchange, processing, and display of text that is written in the common languages around the world, plus many classical and historical texts.
Uniform Resource Indicator (URI): A unique address that is used to identify content on the web, such as a page of text, a video or sound clip, a still or animated image, or a program. The most common form of URI is the web page address, which is a particular form or subset of URI called a Uniform Resource Locator (URL). A URI typically describes how to access the resource, the computer that contains the resource, and the name of the resource (a file name) on the computer.
URI: See Uniform Resource Indicator.
user account: The login directory and other information that gives a user access to the system.
UTF-8: Unicode Transformation Format, 8-bit encoding form, which is designed for ease of use with existing ASCII-based systems. The CCSID value for data in UTF-8 format is 1208.

V

variable component name: A component of a group type that includes the literal at the end of the name because it represents more than one type. The literal ANY acts like a wild card, which represents any type whose name could appear in that place.
virtual image (image): The operating system and product binary files that are required to create a virtual system pattern.
virtual machine: An abstract specification for a computing device that can be implemented in different ways in software and hardware.

W

watch: A map, including the set of events that initiate it, as defined from the Integration Flow Designer.
web service: A self-contained, self-describing modular application that can be published, discovered, and invoked over a network using standard network protocols. Typically, XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available, and UDDI is used for listing what services are available. See also SOAP, Web Services Description Language.
Web Services Description Language (WSDL): An XML-based specification for describing networked services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. See also web service.
workbench: The user interface and integrated development environment (IDE) in Eclipse and Eclipse-based tools such as IBM Rational Application Developer.
WSDL: See Web Services Description Language.