About Integrations Concepts

The following topics describe each of the components required to create an end-to-end integration. Each integration includes connections and mappings. You can also include lookups, which are reusable mappings for the different codes and terms used in your applications to describe the same item. You can also group integrations into packages.

About Connections

Connections define information about the instances of each configuration you are integrating. Oracle Integration includes a set of predefined adapters, which are the types of applications on which you can base your connections, such as Oracle Engagement Cloud Adapter, Oracle Eloqua Cloud, Oracle Service Cloud (RightNow) Adapter, and others. A connection is based on an adapter. For example, to create a connection to a specific Oracle Service Cloud application instance, you must select the Oracle Service Cloud (RightNow) Adapter and then specify the WSDL URL, security policy, and security credentials to connect to it.

Connection Creation

You can create a connection based on any of the following adapters.

Adapter For Information
Adobe eSign Adapter Using the Adobe eSign Adapter
Concur Adapter Using the Concur Adapter

DB2 Adapter

Using the DB2 Adapter
DocuSign Adapter Using the DocuSign Adapter
Eventbrite Adapter Using the Eventbrite Adapter
Evernote Adapter Using the Evernote Adapter
Facebook Adapter Using the Facebook Adapter
File Adapter Using the File Adapter
FTP Adapter Using the FTP Adapter
Gmail Adapter Using the Gmail Adapter
Google Calendar Adapter Using the Google Calendar Adapter
Google Task Adapter Using the Google Task Adapter
LinkedIn Adapter Using the LinkedIn Adapter
Microsoft Calendar Adapter Using the Microsoft Calendar Adapter
Microsoft Contact Adapter Using the Microsoft Contact Adapter
Microsoft Email Adapter Using the Microsoft Email Adapter
Microsoft SQL Server Adapter Using the Microsoft SQL Server Adapter
MailChimp Adapter Using the MailChimp Adapter
MySQL Adapter Using the MySQL Adapter
Oracle Advanced Queuing (AQ) Adapter Using the Oracle Advanced Queuing (AQ) Adapter
Oracle Commerce Cloud Adapter Using the Oracle Commerce Cloud Adapter
Oracle CPQ Cloud Adapter Using the Oracle CPQ Cloud Adapter
Oracle Database Adapter Using the Oracle Database Adapter
Oracle Database Cloud Service Adapter Using the Oracle Database Cloud Service Adapter

Oracle Enterprise Performance Management Cloud Adapter

Using the Oracle Enterprise Performance Management Cloud Adapter

Oracle E-Business Suite Adapter Using the Oracle E-Business Suite Adapter
Oracle Eloqua Cloud Adapter Using the Oracle Eloqua Cloud Adapter
Oracle ERP Cloud Adapter Using the Oracle ERP Cloud Adapter
Oracle Field Service Adapter Using the Oracle Field Service Adapter
Oracle HCM Cloud Adapter Using the Oracle HCM Cloud Adapter
Oracle JD Edwards EnterpriseOne Adapter Using the Oracle JD Edwards EnterpriseOne Adapter
Oracle Logistics Adapter Using the Oracle Logistics Adapter
Oracle Messaging Cloud Service Adapter Using the Oracle Messaging Cloud Service Adapter
Oracle Monetization Cloud Adapter Using the Oracle Monetization Cloud Adapter
Oracle NetSuite Adapter Using the Oracle NetSuite Adapter

Oracle Policy Automation Adapter

Using the Oracle Policy Automation Adapter
Oracle Responsys Adapter Using the Oracle Responsys Adapter
Oracle Engagement Cloud Adapter Using the Oracle Engagement Cloud Adapter
Oracle Service Cloud (RightNow) Adapter Using the Oracle Service Cloud (RightNow) Adapter
Oracle Siebel Adapter Using the Oracle Siebel Adapter
Oracle Talent Acquisition Cloud (Taleo EE) Adapter Using the Oracle Talent Acquisition Cloud (Taleo EE) Adapter

Oracle Talent Cloud for Midsize Adapter (Taleo Business Edition)

Using the Oracle Talent Cloud for Midsize Adapter (Taleo Business Edition)
Oracle WebLogic JMS Adapter Using the Oracle WebLogic JMS Adapter

Oracle Utilities Adapter

Oracle Utilities Adapter
REST Adapter Using the REST Adapter
Salesforce Adapter Using the Salesforce Adapter
SAP Adapter Using the SAP Adapter
SAP Ariba Adapter Using the SAP Ariba Adapter
SOAP Adapter Using the SOAP Adapter
SuccessFactors Adapter Using the SuccessFactors Adapter
SurveyMonkey Adapter Using the SurveyMonkey Adapter
Trello Adapter Using the Trello Adapter
Twilio Adapter Using the Twilio Adapter
Twitter Adapter Using the Twitter Adapter
Workday Adapter Using the Workday Adapter
Oracle Integration Messaging

