Skip to main content
Version: 4.2.5

Running and monitoring integration flows

You can track the progress of your integration flows by studying the various tracking entities (Nodes, Events, Jobs and Logs) in the Tracking section. For each subsection, you can create entity filters to group, sort and filter its contents (for more information, see Entity filters).

The Tracking section also contains the System monitor and the OS Event Log which provide you with information about active services and runtime.

The table below contains common tasks related to running, monitoring and tracking integration flows.

Create an Event

  1. Click the Create Event button () on top of the system explorer.
  2. Enter the required information (Event type, Event params etc.) in the dialog box.

Create an Event on a Node

  1. Select Tracking -> Nodes.
  2. Select the entity filter that displays the Node you want to create an Event on.
    • In the Document area, select the Node and click the Create Event button on the Document header.
      OR
    • Right-click the Node and select Create Event in the shortcut menu.
      OR
    • In the Document details, select the Details tab and click the Create Event button.

Create an Event from a Timer

  1. Select Configuration -> Timers.
  2. Click the Add Timer button in the Document header.
  3. Set the Timer properties (for example, when you want the Timer to expire/trigger)
  4. In the Document details pane, add the Event type(s) that you want to associate with the Timer. When the Timer expires, Events of the specified Event type(s) will be generated.

You can also create Events directly from an existing Timer without having to wait for the Timer to expire:

  1. Select Configuration -> Timers.
  2. Select the entity filter that displays the Timer you want to create an Event (or Events) from.
    • In the Document area, select the Timer and click the Create Timer Events () button in the Document header.
      OR

    • Right-click the Timer and select Create Timer Events in the shortcut menu.

      note

      The Create Timer Events command will create Events for all Event Types associated with the Timer. Timer Events can be created even if the Timer is not active, but if this is the case, a warning message is displayed in the dialog box and the user is provided with the option to abort the operation.

Re-create an Event

  1. Select Tracking -> Events.
  2. Select the entity filter that displays the Event that you want to re-create.
    • Select the Event and click the Re-create Event button () on the Document header.
      OR
    • Right-click the Event and select Re-create Event in the shortcut menu.
      OR
    • In the Document details, select the Details tab and click the Re-create Event button.

Re-run a single or multiple Jobs

  1. Select Tracking -> Jobs.
  2. Select the entity filter that displays the Job (or Jobs) that you want to run again.
    • In the Document area, select the Job/Jobs that you want to run and click the Re-run Job button () on the Document header.
      OR
    • In the Document details, select the Details tab and click the Re-run Job button.
note

Not all Jobs can be re-run – for more information, see Job.

Go to Job

Right-click any Event, Node or Log entry and select Go to Job to navigate directly to its parent Job.

Delete a Job

It is possible to delete Jobs that have not executed: Simply select the Job and press Delete (or use the shortcut menu). Jobs that have executed or executed and failed (and will not run again) cannot be deleted.

Mark a Job as Lost

Under normal circumstances, the management service automatically identifies lost Jobs and changes the Job state accordingly. However, in some cases it is necessary to change the state manually. For example, a server part Job could be running on a server which is no longer available.

To mark a Job as lost: Select the Job, right-click and select Mark as Lost. The Job state now changes to Lost provided that the service to which the Job belongs has been stopped or is not installed.

Note the following:

  • The Job must be a server part Job in the Running state.
  • Before you change the Job state, verify that the Job is not actually running.

For more information about Job states, see Job.

View the arguments of a Job

To view the arguments of a Job:

  • Select the argument in the Document details area and then click View selected argument. A dialog box with the content of the selected argument value opens. All arguments can be viewed, regardless of whether its value is displayed or not currently loaded.

Set a Tracking page

You can use a Component definition to customize the content of the main tracking page:

  1. Create a Component definition (Adapterflow, Workflow, or Script) that returns the tracking data you want to present.

    note

    The Component definition must have a result value set.

  2. Select the Tracking section in the system explorer.

  3. Right-click and select Select tracking page content...

  4. Check the Show custom content checkbox.

  5. Select the Component definition.

  6. Click Ok. The contents of the tracking page (the "document" area) is updated.

Clean up tracking entities

We recommend that you use the Daily Maintenance functionality in the Common package to set up a regular clean-up routine for tracking entities. Keeping a large number of tracking entities (for example log entries) can effect performance and make it difficult to get a good overview of integration flows. The Common package is free to download from iCore Tech.

See Also

System monitor
Display Node content with stylesheet
Editing Node contents