Track Business Identifiers in Integrations During Runtime

You can track fields in messages on which you have defined business identifiers on the Tracking page during runtime. These fields are only available for tracking on the Tracking page if you defined a primary business identifier in the Business Identifiers for Tracking dialog during design time.

To track business identifiers in integrations during runtime:
  1. In the navigation pane, click Integrations, then click the < arrow next to Designer.
  2. Click Monitoring, then click Tracking.
  3. From the dropdown list, select the time period or retention period during which to search for business identifiers in messages.
    You can also specify a custom time range with which to filter the search for instances with the From and To buttons at the bottom. This enables you to select a time range as small as a minute and track only those instances processed within that specified time range. The specified time range is preserved by default and applied to the data being displayed when you navigate from one monitoring page to another (for example, when you move from the Track Instances page to the Integrations, Track Runs, or Errors page).

    Note:

    The time range specified must be within the retention period. Data beyond the retention period is not retained. If the selected time range is beyond the retention period, only available data is displayed.
    Results are displayed for any integration on which a primary business identifier is set, including the business identifier and value, the instance identifier of the integration, and the state of the integration (for example, completed, failed, or aborted). You can show the name and value of tracking variables.

    For aborted instances, the running time does not point to the actual time the aborted (faulted) instance was running. Instead, it consists of the total time span between when the instance began and when the instance was manually aborted.



  4. Use the Search field to search for values across both primary identifiers and secondary identifiers.
    1. To search on primary and secondary identifier values, enter a value, and click Search. For this example, James is entered. In the search results, Instance ID 13, Instance ID 12, and Instance ID 11 that are returned have a primary value of James. Instance ID 14 with a secondary identifier value of Mark.James@asc.com is also returned.
    2. To search only on primary business identifier values, enter the value as primary: value or Primary: value in the Search field

      Search field value of primary:James. The Search button is to the right.
  5. Click the business identifier to access a graphical display of the integration instance.
    This page provides information about the business identifiers and values defined for the integration, the instance identifier of the integration, any error message, the audit trail, the activity stream, a button for discarding an error, and other information. The entire message flow is tracked through the integration. Successful message flows are indicated by green arrows. Any message flow errors that occur are identified by red arrows. For looping elements (such as for-each, while, and others), successful instances do not capture the flow inside the iterations. The loop-internal actions and colored lines are shown only if a failure occurs.
    Description of tracking_bus_id.png follows
    Description of the illustration tracking_bus_id.png
  6. From the hamburger menu menu, select Audit Trail to view the message flow. The audit trail shows details about the movement of the message through the integration, including where any failures occurred. For orchestrated integrations, the message flow through each activity (for example, any defined switch activity branches) is shown.
  7. Select View Activity Stream to view the high level activity stream. If you enabled tracing to include the payload when you activated your integration, more specific payload details are provided.

Note:

  • If you enter a primary business identifier in the Search field, but do not click the Search button, then select a value from the time period dropdown list, note that the instances are filtered considering the string entered in the Search field, even though the Search button was not clicked. This is the expected behavior and is true for other landing pages in Oracle Integration.

  • The search facility on the Tracking page is case sensitive.