About Integrations
Oracle Integration is a complete, secure, but lightweight integration solution that enables you to connect your applications in the cloud. It simplifies connectivity between your applications and connects both your applications that live in the cloud and your applications that still live on premises. Oracle Integration provides secure, enterprise-grade connectivity regardless of the applications you are connecting or where they reside.
Oracle Integration provides native connectivity to Oracle Software as a Service (SaaS) applications, such as Oracle Sales Cloud, Oracle Service Cloud, and so on. Oracle Integration adapters simplify connectivity by handling the underlying complexities of connecting to applications using industry-wide best practices. You only need to create a connection that provides minimal connectivity information for each system. Oracle Integration lookups map the different codes or terms used by the applications you are integrating to describe similar items (such as country or gender codes). Finally, the visual data mapper enables you to quickly create direct mappings between the trigger and invoke data structures. From the mapper, you can also access lookup tables and use standard XPath functions to map data between your applications.
Once you integrate your applications and activate the integrations to the runtime environment, the dashboard displays information about the running integrations so you can monitor the status and processing statistics for each integration. The dashboard measures and tracks the performance of your transactions by capturing and reporting key information, such as throughput, the number of messages processed successfully, and the number of messages that failed processing. You can also manage business identifiers that track fields in messages and manage errors by integrations, connections, or specific integration instances.
About Connectivity Agents and Integrations Between On-Premises Applications and Oracle Integration
The on-premises connectivity agent enables you to create integrations and exchange messages between on-premises applications and Oracle Integration. Message payloads of up to 10 MB are supported through the use of compression. The on-premises connectivity agent provides multithreading support, which allows for multiple executors to perform downstream message processing.
This type of integration enables you to:
-
Access SOAP/REST endpoints exposed by applications such as Oracle E-Business Suite, Siebel, and JD Edwards and any on-premises home grown SOAP/REST APIs
-
Access non-HTTP-based endpoints such as databases, JMS, AQ, local file systems, SAP, and others
-
Send requests from a cloud application (for example, send a create service order request from an Oracle Service Cloud application) to an on-premises E-Business Suite application
-
Synchronize bulk data extracts of a product from a product data hub in Oracle ERP Cloud with an on-premises Oracle database or an Oracle Database Cloud Service instance using the connectivity agent
-
Synchronize customers that are added/updated in an on-premises SAP application with SaaS applications such as Oracle Sales Cloud, Oracle CPQ, Oracle Service Cloud, and Salesforce.com
About the Connectivity Agent Framework
The connectivity agent framework enables SaaS applications in the cloud to interact through Oracle Integration with on-premises systems.
![Description of connect-agent.png follows Description of connect-agent.png follows](img/connect-agent.png)
Description of the illustration connect-agent.png
Connectivity Agent Components
The connectivity agent consists of the following components:
-
SaaS agent: This agent is installed and runs in Oracle Integration and supports communication with on-premises applications. There is one SaaS agent per Oracle Integration environment.
-
On-premises agent: This agent is installed and runs in an on-premises environment on the same network as internal systems such as Oracle E-Business Suite, Oracle Siebel, Oracle Database, and others. You download the on-premises agent installer from the Agents page in Oracle Integration to your on-premises environment for installation. There can be multiple host systems, each running one or more agents, in a cloud/on premises topology. The on-premises agent does not permit any explicit inbound connections. All connections are established from the on-premises environment to Oracle Integration.
Connectivity Agent Functionality
Note:
While multiple connectivity agents can run on a single host, this is not the recommended practice. If you follow this practice, you must ensure that the physical host has enough resources to run multiple connectivity agents.-
No ports are opened on the on-premises system for communication.
-
All communication is secured using SSL.
-
The on-premises connectivity agent registers with Oracle Integration over SSL using the provided Oracle Integration credentials.
-
The on-premises connectivity agent checks for work by making outbound requests through the firewall.
-
The on-premises connectivity agent can use a proxy to access the internet (the same proxy as other internal applications and browsers use). Authentication support for outbound proxy access is provided.
-
The on-premises connectivity agent connections are configured by the agent retrieving the configuration details from Oracle Integration.
-
The on-premises connectivity agent processes requests by pulling messages from Oracle Integration across SSL.
-
The on-premises connectivity agent posts responses by pushing messages to Oracle Integration across SSL.
-
All communication is initiated by the on-premises connectivity agent.
-
No private SOAP-based web services are exposed.
-
No existing J2EE container is required to deploy the on-premises connectivity agent.
-
No data is persisted in the on-premises agent.
Adapter Connections that Work with the Connectivity Agent
The on-premises agent works with the following adapter connections.
-
Outbound (invoke) adapters: The following adapters can be configured as invoke connections in an integration to support communication with endpoint applications:
-
DB2
-
File
-
Microsoft SQL Server
-
MySQL Database
-
Oracle Database
-
Oracle E-Business Suite
-
REST
-
SAP
-
Siebel
-
SOAP
-
-
Inbound (trigger) adapters: The following adapters can be configured as trigger connections in an integration:
-
DB2
-
File
-
JMS
-
Microsoft SQL Server
-
MySQL Database
-
Oracle Database
-
Oracle E-Business Suite
-
SAP
-
Siebel
-