Oracle Integration Cloud Service is a comprehensive, secure, lightweight integration solution that enables you to easily connect your applications to Oracle Cloud. It simplifies the connectivity between applications and connects both cloud and on-premise applications. Oracle Integration Cloud Service provides secure, enterprise-grade connectivity regardless of the applications that are being connected or where they reside.
Concepts on Integration Cloud Service
Each topic below describes the components required to create an end-to-end integration. The integration includes connections and mappings. You can also include lookups which are reusable mapping for the different codes and terms used in your applications to describe the same item, as well as, grouping integrations into packages.
Integrations Between On-Premise Applications such as PeopleSoft and Oracle Integration Cloud
Oracle Integration Cloud
Integrations are the main functionality of the Oracle Integration Cloud Service. An integration includes a trigger source, a connection for requests sent to Oracle Integration Cloud Service which invokes (target) connection (for requests sent from Oracle Integration Cloud Service to the target), and the field mapping between those two connections. When you create your integrations, you build on the connections you already created by defining how to process the data for the trigger (source) and invoke (target) connections. This can include defining the type of operations to perform on the data, the business objects, and fields against which to perform those operations, required schemes, and so on. To make this easier, the most complex configuration tasks are handled by Oracle Integration Cloud Service. Once the trigger (source) and invoke (target) connections are configured, the maps between the two are enabled so you can define how the information is transferred between the trigger (source) and invoke (target) data structures for both the request and response messages.
One of the key tasks to any integration is defining how the data is transferred or mapped between two applications. In most cases, the messages you want to transfer between the applications in an integration has different data structure that are mapped between two applications. In most cases, the messages you want to transfer between the applications in an integration has a different data structure. A visual mapper enables you to map fields between applications by dragging source fields onto target fields. When you open the mapper for a request or response message in an integration, the data structure is automatically populated with the information pulled from the source and target connections. You can expand the load data structure levels on demand to display additional levels. There's no limit to the levels of display.
Cloud Lookups are used to create reusable tables that map the different terms used to describe the same item across your applications. A lookup associates values used by one application for a specific item to the values used by other applications for the same item. For example, one application uses a specific set of codes to describe countries, while another application uses a different set of codes to describe the same countries. Lookups can be used for items such as mapping gender codes, nationality codes, currency codes — any type of information that your applications must share with each other but that they represent differently. You may have several lookups for one integration, depending on the number of fields that require mapping. Lookups are also reusable and can be used by multiple integrations. Lookups are based on a static definition, meaning you create and populate them during design time, and are not changed by runtime activities. These tables are used for looking up values only.
Cloud Service Packages
You can also group one or more integrations into a single structure called a package. Packages enable you to easily import and export a group of integrations to and from Integration Cloud Service. You can import the packages from the Oracle Marketplace. These packages consist of a series of pre-built integrations provided by Oracle. You can even import and export packages that consist of integrations that you or other users create. Packages are optional, meaning that integrations do not need to be part of packages. However, for a package to exist, it must include at least one integration. Packages cannot be locked to exclude other users of your Integration Cloud Service instance. Packages are displayed on the Packages page in Integration Cloud Service. From this page, you can view, delete, import, and export packages. You create packages when you create an integration in the Create Integration dialog. You can also update an integration's package in the Update Integration dialog.
Agents Between On-Premise Applications and Oracle Integration Cloud
Oracle Integration Cloud Service provides an agent framework that enables you to create integrations and exchange messages between on-premises applications and Oracle Integration Cloud Service. Message payloads of up to 5 MB are supported through the use of compression, which may bring the payload down to 512 KB in size. The on-premises agent provides multi-threading support, which allows for multiple executors to perform downstream message processing.
The Integration Cloud Service Dashboard displays information on the current state of all your running integrations. The dashboard gives you a quick view into the performance metrics of all your active integrations. The graph includes the total number of messages processed, the average processing time, the number of messages with errors, and the success rate. The integrations tab lists metrics for each running integration, and you can view a graph of the metrics for each integration in the list. The dashboard also provides a view of recent activity for running integrations and the ability to download all activities.
You can manage integration errors from the Errors Page in the Integration Cloud Services. The Errors Page displays information about individual integration instances and groups the errors by integrations and connections over a specified period of time.
Creating an Integration for Simple File Transfer
Log in to Oracle Integration Cloud. Using the menu on the left hand column, navigate to the Designer. Go to Connections and create the source and destination connection.
Enter the Source connection details.
Enter the Destination connection details.
Create an Integration using the FTP adapter and the connections created in the above section.
Create the Integration workflow.
Place the file in source destination.
Activate the integration.
Execute an ad hoc run.
Monitor the run.
Track the run results.
Below is the workflow post of a successful integration execution. The green color for each task shows successful completion.
View the activity stream.
Successful File transfer.
Oracle Integration Cloud allows you to seamlessly integrate applications and data by leveraging an extensive library of pre-built adapters to connect with virtually any application, service, or database. Oracle has adapters covering Oracle Sales Cloud, Oracle Service Cloud, Oracle Marketing Cloud, Oracle E-Business Suite, Siebel and JD Edwards, as well as many non-Oracle applications including Salesforce, ServiceNow, and SAP.
With Oracle's comprehensive integration platform, you can:
Accelerate integration using a point-and-click visual designer, pre-built adapters, and process flows.
Integrate all types of applications, databases, and business processes.
Maximize the value of your investments by connecting data and processes across all applications.
Ready to get started with Oracle Integration Cloud? Shedule a meeting with an Astute team member.