In Oracle Integration Cloud (OIC), an "endpoint" typically refers to a specific destination or target system that is part of an integration. In the context of OIC integrations, endpoints are crucial components that define where data is sourced from or sent to.
Endpoints in OIC integrations can be categorized into two main types:
1. **Trigger Endpoints:**
- These are endpoints that initiate the integration process.
- For example, a trigger endpoint could be an Oracle ERP Cloud instance, a database, a file in an FTP server, or an HTTP endpoint that serves as a webhook.
2. **Invoke (Target) Endpoints:**
- These are endpoints that receive the data processed by the integration.
- Examples include a web service, a REST API, an Oracle Cloud application, or another database.
When designing an integration in Oracle Integration Cloud, you typically define the source or trigger endpoint and the target or invoke endpoint. The integration flow specifies how data is transformed and processed between these endpoints.
It's important to configure endpoint connections within OIC, providing the necessary credentials, connection details, and configuration parameters to establish communication between OIC and the external systems.
For instance, if you are integrating an Oracle Cloud ERP system with an on-premises database, you would configure the Oracle Cloud ERP system as the trigger endpoint and the on-premises database as the invoke endpoint (or vice versa, depending on the integration flow). The endpoint configurations ensure that OIC can securely and reliably communicate with these systems during the integration process.
In summary, an endpoint in OIC integrations represents the source or target system that participates in the integration, and configuring endpoints is a fundamental step in setting up seamless data flow between different applications and services.
