Understanding of Adapter Document Definition (ADD) | Oracle Integration
What is the Adapter Document Definition (ADD)?
The previous article explains the complete process of building a custom adapter using RAB in Oracle Integration. This article focuses on Adapter Document Definition (ADD), the only file where you define your adapter’s design and runtime implementation.
To publish an adapter to Oracle Integration, you must define the specifications and functions of your adapter in a JSON metadata file, termed the Adapter Document Definition.
An adapter definition document typically describes the design and implementation of an adapter and contains information about its behavior and properties.
Using the RAB extension, you can quickly create an ADD from a Postman collection of an application’s APIs (or an OpenAPI document describing a set of application APIs), and then you can modify the adapter definition document manually according to your requirements.
The ADD file contains multiple sections the describe the design and implementation of your adapter.
The following section explains all the sections contained in the ADD:
Section: 1 -> info
It includes the general information and branding of your adapter:
Section: 2 -> schema
This section defines the structure of fields that appear in the mapper in Oracle Integration.
Section: 3 -> connection
This section defines the connection parameters and security policies supported by the adapter.
Section: 4 -> triggers
This section defines the events that the adapter can receive to start an integration.
Section: 5 -> action
This section defines the operations that can be implemented against the invoking application. Actions provide a user-centric encapsulation of the operations available and exposed in the invoking application such as get user, get todos, get user by id, etc.
Section: 6 -> categories
This section defines the grouping of actions and triggers for a better user experience.
Section: 7 -> flow
This section defines the implementation logic that drives the adapter. Flows are modeled using a subset of the constructs that are supported in the Serverless Workflow specification of the Cloud Native Computing Foundation (CNCF) project.
Look at the following video to know more details about the Adapter Document Definition (ADD) of RAB.
If you found this article valuable, we would greatly appreciate your support through likes, comments, and shares. Additionally, we invite you to subscribe to our YouTube channel for more insightful videos. Don’t miss out on our latest updates – be sure to click the subscribe button to stay informed about our newest content.
Further readings:
Understanding of Rapid Adapter Builder (RAB)
Process of Building Adapter using Rapid Adapter Builder (RAB)
About the Salesforce REST Adapter
Leveraging Salesforce REST adapter to push accounts to Database
