ION OneView components / event sources

ION OneView provides information related to the messages that were processed and which components were involved. This information is represented in both views: Timeline and Advanced.

In Timeline View, a graphical representation of this information is available. Several icons are used to display this information. Icons displayed include the event sources. These sources can be:

  • Configurable components, such as connection points, monitor instances, workflow instance or activation policies.
  • Engines, such as CBM, Activation Policy, Workflow or Activities.
  • The messages handled (original, mapped, updated, and Confirm BOD).
Category Icon Component / Event Source
Connection Points Application Connection Point
Connection Points Database Connection Point
Connection Points JMS Connection Point
Connection Points File Connection Point
Connection Points Web Service Connection Point
Connection Points Business Connection Point
Connection Points nt_ico_ion_api_blue API Connection Point
Flows Filter Flow
Flow Content-Based Routing Flow
Other Activities nt_ico_ion_split Splitter
Other Activities Mapping
Other Activities Workflow from Document Flow
Other Activities Message Listener
Other Activities Message Listener if the message cannot be delivered.
ION Engines Activation Policy / Monitor Engine
ION Engines Workflow Engine
ION Engines ION Container, used for internal event sources. Confirm BOD Manager Engine
ION Engines Activities Engine
Event Management Activation Policy
Workflow Workflow
Event Management Monitor
Event Management nt_ico_alarm_template Alarm Template
Manual Actions Manual Action
Others Unknown Component / Event Source
Messages Original Document / Updated Document / Mapped Document
Messages Confirm BOD

When this icon is shown in the timeline of another document, right-click to navigate to the timeline of the Confirm BOD

Messages Original Document / Updated Document / Mapped Document with timeline link. Right-click to navigate to the timeline of this document

Components that did not finish the processing of a message can temporarily show the retrying flag: