Oracle Fusion Cloud Technical

Oracle Integration Cloud Adapter Types: Trigger, Invoke and Connectivity Explained

Pinterest LinkedIn Tumblr

Oracle Integration Cloud (OIC) simplifies communication between cloud applications, on-premises systems, and third-party services. One of its most important components is the adapter, which enables integrations to connect with different applications and exchange data without requiring extensive custom coding.

Understanding Oracle Integration Cloud adapter types, particularly Trigger and Invoke adapters, is essential for designing effective integrations. It is also important to understand connectivity options such as the Connectivity Agent, which allows OIC to communicate with systems hosted behind an organization’s firewall.

This guide explains how Trigger and Invoke adapters work, the difference between them, common adapter examples, and how connectivity is established in OIC.

What Are Adapters in Oracle Integration Cloud?

Adapters in Oracle Integration Cloud are predefined connection components that simplify communication between OIC and external applications, databases, APIs, and enterprise systems.

Instead of developing a custom connection for every application, developers can use adapters to configure endpoints, authentication, operations, and data exchange.

Adapters help with:

  • Connecting Oracle applications such as Oracle Fusion Cloud ERP and HCM.
  • Integrating third-party SaaS platforms.
  • Exchanging data through REST and SOAP APIs.
  • Connecting to databases and on-premises applications.
  • Supporting event-driven and scheduled integrations.
  • Managing request and response data through integration mappings.

An adapter is generally selected when creating a connection in OIC. That connection can then be used in an integration as a trigger, an invoke, or both, depending on the adapter’s capabilities.

1. What Is a Trigger Adapter in OIC?

A Trigger adapter is used to initiate an integration. It defines how an integration receives information from an external application or system.

When an external application sends a request or an event reaches the configured endpoint, the trigger starts the integration.

For example, when a new employee is created in an HR application, an event or request can initiate an OIC integration to synchronize the employee information with another system.

How Does a Trigger Adapter Work?

A typical trigger flow follows these steps:

  1. An external application sends a request or generates an event.
  2. The configured trigger endpoint receives the request or event.
  3. OIC starts the integration.
  4. The integration processes and maps the incoming data.
  5. The integration may call other applications using Invoke adapters.
  6. OIC returns a response when the integration pattern and endpoint support one.

Examples of Trigger Adapters

Common examples include:

  • REST Adapter: Exposes REST endpoints that external applications can call to start an integration.
  • SOAP Adapter: Exposes SOAP-based services for systems that communicate using SOAP messages.
  • Oracle ERP Cloud Adapter: Can receive supported business events from Oracle Fusion Cloud ERP.
  • Oracle HCM Cloud Adapter: Supports supported business-event and application integration scenarios involving Oracle HCM Cloud.

The available trigger capabilities depend on the adapter, application, and integration pattern.

When Should You Use a Trigger Adapter?

Use a Trigger adapter when:

  • An external application needs to send data to OIC.
  • An application event should initiate a business process.
  • You need to expose an API for external systems.
  • An integration should start when a supported business event occurs.

2. What Is an Invoke Adapter in OIC?

An Invoke adapter is used when an integration needs to communicate with an external application or service.

It allows OIC to send requests, execute operations, retrieve information, or update records in another system.

For example, when an employee record is received through a REST Trigger, an Invoke adapter can call Oracle Fusion HCM to create or update the corresponding employee record.

How Does an Invoke Adapter Work?

A typical Invoke flow includes:

  1. The integration receives data through its trigger or scheduled process.
  2. OIC processes the incoming information.
  3. The integration maps the required fields.
  4. The Invoke adapter sends a request to the target application.
  5. The target application processes the request and returns a response.
  6. OIC handles the response and continues the integration flow.

Examples of Invoke Adapters

Common Invoke adapter examples include:

  • Oracle ERP Cloud Adapter: Performs supported operations such as submitting business requests or working with ERP business objects.
  • Oracle HCM Cloud Adapter: Supports operations involving HCM resources and services.
  • REST Adapter: Calls REST APIs to retrieve, create, update, or delete data, depending on the API.
  • SOAP Adapter: Invokes SOAP-based web services.
  • Database Adapter: Executes supported database operations and procedures.
  • FTP Adapter: Transfers files between OIC and an FTP or SFTP server.

When Should You Use an Invoke Adapter?

Use an Invoke adapter when:

  • You need to send data from OIC to another application.
  • An integration must retrieve information from an external system.
  • You want to update records in Oracle Fusion applications.
  • You need to call a third-party REST or SOAP API.
  • Your integration requires database operations or file transfers.

3. Difference Between Trigger and Invoke Adapters

Trigger and Invoke adapters have different responsibilities within an integration. A Trigger starts the integration, whereas an Invoke allows the integration to communicate with another application or service.

Parameter Trigger Adapter Invoke Adapter
Main purpose Starts an integration Calls an external application
Direction Receives requests or events Sends requests to a target
Role Entry point Outbound communication
Typical use Receiving employee data Creating an employee record
Configuration Defines the inbound endpoint or event Defines the target operation
Example REST Trigger REST Invoke

Practical Example: Employee Data Synchronization

Consider a company that wants to synchronize employee information from an external HR application to Oracle Fusion HCM.

The integration can work as follows:

  • Trigger: REST Adapter receives employee information from the source HR application.
  • Transformation: OIC maps the employee fields into the required target format.
  • Invoke: Oracle HCM Cloud Adapter calls the appropriate HCM operation.
  • Response: OIC processes the response and records the integration outcome.

This example demonstrates how Trigger and Invoke adapters work together to complete an end-to-end integration.

4. What Is Connectivity in Oracle Integration Cloud?

Connectivity refers to the communication path between OIC and the applications or systems involved in an integration.

OIC can connect to cloud applications over supported network paths. However, some enterprise applications and databases are hosted within private networks and cannot be accessed directly from the public internet.

For these scenarios, Oracle provides the Connectivity Agent.

What Is the OIC Connectivity Agent?

The Oracle Integration Cloud Connectivity Agent is a software component installed within an organization’s network. It enables OIC to communicate with supported on-premises applications and systems without requiring those systems to be directly exposed to the internet.

The agent establishes secure communication with OIC and acts as a bridge between the cloud integration environment and the private network.

How Does the Connectivity Agent Work?

A simplified connectivity process looks like this:

  1. Install and configure the Connectivity Agent on a supported server within the organization’s network.
  2. Register the agent with the OIC instance.
  3. Configure the required connections in OIC.
  4. Select the agent group when configuring an adapter connection that supports agent-based connectivity.
  5. OIC uses the agent to communicate with the target on-premises application.

The exact installation requirements and supported adapters depend on the OIC version and Oracle’s current documentation.

When Is the Connectivity Agent Required?

You may need the Connectivity Agent when:

  • Your database is hosted on an internal network.
  • Your ERP or other enterprise application is deployed on-premises.
  • The target application is not publicly accessible.
  • Your integration requires access to systems behind a corporate firewall.

Not every adapter requires an agent. Cloud applications that are accessible through supported public endpoints generally connect directly through their configured network and authentication settings.

5. Common Adapter Types in Oracle Integration Cloud

Oracle Integration Cloud provides several adapters for different integration requirements.

Adapter Common Purpose
REST Adapter Connects to REST APIs and exposes REST endpoints
SOAP Adapter Integrates with SOAP web services
Oracle ERP Cloud Adapter Integrates with Oracle Fusion Cloud ERP
Oracle HCM Cloud Adapter Integrates with Oracle Fusion Cloud HCM
Database Adapter Performs supported database operations
FTP Adapter Transfers files using FTP or SFTP
Salesforce Adapter Connects with Salesforce applications
Oracle Messaging Adapter Supports messaging-based integration scenarios

The specific operations and features available depend on the adapter version, target application, and connection configuration.

6. Best Practices for Using Adapters in OIC

Follow these practices to build reliable and maintainable integrations:

1. Select the right adapter: Choose an application-specific adapter when it provides the required functionality. Use REST or SOAP adapters when integrating through supported APIs.

2. Understand Trigger and Invoke roles: Identify which application initiates the integration and which systems are called during processing.

3. Configure authentication securely: Use supported authentication mechanisms and follow your organization’s credential-management policies.

4. Validate data mappings: Check mandatory fields, data types, date formats, and lookup values before sending requests to target applications.

5. Handle errors properly: Use fault handlers, appropriate logging, and error-handling strategies to manage connectivity issues and application errors.

6. Monitor integrations: Review integration instances and activity streams to identify failed connections, mapping issues, and unsuccessful requests.

7. Test connectivity before deployment: Verify endpoint access, credentials, network requirements, and agent availability in the development environment.

7. Common Adapter Connectivity Issues and Troubleshooting

Some common issues encountered during OIC adapter configuration include:

  • Authentication errors: Verify usernames, passwords, OAuth credentials, certificates, and token configurations.
  • Connection failures: Check endpoint URLs, network access, firewall rules, and agent status where applicable.
  • Invalid payload errors: Validate the request structure against the target API or adapter operation.
  • Timeout errors: Review target application availability, response times, and timeout settings.
  • Permission errors: Confirm that the integration user has the necessary privileges in the target application.
  • Mapping errors: Check schema definitions, mandatory fields, namespaces, and data types.

Use OIC monitoring tools and the target application’s logs to identify the root cause rather than relying only on the final error message.

Conclusion

Understanding Oracle Integration Cloud adapter types is essential for building successful integrations. Trigger adapters receive requests or events and initiate integrations, while Invoke adapters allow OIC to communicate with external applications and services.

Connectivity determines how these integrations reach cloud and on-premises systems. For private network environments, the Oracle Integration Cloud Connectivity Agent provides a supported communication path to eligible on-premises applications.

By selecting the appropriate adapters, configuring secure connections, validating mappings, and implementing proper error handling, developers can build scalable and reliable integrations across enterprise applications.

For professionals learning Oracle Integration Cloud, understanding Trigger adapters, Invoke adapters, and connectivity is an important foundation for designing real-world OIC integration solutions.

Write A Comment

Enquiry Now
close slider

    Enquiry

    What is Refresh icon