Oracle Integration Messaging enables you to publish messages to and subscribe to messages from Oracle Integration.

You may have business use cases in which you need to synchronize objects between applications. For example:
  • Create an object in one application that causes the object to be created in other applications. For example, create a new account in Oracle Engagement Cloud Adapter, which causes the creation of an Oracle RightNow organization and an Oracle Eloqua account.

  • Enable multiple applications to subscribe to Oracle Integration and register for updates.

  • Add or remove subscribers without impacting other subscribers or producers.

Oracle Integration Messaging addresses these business requirements through the creation of two types of integrations: one for publishing to Oracle Integration and one for subscribing to Oracle Integration.

  • You create an integration that enables you to publish messages to Oracle Integration by selecting the Publish to ICS option in the Create Integration — Select a Pattern dialog. In this integration:
    • Oracle Integration is added as an invoke and is automatically configured.

    • You configure a trigger (source) adapter (for example, Oracle RightNow, Oracle Engagement Cloud Adapter, or another).

    • The message to pass to Oracle Integration is opaque, so no request mapper support is provided.

    • No trigger (source) enrichment mapper support is provided.

    • Multiple publishers targeting a single message destination is not supported.

      Note:

      Modifying the publisher after creating the subscribers can potentially impact the subscribers. For example, if you change the published object, any existing subscriber mappings are impacted.
  • You create an integration that enables you to subscribe to messages from Oracle Integration by selecting the Subscribe to ICS option in the Create Integration — Select a Pattern dialog. In this integration:
    • Oracle Integration is added as a trigger (source).

    • You are prompted to select the published integration to which to subscribe.



    • You configure an invoke adapter to subscribe to and receive messages from Oracle Integration.

    • Response mapper support is provided between the published object and the subscriber’s application object.

    • Trigger (source) enrichment mapper support is provided.

See Create an Integration to Publish Messages to Oracle Integration and Create an Integration to Subscribe to Oracle Integration.

Related Topics

See the following sections for additional information.

About Oracle Integration Integrations

Integrations are the main ingredient of Oracle Integration. An integration includes at the least a trigger (source) connection (for requests sent to Oracle Integration) and invoke (target) connection (for requests sent from Oracle Integration 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 schemas, and so on. To make this easier, the most complex configuration tasks are handled by Oracle Integration. Once your trigger (source) and invoke (target) connections are configured, the mappers 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.

About Mappings

One of the key tasks to any integration is defining how data is transferred, or mapped, between two applications.

In most cases, the messages you want to transfer between the applications in an integration have different data structures. A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes. When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections. You can expand and load data structure levels on demand to display additional levels. There is no limit on the levels of display.
Description of jet_mapper.png follows
Description of the illustration jet_mapper.png

The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation. A standard set of XSLT constructs are provided (for example, xsl:if, xsl:for-each, and others). A specialized function is also provided for you to reference lookups directly from the mapper.

The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=”qualified”). Elements and attributes with and without namespace prefixes are also supported.

Substitution groups in schemas are supported. You can see all the substitutable elements in a base element in the mapper, and select the one to use.

Extended data types are also supported.

Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names. To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields, and click Apply.

You can also place your cursor over elements and attributes to display specific schema details such as the data type, if mapping is required, and so on.
Description of jet_mapper_element_det.png follows
Description of the illustration jet_mapper_element_det.png

Additional custom annotations can also be displayed. These annotations are currently only available with the Oracle Engagement Cloud Adapter. The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL. This information is then read and made visible as annotations in the mapper (for example, title and description). This information can help you better understand what data is being mapped.

The mapper toolbar provides the following functionality.

Element Description
Recommend link

If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings. This eliminates the need to analyze and perform each individual source-to-target mapping.

Code link

You can view the XSLT code being created as you design your mappings.

Test link

Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.

View link

You can select the following options:

  • Select flow control mode, which enables you to add XSLT statements to your mapping, such as choose, for each, if, otherwise, when, copy-of, text, and value-of. A target element must already be created for you to drag an XSLT statement onto a target element node. Select this option, then select function link in the mapper toolbar to show the XSLT statements.

  • Select to show the namespace prefixes on source and target element nodes.

  • Select to show the types (prefixes and data types) on source and target element nodes.

Filter link

You can filter the display of element nodes, error messages, and warnings in the source or target data structures.

Undo link

You can select to undo the previous action performed in the mapper. For example, if you perform a mapping, then press this button, the mapping is removed. The link is disabled when all actions have been undone.

Redo link

You can redo the action that was undone.

Maximize link

You can maximize the size of the mapper. This is useful when working with large schemas.

