Application Integration: A Quick On-boarding Guide
Application integration is the process of connecting two or more software applications so that they can share data and communicate with each other. This can be a complex and time-consuming process, but it can also be a valuable way to improve efficiency and productivity.
If you are new to application integration, or if you are looking for a quick way to get up and running, this guide will provide you with a step-by-step process for understanding the basic concepts and applications of application integration.
- Go through Key documentation to Understand concepts of Application Integration:
- Application Integration overview: Application Integration is an Integration-Platform-as-a-Service (iPaaS) solution in Google Cloud that offers a comprehensive set of core integration tools to connect and manage the multitude of applications and data required to support various business operations
- Understand Key Concepts - This page introduces the various fundamental concepts of Application Integration:
Triggers: Events that cause an integration to start running.You can think of a trigger as an entry point to your integration—the event tied to the trigger causes the tasks associated with the trigger to run
Tasks: The basic building blocks of integrations that perform specific operations.In general, tasks can take an input, complete a unit of work using the input, and produce an output.
Forks: A fork is a control point for the outgoing edges of a task. It lets you specify the execution strategy for the immediate next tasks
Joins:A join is a control point for the incoming edges of a task. It lets you specify the execution strategy for the current task.
Edge:An edge is a connection between any two elements in an integration. The connection denotes the direction of the control flow from one element(task or trigger) to another.By using an edge along with fork and join, you can implement complex branching and conditions in your integration.
Edge Connections: Edge conditions let you specify the conditions that must be met for control of an integration to pass to the task connected by the edge. The task is run only if the specified conditions are met. Edge conditions are useful in cases where there are multiple incoming edges to a task, where each edge checks for specific conditions before the task.
Data Mapping: Data mapping is the process of extracting and standardizing data from multiple sources in order to establish a relationship between them and the related target data fields in the destination.
Variables/Integration Variables: A variable is an integration element that holds and transports data between the tasks, triggers, and edges of an integration.
Integration Versions: Allow you to collaborate track changes to an integration over time.
Data Persistence: The process of storing data that is used by an integration.
2. Learn by Hands-on Training:
- Create New Integration
- Create and configure new API Trigger
- Add and configure Tasks
- Test the integration
- Monitor Log
This simple and easy-to-understand example will help you grasp some fundamental concepts. Then, proceed with the remaining five tutorials.
- Advanced Use case: Practice with Advance Use case to get deeper understanding of various aspects of Application Integration configurations.
LinkedIn
Twitter
