Glossary

This glossary provides terms and definitions for App Connect.

A

account: A collection of the credentials, such as username and password, that App Connect needs to connect to your applications. You can configure accounts on the App Connect Applications and APIs page or when you add a connector to a flow. For more information, see Connecting to accounts.
action: A defined task that an application performs on an object as a result of an event. Typical actions include creating, updating, retrieving, and deleting objects.
API: See application programming interface (API).
API flow: A flow that implements an application programming interface (API). An API flow contains a request, actions for one or more target applications, and a response. For more information, see Types of flows.
App Connect Designer: The user interface where you create event-driven and API flows. You can also deploy flows from the Designer. For more information, see Creating flows in App Connect Designer.
App Connect Enterprise Toolkit: See IBM App Connect Enterprise Toolkit.
application: One or more software programs that provide a function in direct support of specific business processes. App Connect connects your applications like Salesforce, Marketo, and Amazon services.
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.
Automation Explorer: See IBM Automation Explorer.

B

BAR file: See broker archive file.
basic authentication: An authentication method that uses a username and a password.
basic connector: A technology connector such as HTTP, REST, and IBM MQ, which you can use to integrate custom, home-grown applications, including traditional solutions. See also premium connector.
batch process: A process that retrieves many records (bulk data) from an application and processes the records in parallel. For more information, see Using batch processing in IBM App Connect.
broker archive file: The unit of deployment for integrations that you develop in the IBM App Connect Enterprise Toolkit. Also known as a BAR file. The BAR file contains message flows and other user-provided files that the message flows might need at run time. If you're on the VPC hours plan, you also export flows from App Connect Designer as BAR files to deploy in the App Connect Dashboard.

C

callable flow: A flow that can call another flow directly. Both flows can be in the same location, or one can be in App Connect while the other is in IBM App Connect Enterprise. For more information, see Splitting processing with callable flows.
CDK: See Connector Developer Kit (CDK).
certificate authority: A trusted third-party organization or company that issues digital certificates. The certificate authority typically verifies the identity of the individuals who are granted the unique certificate.
community connector: A connector that another App Connect develops and shares in the IBM Automation Explorer. For more information, see Adding or creating community connectors.
configuration: A set of attributes that define how an integration runs when it is deployed. For example, an Accounts configuration provides the credentials to connect to your application accounts. Or a Policy project configuration contains policies that control the behavior of the message flows at run time. For more information, see Configuration types.
connector: A component that provides data connectivity and extraction capabilities for external applications. The connectors are listed on the Applications and APIs page.
Connector Developer Kit (CDK): A tool to create and test a custom connector to use in App Connect. You can share the connectors that you develop with other users in the IBM Automation Explorer.

D

dashboard

The user interface where you can deploy and manage integrations if you're on the VPC hours plan.
The dashboard of the Designer user interface where you create, edit, and export event-driven and API flows that you create in Designer.
The dashboard of the Dashboard user interface where you view and manage integration runtimes and deployed integrations if you're on the VPC hours plan.

For more information, see IBM App Connect components and resources.

deployment

The process of transferring integrations and associated resources from a local development environment into an operational, or runtime, environment. For more information, see Deploying integrations.

Designer

See App Connect Designer.

E

endpoint: An external application that your flow interacts with. An event in a source endpoint (application) triggers your flow to complete actions in one or more target endpoints (applications).
event: A change of state or content in a source application that triggers your flow to complete actions in one or more target applications. A typical event is when an object is created, updated, or deleted.
event-driven flow: A flow that is triggered by an event that occurs in a source application. For more information, see Types of flows.

F

flow: An integration artifact that includes one or more steps (or nodes) that automate the movement of data between a source and target. For more information, see Types of flows.
flow run: A unit of measurement that is used to determine the licensing cost of App Connect Enterprise as a Service. A flow run occurs when an event triggers part of a flow to complete one or more actions. If you're on the flow runs plan, you're charged for the number of flow runs that are triggered. For more information, see Pricing plans.

I