Function link

You can add functions, operators, and XSLT expressions to your mappings.

Map Request Data Between Applications

Once you create an integration and have the trigger (source) and invoke (target) in place, you can define how data is mapped between the two data structures.

The mapper appears with the source data structure on the left and the target data structure on the right:
  1. Map request data between the source data structure and target data structure.
  2. Click Close.
When returning from the mapper, the map icon changes color to indicate it is complete. Once you create a mapping in an integration, you can return to the mapping and make any necessary changes to how you mapped your data.
See Mapping Data of Using the Oracle Mapper.

Map Response Data Between Applications

If your integration pattern contains a response, you can map the response.

  1. Map response data between the source data structure and target data structure.
  2. Click Close.
    When returning from the mapper, the map icon changes color to indicate it is complete.
    Once you create a mapping in an integration, you can return to the mapping and make any necessary changes to how you mapped your data.
See Mapping Data of Using the Oracle Mapper.

About Mapping Multiple Sources to a Target

When mapping data between source and target data structures, some integration scenarios enable you to map the fields of multiple source structures to the fields of a single target structure.

Integration scenarios that include multiple source structure capabilities include the following:
  • Integrations in which message enrichment points have been added (for example, a request message enrichment point, a response message enrichment point, or both points). For example, within the context of the following inbound trigger connection to outbound invoke connection, request mappings and request enrichment mappings are both defined.
    Description of mapper_mult_sources11.png follows
    Description of the illustration mapper_mult_sources11.png

    Clicking the Request Mapping icon shows that there are two sources available for mapping in the Source section. The process structure is the primary source. The $RequestEnrichmentApplicationObject structure is the secondary source. Secondary sources are treated as variables and identified by the $ added to the front. The fields of both sources can be mapped to the fields of the target.
    Description of mapper_mult_sources9.png follows
    Description of the illustration mapper_mult_sources9.png

  • Integration responses with a response mapping between a trigger connection and an invoke connection. For example, within the context of the invoke connection’s response back to the trigger connection, there are response mappings.
    Description of mapper_mult_sources7.png follows
    Description of the illustration mapper_mult_sources7.png

    Clicking the Response Mapping icon shows the two sources available for mapping in the Source section. The GetResponse structure is the primary source. The $SourceApplicationObject structure is the secondary source (note the $). The fields of both sources can be mapped to the fields of the target.
    Description of mapper_mult_sources10.png follows
    Description of the illustration mapper_mult_sources10.png

See Mapping Multiple Sources to a Target of Using the Oracle Mapper.

About Oracle Integration Enrichments

You may have business use cases in which you need to enhance data by calling another service before sending data to an invoke service or before sending data back to a requestor. To address this business requirement, you can optionally add enrichment data sources to the request part, the response part, or both parts of an integration. Enrichments participate in the overall integration flow and can be used in the request and/or response payloads between the trigger and invoke services. Enrichments subscribe to a synchronous request and response message pattern.

Enrichments enable you to:
  • Add additional information. For example, your business use case may require you to:

    • Add a stock price

    • Increase on-site quantities of a product

    • Estimate local currency

  • Convert data, such as mapping data between account numbers. The ability to map data between the request/response payload and the enrichment source application is a key feature of enrichments.

See Add Request and Response Enrichments.

About Oracle Integration Lookups

Use lookups in your integrations 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.

Lookup Function

Oracle Integration provides a lookupValue function that you can call in the mapper to specify when to reference a lookup table. Use this function to look up values at runtime based on information in incoming messages. This way, your integration knows how to map data coming in from one application to data being sent to another application.

See Referencing Lookups of Using the Oracle Mapper.

About Oracle Integration Packages

You can 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 Oracle Integration. You can import packages from the Oracle Marketplace. These packages consist of a series of prebuilt integrations provided by Oracle. You can also import and export packages that consist of integrations that you or other users created. 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 Oracle Integration instance.

Packages are displayed on the Packages page in Oracle Integration. 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.
Description of ics_package_view.png follows
Description of the illustration ics_package_view.png

See Manage Packages and Create Integrations.

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

The above capabilities enable you to implement use cases such as the following:
  • 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 Engagement Cloud Adapter, 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 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

The connectivity agent provides the following 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

Workflow for Using the Connectivity Agent

Follow this workflow to use the connectivity on-premises agent.

Task Documentation
Create a connectivity agent group. Create an Agent Group
Download and run the on-premises connectivity agent installer on your host. During installation setup, you associate the on-premises connectivity agent with the agent group.

Download and Run the Connectivity Agent Installer

Create an adapter connection in Oracle Integration and associate the connection with the connectivity agent group.

Create Connections

Design an integration that uses this connection.

Create Integrations

Activate the integration. Activate an Integration