1. Using Integrations in Oracle Integration Generation 2
  2. Create Basic Routing Integrations and Integrations to Publish and Subscribe to Oracle Integration
  3. Create Integrations to Publish and Subscribe to Oracle Integration

Create Integrations to Publish and Subscribe to Oracle Integration

You can create integrations that enable you to publish messages to Oracle Integration. and integrations that enable you to subscribe to messages from Oracle Integration.

Topics:

Create an Integration to Publish Messages to Oracle Integration

You can create integrations that enable you to publish messages to Oracle Integration. Message publishing is accomplished through use of Oracle Integration Messaging.

To create an integration to publish messages to Oracle Integration:

Note:

Oracle Integration Messaging supports messages of up to 10 MB in size.
  1. Follow the steps in Create Integrations to create an integration to publish to Oracle Integration. This creates an integration style with a predefined Oracle Integration Messaging invoke connection that enables you to publish messages to Oracle Integration.
  2. In the integration canvas, drag an adapter from the Connections panel on the right to the trigger (source) area of the canvas. For this example, an Oracle CX Sales and B2B Service Adapter is selected.
    The Adapter Endpoint Configuration Wizard is displayed.
  3. On the Basic Info page, enter an endpoint name and optional identifier for this connection.
  4. Click Next.
  5. On the Request page, select a business object (for this example, Account is selected), then click Next.
  6. On the Response page, select None as the response type, then click Next.
  7. On the Summary page, click Done.
    The Oracle ERP Cloud Adapter is configured to publish messages to Oracle Integration through use of Oracle Integration Messaging. Note that there is no request mapper available with this type of integration style.
    Description of publish_to_oic.png follows
    Description of the illustration publish_to_oic.png

  8. Click Save, then click Close.
    To subscribe to the message configured in this section, you must now configure Oracle Integration to act as a publisher. This enables Oracle Integration to publish the messages to which other adapters can then subscribe. See Create an Integration to Subscribe to Oracle Integration.

Create an Integration to Subscribe to Oracle Integration

You can create integrations that enable you to subscribe to messages from Oracle Integration. Message subscription is accomplished through use of Oracle Integration Messaging.

To create an integration to subscribe to Oracle Integration:
  1. Follow the steps in Create Integrations to create an integration to subscribe to Oracle Integration. This creates an integration style with Oracle Integration Messaging that enables you to subscribe to messages from Oracle Integration.
    The Select a Publisher dialog is displayed.
  2. Select the integration to which to subscribe, then click Use. For an integration to be displayed for selection, you must first configure Oracle Integration as a subscriber, as described in Create an Integration to Publish Messages to Oracle Integration. Only integrations that are 100% completed and unlocked are displayed. Integrations that are locked (meaning that they are being edited) are not displayed.
    Description of ics_subscribe_to_ics2.png follows
    Description of the illustration ics_subscribe_to_ics2.png

  3. Drag an adapter to the invoke (target) area of the integration designer. For this example, an Oracle Service Cloud (RightNow) Adapter is added.
  4. On the Basic Info page, enter a name and optional identifier for this connection.
  5. Click Next.
  6. On the Operations page, select an appropriate operation and business object, then click Next. For this example, a CRUD Create operation and Organization business object are selected.
    Description of subscribe_to_rn.png follows
    Description of the illustration subscribe_to_rn.png

  7. On the Summary page, review your changes, then click Done.
    Description of subscribe_to_oic.png follows
    Description of the illustration subscribe_to_oic.png

    The request mapper is available with this type of integration style.
  8. Click the Request Mapping icon, then click Create.
  9. Map source fields to the corresponding target fields. See Mapping Data of Using the Oracle Mapper with Oracle Integration Generation 2.
  10. When complete, click Close, then click Apply to save your changes.
    The Oracle Service Cloud (RightNow) Adapter is configured to subscribe to messages from Oracle Integration through use of Oracle Integration Messaging.
  11. Click Save, then click Close.
  12. Activate the publishing integration described in Create an Integration to Publish Messages to Oracle Integration and the subscribing integration described in this section. See Activate an Integration.
    The completed publishing and subscription integrations enable you to:

    • Create an object in one application that causes the object to be created in other applications.

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

    • Enable additional subscribers to be added or removed without impacting other subscribers or publishers.

Business identifier tracking data is copied when a subscriber is created. If a publishing integration is updated later, you must update the subscribing integration.

For example, assume you create a publishing integration, then create a subscribing integration and select to subscribe to the publishing integration. Select Tracking from the hamburger menu menu, and note that the tracking attributes of the selected publishing integration are displayed. Assume you then edit the publishing integration and change the operation of the trigger adapter (as an example), save, and exit the canvas. If you then edit the subscribing integration and select Tracking from the hamburger menu menu, note that the business identifier tracking attributes of the publishing integration that are displayed are those that existed before the updates were made. The tracking fields are not updated as per the updated publisher integration. This is the expected behavior.