Choosing an Integration Pattern

Exchange data between on-premises, legacy, and cloud applications using an integration. To create the integration, add adapter connections and define how information is shared between them.

Choose one of these integration patterns and then complete the procedure for the selected pattern:
  • Map Data: Creates an integration to which you add a trigger and an invoke connection. You can create a single routing expression, and request and response enrichments, as needed. This pattern doesn’t support multiple routing expressions. If your integration requires this feature, then create an Orchestration integration. See Creating a Map Data Integration.

  • Orchestration: Creates a synchronous, asynchronous, or fire-and-forget (no response) orchestrated integration. Orchestrations provide the following features:
    • Capability to build a multistep integration between multiple applications.

    • Ability to perform conditions, iterations, Javascript callouts, and file processing.

    • Ability to model fault/error handlers.

    See Creating an Orchestrated Integration.

Creating a Map Data Integration

Create a Map Data integration pattern to which you add a trigger (source) and an invoke (target) connection. The trigger connection sends requests to Oracle Integration Cloud Service. You can create a single routing expression as well as request and response enrichments as needed.

Note:

If your integration requires multiple routing expressions, create an Orchestration integration. See Creating an Orchestrated Integration.
  1. Log in to Oracle Integration Cloud Service, click Integrations, and then New Integration.
  2. Select the Map Data integration pattern, complete the required and optional fields, and then click Create.
  3. Add the trigger connection:
    1. From the Connections or Technologies panes, drag a connection to the Drag and Drop a Trigger area on the integration canvas.
    2. Complete the Adapter Endpoint Configuration Wizard. For field descriptions, see About the Fields in the Adapter Endpoint Configuration Wizard.
    3. Click Save.
  4. Add the invoke connection:
    1. From the Connections or Technologies panes, drag a connection to the Drag and Drop an Invoke area on the integration canvas.
    2. Complete the Adapter Endpoint Configuration Wizard. For field descriptions, see About the Fields in the Adapter Endpoint Configuration Wizard.
    3. Click Save.
  5. Assign the business identifiers for tracking fields:
    1. Click the Tracking icon in the upper right part of the page.
    2. Define the tracking fields.
    3. Click Done.
    4. Click Save, and then click Exit Integration.
  6. Map the data. See Creating Mappings and Lookups.
  7. Activate the integration. See Activating an Integration.

Creating an Orchestrated Integration

When you design your integration, you can do the following:

  • Add switch activities to create multiple routing expressions.

  • Create ad hoc mappings on switch branches.

  • Add callback activities (to end an integration and respond back to the sender) and end activities (to end an integration without responding back to the sender) in asynchronous integrations.

  1. Log in to Oracle Integration Cloud Service, click Integrations, and then New Integration.
  2. Select the Orchestration integration pattern, complete the required and optional fields, and click Create.
  3. Define the inbound trigger:
    1. On the left side of the integration canvas, click TRIGGERS to expand the panel.
    2. Click the adapter type to display the specific type and number of configured adapters. Synchronous, asynchronous, and fire-and-forget (no response) triggers are supported.
    3. Drag the configured adapter to the large plus (+) symbol within the circle on the integration canvas.
    4. Complete the Adapter Endpoint Configuration Wizard. For field descriptions, see About the Fields in the Adapter Endpoint Configuration Wizard.
  4. Define the outbound invoke:
    1. On the left side of the integration canvas, click INVOKES to expand the panel.
    2. Click the adapter type to display the specific type and number of configured adapters.
    3. Drag an adapter to the integration canvas and drop it on one of the large plus (+) symbols.
    4. Complete the Adapter Endpoint Configuration Wizard. For field descriptions, see About the Fields in the Adapter Endpoint Configuration Wizard.
  5. Define the switch branches:
    1. On the left side of the canvas, click ACTIONS to expand the panel.
    2. Drag the SWITCH icon to the integration canvas and drop it on one of the large plus (+) symbols.
    3. Click the Undefined branch icon.
    4. Select the Edit icon.
    5. Define a routing expression, then click Save and Exit Expression Builder.
    6. On the left side of the canvas click INVOKES to expand the panel.
    7. Drag an adapter to the plus (+) symbol on the defined branch or the otherwise branch.
    8. Complete the Adapter Endpoint Configuration Wizard. For field descriptions, see About the Fields in the Adapter Endpoint Configuration Wizard.
  6. Define the optional ad-hoc mappings:
    1. On the left side of the canvas, click ACTIONS to expand the panel.
    2. Drag a MAP icon to a branch of the switch activity.
    3. Select an endpoint to map.
    4. Map the source data structure to the target data structure.
    5. Click Save, and then click Exit Mapper.
    6. Drag a MAP icon to the otherwise branch of the switch activity.
    7. Repeat steps d to f.
  7. Assign the business identifiers for tracking fields:
    1. Click the Tracking icon in the upper right part of the page.
    2. Define the tracking fields.
    3. Click Done.
    4. Click Save, and then click Exit Integration.
  8. Activate the integration. See Activating an Integration.

