About Application Integration

Application Integration, part of the Amplify Platform, provides capabilities for integrating applications that span multiple domains, personas, endpoints and deployment architectures. Applications can be deployed in the cloud, on-premises or both. 

The following table describes the key parts of Amplify Platform that are relevant to Application Integration.

Component Description
API Builder Smart adapter for application Integration. You can use for cloud-to-ground, ground-to-cloud and ground-to-ground patterns. You can build APIs and microservices in on-premises or private cloud containerized environments.
Catalog Unified catalog for finding and reusing integration services. These include APIs, microservices, application integrations and traditional flows. The catalog simplifies and quickens the building, integration and deployment of services and apps. The catalog enables self-service integration and co-creation.
Central Manages your services and endpoints across multiple environments in the cloud or on-premises. This also secures access to your services.
Integration Builder Connects and integrates cloud applications. Provided are 170 prebuilt cloud connectors and powerful integration capabilities. You also can create your own connectors.

Application Integration and HIP

According to Gartner, a hybrid integration platform (HIP) is:

“... a framework of on-premises and cloud-based integration and governance capabilities that enables differently skilled personas (integration specialists and nonspecialists) to support a wide range of integration use cases.” (Massimo Pezzini. Gartner, 2019)

Businesses need a cohesive set of integration and governance capabilities that support their HIP use cases. These capabilities can span environments and should be selectively exposed to users based on their roles. The hybrid aspect manifests itself through support for:

  • Multiple deployment models; on premises, in a managed, public or private cloud, across multiple clouds or embedded in devices.
  • Multiple personas with focus on technical specialists and business users to enable faster completion of projects.
  • Multiple integration patterns.
  • Multiple endpoints.

The intent behind HIP is to bring integration close to where needed, and to involve the lines of business and solution partners directly. These users have diverse needs and skills. Many are nonspecialists. Application Integration has capabilities that support integrations among many applications.  Moreover, the platform is optimized for less technical users, enabling them to build and run integrations without help of technical specialists.

Business purpose

Application integration is about taking data or functions from one application to another. Businesses' use of systems and applications is growing rapidly. These are traditional enterprise resource planning and customer relationship management systems and newer on-premises and cloud applications handling transaction-based data. Application Integration enables sharing among applications and participants:

  • Simplifies and speeds up the building, integration and deployment of services and applications
  • Enables self-service integration and co-creation between constituents

Why use it

Any organization can use Application Integration for a scalable, flexible and easy-to-use solution that integrates applications and enables users to create, publish, share and reuse content across multiple personas, domains and endpoints.

  • The graphical user interface is easy for non-technical users
  • The ability to leverage JavaScript enables versatile integration patterns, an attractive solution for power users
  • The open and API-driven architecture supports solutions in the chain for continuous integration and delivery

Key concepts

Concept Description
API An application programming interface (API) is an interface to a service that enables developers to interact with it or consume it. For example, you might have a weather service that developers can use to show today's weather forecast to users of their bicycling application.
API proxy

An API proxy is a secured and governed interface for your APIs. In Central, you create an API proxy to represent your back-end API to your API consumers. Instead of interacting directly with your API, app developers interact with the API proxy. You can:

  • Change implementation of the back-end service without affecting app developers as they continue to call the API proxy.
  • Apply policies to the API proxy to manage or secure how client apps use your API.
  • Analyze usage of your APIs by client apps. You can identify and analyze failed transactions, as all traffic that flows through an API proxy is monitored and recorded.

The Catalog is where producers and consumers come together in the Amplify Platform. Producers can publish their artifacts to the Catalog. Consumers can browse the Catalog for items available for reuse and to subscribe to services.

A central, unified Catalog simplifies reuse. It promotes self-service integration and co-creation. This results in faster building, integration and deployment of services and apps. 


Connectors are prebuilt adapters for integrating cloud applications, such as Salesforce, Marketo and Slack, or adapters that you build on your own. You create connector instances from the connector templates to use in flow instances.


An endpoint represents one end of a communication channel. When an API interacts with systems, the touch points on either side are endpoints. An endpoint can include a URL of a server or service. 

Endpoints specify where APIs can access resources. They have key roles in ensuring correct functioning of the interacting software.


Flows define the movement and manipulation of data from sources through intermediaries to consumers. There are two types of flow objects: templates and instances. Flow templates are reusable workflows that describe integration steps among multiple applications along with variables and connectors. You use flow templates to create flow instances that specify variable values and connector instances. You execute flow instances.

About Integration Builder

Integration Builder is part of Application Integration, Axway's iPaaS for integrating data with virtually any endpoint in any environment. Use Integration Builder to define interfaces, called connectors, to your cloud applications. Then create integrations, or flows, between the applications. There are three primary concepts in the context of cloud application integration:

  • Connectors are pre-built API integrations that provide a consistent and simplified developer experience.
  • Mappings define and perform one-to-many transformations and normalize fields across elements.
  • Flows create workflow templates for synchronized and automated processes across systems.

Related Links