Job Status Example Profile Workflow
The profile has the following workflow:
- The profile receives a trigger that initiates back-end processing every 10 seconds.
- The profile checks if there already is a message being processed. If so, the system puts the trigger into the pending state by saving it to a dedicated location in the Data Storage.
- After processing on the back end is done (emulated), the profile gets the trigger in the pending state from the Data Storage and puts it into the processing state by starting processing on the back end.
The profile contains the following routes:
Job Route
This route emulates back-end processing (delays processing for 30 seconds).
Route Components Description:
| Get data for Processing
|
File System Inbound |
Picks up data ready for processing. |
| Delay
|
Delay |
Delays processing by 30 seconds to emulate data processing. |
| Result of Processing
|
File System Outbound |
Stored processing results in a dedicated file system folder. |
Trigger Processing Route
This route represents the main processing flow for the incoming triggers and puts them to the corresponding states to make sure that only one of the incoming triggers invokes the back-end processing.
Route Components Description:
| Timer Reporter
|
Timer Reporter |
Fires triggers every 10 seconds. |
| Get Current
|
Data Storage Inbound |
Attempts to get data from
the current folder. Presence of data
in this folder means that there is an item currently being processed
on the back-end side. |
| Found?
|
Router |
Checks to see if data has been found in the Data Storage. |
| Put to Pending
|
Data Storage Outbound |
In case there is an item being processed, puts the trigger to the pending state (stores the trigger in a dedicated location). |
| Put to Current
|
Data Storage Outbound |
Puts the data into the processing state. |
| Start Processing
|
Data storage Inbound |
Picks up data from the Data Storage to start processing. |
| Get Current
|
Data Storage Inbound |
gets the current trigger. This is performed
in order not to lose the trigger
in case of a profile crash. |
| To Processing
|
File System Outbound |
Puts data ready for processing on the Job route to a dedicated file system folder. |
| Processing Result
|
File System Inbound |
Picks up processed data (emulated) from a dedicated file system folder. |
| Delete Current
|
Data Storage Inbound |
Removes the processed item from the current
state. |
| Extract Pending
|
Data Storage Inbound |
Moves the item from the pending
to the current state. |
| Move to Current
|
Data Storage Outbound |
Moves pending data into the current (processing) state. |
| Put to Start Processing
|
Data Storage Outbound |
Triggers the back-end processing start. |