Refreshing Integration Metadata

You can manually refresh the currently-cached metadata available to adapters that have implemented metadata caching. Metadata changes typically relate to customizations of integrations, such as adding custom objects and attributes to integrations. There may also be cases in which integrations have been patched, which results in additional custom objects and attributes being added. This option is similar to clearing the cache in your browser. Without a manual refresh, a staleness check is only performed when you drag a connection into an integration. This is typically sufficient, but in some cases you may know that a refresh is required. For these cases, the Refresh Metadata menu option is provided.

To refresh integration metadata:

Note:

The Refresh Metadata menu option is only available with adapters that have implemented metadata caching.
  1. On the Oracle Integration Cloud Service home page, click Connections.
  2. Locate the connection to refresh.
  3. From the menu at the right, select Refresh Metadata.
    Description of conn_actions_menu.png follows
    Description of the illustration conn_actions_menu.png
    A message is displayed indicating that the refresh was successful.
    Metadata refresh for connection "connection_type" has been initiated successfully.

About the Fields in the Adapter Endpoint Configuration Wizard

The following tables provide descriptions of the fields that appear in the Oracle Integration Cloud ServiceAdapter Endpoint Configuration Wizard. The wizard appears when you create an integration.

Basic Info Page

Field Description

What do you want to call your endpoint?

Provide a meaningful name so that others can understand the purpose of the connection. For example, LinkedInTarget_update_status. You can use English alphabetic characters, numbers, underscores, and dashes in the name. You can’t use:
  • Blank spaces (for example, My FTP Connection)

  • Special characters (for example,  #;83& or righ(t)now4)

  • Multibyte characters

What does this endpoint do?

Enter an optional description of connection functionality. For example: This endpoint updates status on a user's LinkedIn timeline.

Trigger Request Page

Field Description

Browse by

Select the Oracle Utilities application that hosts the business object.

Select a Business Object

Select the business object from the Oracle Utilities application to receive as a request that starts the integration.

Filter by object name

Enter the initial letters to filter the display of business objects.

Trigger Response Page

Field Description

Browse by

Select the Oracle Utilities application that hosts the business object.

Select a Business Object

Select the business object from the Oracle Utilities application to receive as a request that starts the integration.

Filter by object name

Enter the initial letters to filter the display of business objects.

Response Type

Select one of these options:

  • Request-Response: The default. The Oracle Utilities application waits until a response is received from the integration. This is also known as the request and response message exchange pattern.

  • Send Faults

Invoke Operations Page

Field Description

Browse by

Select the Oracle Utilities application that hosts the business object.

Select a Business Service

Select a business service to invoke.

Filter by service name

Enter the initial letters to filter the display of business services.

Select the Operation to Perform on the Service

Select an operation from the published web service.

Summary Page

Field Description

Summary

Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard. The information that’s displayed can vary by adapter. For some adapters, the selected business objects and operation name are displayed. For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.