You can track fields in messages on which you have defined business identifiers on the Track Instances page during runtime. These fields are only available for tracking on the Track Instances page if you defined a primary business identifier in the Business Identifiers for Tracking dialog during design time.
- In the left navigation pane, click Home > Monitoring > Integrations > Tracking.
- From the link, select the time window, instance ID, status, integration, request
ID, recovery job ID, or asserter instance for which to search for business
identifiers in messages.You can also click Date Range to 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 Monitor Integrations 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.
- Use the Search field to search for values across both primary identifiers and secondary identifiers.
- To search for primary and secondary identifier values, enter a value,
and click Search. For example, assume the primary
James. In the search results, any instances that have a primary value of James are returned. Any instances with a secondary value that includes James (for example, Mark.James@asc.com) are also returned.
- To search only on primary business identifier values, enter the value as
Primary: valuein the Search field
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 Track Instances page is case sensitive.
- To search for primary and secondary identifier values, enter a value, and click Search. For example, assume the primary value is
- 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 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.
For Orchestrated Integrations
Follow these instructions to track business identifiers in orchestrated integrations.
- From the menu, select View Activity Stream to view the
message flow. The activity stream shows details about the movement of the
message through the integration, including where any failures occurred. For
orchestrated integrations, the message flow through each action (for example,
any defined switch action branches) is also shown. The date and time according
to your user preferences are displayed.
- Perform the following tasks in the Activity Stream section.
Click ... To ... Download a ZIP file of the complete activity stream. Display the activity stream on a full page. This link works as a toggle to expand and collapse the activity stream. Close the activity stream.
- Click Message to view the payload details for the action.
- If your integration includes any looping actions (such as for-each, while, and others), expand
Iteration to view flow execution inside the loop
(available if you enabled tracing to include the payload when you activated your
integration).Any errors are displayed in red. Instances with errors are displayed in a descending execution sequence to show the error at the top.
- Click Error to show the error message.
- Perform the following tasks in the Message section.
Click ... To ... Download a ZIP file of a specific message payload. Copy the payload to the clipboard. Each Message section includes this option.
Note: Because payload information is derived from log files (which can rotate when newer data gets written), older instances may no longer show the payload information in the activity stream.
Display the payload on a full page. This link works as a toggle to expand and collapse the payload. Close the Message section.
For Basic Routing Integrations
Follow these instructions to track business identifiers in basic routing integrations.
- From the 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.
- 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.