1. Using Integrations in Oracle Integration 3
  2. Manage Integrations
  3. Use Metadata in Integrations

Use Metadata in Integrations

You can access the integration name, identifier, and version instead of hard coding those values in integrations. You can also access runtime data and environment data inside the integration.

The following metadata is exposed in integrations. You can use this metadata in the mapper and actions that include the Expression Builder such as assign, log, notification, and others.
  • integration
    • name
    • identifier
    • version
  • runtime
    • instanceId
    • invokedBy
  • environment
    • serviceInstanceName
    • baseURL

The following use case provides a high-level overview of using metadata in an integration.

  1. Create and design an application integration.
  2. Add an action that includes an Expression Builder.
    For this example, a log action is added.
  3. In the source tree, find the integration metadata.
  4. Add the required metadata to the Logger Message field. For this example, a concat function is used to include the integration name metadata.

    The Input Sources and Functions tabs are shown. The Sources tree has been expanded to show the name element selected. On the right is the Configure Logger panel. The name and description fields appear at the top. Below this the Log option has been set to Always. Below this, the Logger Message field is populated to show the concat function added.

  5. Complete design of the integration.
  6. Activate and run the integration.
  7. Go to the Instances page.
  8. Click the business identifier of the integration.
  9. Scroll down and note that the log message in the activity stream shows the integration name (for this example, Hello World).

    The activity stream is shown. Tracing level is set to Production. The message flow is shown. For the logger, the view payload icon has been expanded to show Integration name is :Hello World. Download, copy, and payload line numbering icons are shown.