IBM App Connect Enterprise Toolkit: A graphical user interface that is used to develop message flows in App Connect Enterprise. For more information, see Developing integrations in the IBM App Connect Enterprise Toolkit.
IBM Automation Explorer: A repository of connectors for use in App Connect flows. The Automation Explorer includes IBM-developed connectors and community connectors, which other App Connect users develop in the Connector Development Kit.
integration: One or more flows that automate processes by connecting your applications. An integration can consist of one or more flows that are created in IBM App Connect Enterprise Toolkit, or an event-driven or API flow that is created in App Connect Designer.
integration runtime: A set of resources that are used to run an integration in App Connect. If you're on the flow runs plan, your integrations are deployed automatically to an integration runtime. Event-driven and API flows are deployed on a shared integration runtime. An integration that you develop in App Connect Enterprise and upload as a BAR file is deployed to a new integration runtime. If you're on the VPC hours plan, you must create and configure an integration runtime to run your integrations. For more information, see Deploying integrations on the VPC plan.
integration server: A set of resources that provides an isolated runtime environment for a set of deployed messages flows and resources in App Connect Enterprise. When you use callable flows to split processing between App Connect and App Connect Enterprise, you need an integration server to route data between the flows. For more information, see Splitting processing with callable flows.
invocation: The activation of a flow, API, or process. An invocation is another name for a flow run. For more information, see Pricing plans.

J

JSONata: A lightweight query and transformation language for JSON data. JSONata uses sophisticated query expressions with built-in operators and functions and minimal syntax to manipulate and combine data. For more information, see Applying JSONata functions to transform your data.

K

keystore: In security, a file or a hardware cryptographic card where identities and private keys are stored, for authentication and encryption purposes. Some keystores also contain trusted or public keys.

L

latency: The time that elapses between when a flow is triggered and when it completes processing. For an event-driven flow, latency is the time between when the flow receives the event and when the flow completes. For an API flow, latency is the time between when App Connect receives the request and when App Connect sends the response.
local environment: A tree structure in the App Connect Enterprise message assembly where you can store information while the message flow processes the message.

M

mapping: The process of defining the relationship between components to enable the flow of data from a data source to a target system. For more information, see Mapping your data by inserting references.
message flow: A sequence of processing steps that run when an input message is received. A message flow is created in the App Connect Enterprise Toolkit by connecting a series of message flow nodes that each represents a set of actions that define a processing step. The connections in the flow determine which processing steps are carried out, in which order, and under which conditions.
message flow node: A processing step in a message flow that is developed in the App Connect Enterprise Toolkit (also called a message processing node).

N

node: A processing step in a message flow, event-driven flow, or API flow.

P

parser: A program that interprets user input and determines what to do with the input.
premium asset pack: A pack of three premium connectors that you purchase to use in your App Connect flows.
premium connector: Connectors that integrate business-critical enterprise applications like SAP, Workday, and Salesforce. See also basic connector.
private network: A network that a private organization or corporation establishes or operates for users within that organization or corporation. You must create a private network connection in App Connect to connect to applications on a private network or to configure callable flows between App Connect and App Connect Enterprise.

Q

queue manager: A component of a message queuing system that provides queuing services to applications.

R

resource unit: An independent measure of a resource that is managed by, processed by, or related to the use of a product. For App Connect Enterprise as a Service, the resource is a flow run.

S

SaaS: See software as a service.
social learning: The aggregation of field mappings in anonymous users' flows to provide mapping suggestions to all users based on common actions. For more information, see Mapping Assist overview.
source application: The first application in an App Connect flow. When an event occurs in the source application, it triggers the flow to complete one or more actions in the target applications.
software as a service: A model of software deployment where software that includes business processes, enterprise applications, and collaboration tools, are provided as a service to customers through the cloud.
switch server: A special type of integration server that routes data between App Connect and App Connect Enterprise. For example, you use a switch server to route data between callable flows.

T

target application: An application in your App Connect flow where you want to complete one or more actions when an event occurs in your source application.
throttling: The act of cutting off or reducing input or output.
toolbox: A collection of tools that you can add to App Connect flows when you create them. Tools are provided for parsing, batch processing, logging, and conditional processing of data.
Toolkit: See App Connect Enterprise Toolkit.
trigger: A mechanism that detects an occurrence and can cause other processing in response. When an event occurs in a source application, that event triggers a flow to complete one or more actions in target applications.
truststore: In security, a storage object, either a file or a hardware cryptographic card, where public keys are stored in the form of trusted certificates, for authentication purposes in web transactions. In some applications, these trusted certificates are moved into the application keystore to be stored with the private keys.

V

validation

The checking of data or code for correctness or for compliance with applicable standards, rules, and conventions. When you create, edit, or import flows in App Connect Designer, App Connect automatically validates each step in the flow. A warning icon is displayed for any validation errors, which include unconnected or disconnected accounts or incomplete mandatory fields.

virtual private cloud

A virtual network that is tied to a private user account and isolated from other networks in a public cloud. Only authorized users can access virtual private cloud resources, which include virtual servers, storage, and subnets.

virtual processor core

A unit of measurement that is used to determine the licensing cost of IBM products. A VPC hour represents each hour that a VPC is available to App Connect Enterprise as a Service. See also flow run.

VPC

See virtual private cloud.
See virtual processor core.