Introduction to Trigger Definitions

While building your adapter, you can specify the trigger model that the adapter supports and define other trigger-related information in the triggers section of the adapter definition document.

Types of Triggers

A trigger is a mechanism that initiates an integration flow when a specific event occurs in an external system. While designing an adapter for Oracle Integration, you can model two types of triggers:

Webhook trigger: In this trigger type, external applications automatically send new data to Oracle Integration when a specific event occurs. See What Is a Webhook Trigger.
Polling trigger: In this trigger type, Oracle Integration actively checks for changes in an external application. See What Is a Polling Trigger.

Overview of Designing a Trigger

Using the adapter definition document, you can design a trigger object that can receive or retrieve events occurring in external applications and services. A trigger definition contains several components beyond just event handling. Here are all the components of a trigger definition:

Component	Description
Identity	The identity of the adapter. It contains properties such as display name, description, and group. See Trigger Properties and Sample Code.
Trigger contract	The message that is received (or retrieved) from an external application as a trigger. See What Is a Webhook Trigger and What Is a Polling Trigger.
Subscription registration	The component that allows the modeling of the webhook registration. See Understand Event Subscription. Note: This applies only to webhook triggers.
Security	The security schemes that validate if the events are received (or retrieved) from the right application and according to the security policy defined in the connection. See Understand Trigger Security.
Configuration	The component that allows the modeling of trigger configuration, whenever necessary. In design time, the integration developer can configure the trigger using the options available or mechanism defined. See Understand Configuration Scenarios.
Runtime implementation	The component that transforms the incoming data to a human-readable format (mapper-friendly format). See Runtime Implementation of Triggers. Note: This applies only to webhook triggers.