An Introduction to Oracle Integration Cloud Service
Oracle Integration Cloud Service (ICS) is a cloud-based integration software designed to do integrations between cloud-based software and contains abilities that extend past this to doing integrations along with your on assumptions software.
Dependent on the fantastic Oracle Service Bus program, ICS was made to be non-developer friendly and requires another way of generating integrations. All settings are browser-based, and XSL can be used for information mapping/transformation.
ICS ships using a very lengthy list of program adapters which always grows. Many adapters all link to additional cloud-based programs, but standard adapters for database, database, and FTP are also encouraged. Here’s the current list of adapters:
- Adobe eSign
- Google Calendar
- Google Mail
- Google Task
- JD Edwards EnterpriseOne
- Microsoft Calendar
- Microsoft Contact
- Microsoft Email
- Microsoft SQL Server
- Oracle Commerce Cloud
- Oracle CPQ
- Oracle Database
- Oracle E-Business Suite
- Oracle ERP Cloud
- Oracle Field Service Cloud
- Oracle HCM Cloud
- Oracle Messaging Cloud Service
- Oracle RightNow (Service Cloud)
- Oracle Sales Cloud
- Oracle Siebel
- Oracle Utilities
The main ICS components are Connections and Integrations.
A link is an example of the adapter configured to utilize a specific endpoint and credentials. Consequently, in case you’ve got a need to speak to two different systems with the identical SOAP adapter, then it counts just two links. Since ICS is accredited by link, it’s an inexpensive integration option for those businesses which don’t want the complete Oracle SOA Suite heap. Let us look a little at ICS’s abilities.
Here’s a listing of the Different Kinds of confirmed integrations:
The Fundamental Map Data Style/Pattern permits for data transfer between 2 systems, together with the capacity to include one extra enrichment call through the petition and the answer. The use-case with this particular routine is geared towards obtaining information from system “A” to system “B.” The transformations are rather simple, and there might be a minimal requirement to collect extra details.
The Orchestration Style/Pattern is just one I enjoy very much, providing the following actions:
Combining these supplies you with abilities to make more complex flows, i.e., invoking requires for downstream systems, aggregating information, and creating if/then implementation flow decisions depending on the information you get. Much like Oracle Service Bus, these integrations are all stateless. A subsequent blog article will ensure the Orchestration Style/Pattern is longer detailed.
The previous two Styles/Patterns are for Publish/Subscribe to ICS messaging. Consider using JMS to compose and read messages to be leveraged across several integrations.
For communicating with your assumptions systems, it is possible to install both Connection and Execution Agents. The Link Agent lets your ICS case convey directly without needing to hit a hole in your firewall if the Execution Agent provides you an example of ICS, which runs integrations locally. This is great for communicating between assumptions systems, preventing the latency between the ICS case from the cloud.
ICS offers a monitoring console to track messages and errors:
You’re able to track by connection and integration. Diagnostic and Task logs may be downloaded as required. These offer the identical kind of WebLogic Server logs that you would ordinarily see from the application server. These pictures can be useful for debugging and monitoring purposes.