SetConnect

Configuration

Tracking
Theory of Operation

Tracking is a builtin system which can help to get a better insight in your running workflows. Typically it is very useful for hotfolder workflows which span more then one daemon and/or server. With tracking you can define "Groups" which contain "Flows". A Flow consists of a specified number of Steps and each Step is a certain point in your (work)flow that you want to monitor. These Steps can then be assigned to the properties of actual workflows. Everytime these workflows are active they will log tracking-data to the tracking-database and this data is visualized on an ASP.Net website (IIS required).

Because tracking uses a central database to store all tracking information it's very easy to feed the database from different Agent servers and/or daemons. On every Agent server you must configure the special database-handle "WEB" to point to the tracking database (server).

Requirements

Tracking requires an SQLserver database where it can create the necessary tracking tables. This database must be accessible for all Agent which you plan to include in the tracking system.

The tracking functionality requires Agent WEB to be installed and configured.

Configuration
  • On every server you plan to include in the tracking system you need to configure the "WEB" preset-database. You can do this with the "Manage Databases" option in the "Options" menu of the "Configuration Manager". Note that once you have configured this database and you click "Ok" the necessary tables will automatically be created in the database.
  • Next you need to configure "Groups" and "Flows". You can do this on the "ConfigurationTracking" tab in the "Configuration Manager". A Group can contain one or more "Flows".
  • Once a Group is created you need to create "Flows" in the group. Each Flow can have up to 25 Steps and each Step represents a point in your flow which you want to monitor. Once a Flow is created you can name the Steps in the "Tracking Flow Steps" list in the "Tracking" tab. Don't forget to "Save Steps" after you have changed the description of the Steps.
  • Now that a Group exists which contains a Flow, you can select this Group & Flow in the properties of every workflow (in every Agent server/daemon which points to the same tracking database)..
  • Assign the correct GroupFlowStep to the worklfows which represent these Steps in your flow. Depending on how your (work)flows are setup you can connect a Step to more then one workflow

If Agent WEB was configured correctly you can now login to Agent WEB and use the "Overview" and "Detail" pages to view the tracking information. The "Overview" page contains an overview of all the Flows in a Group. The "Details" page shows more detailed information about a specific Flow in a Group. On this page you will see the different Steps in a Flow and the status of these Steps.

Documentation

Release notes