...
There are two components of an Integration definition:
...
Application
...
| Table of Contents | ||||
|---|---|---|---|---|
|
Application
...
‘Application’ represents the third-party application or system to be integrated using the Web Services/APIs. The integrations are defined at the tenant level with connectivity and authentication mechanisms mechanism details, that are used by the Automation workflow to connect to the target system. Here we define the name of the application (like ISM, SDM), and integration type (for example, REST, SOAP).
Instance
...
The application instance represents the specific environment of the target systems where the task is executed. The App Instance helps to set the target environment for the execution of the web service operations. Here we define the Web service, authorization type, and other Global parameters required to connect to the target system. The App instance is selected in the Automation Workflow to create the Web Service Operation to be executed in the target system.
Operations
Operations are the actions to be performed on the target system. These represent the functions that are exposed by the Target system’s API. As a Workflow designer, you can configure and add the operations in workflows to perform a specific task in the target environment.
There are two ways to create Integration Operations for your Workflow:
Mule Operations- Build the Workflow in Mulesoft Connectors with Anypoint studio and Import to Luma Automation
Rest Operations - Custom operations built using REST APIs