Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Handling: The System Monitor will be notified to the service related to the Job Chain with the message error. The error message at the System Monitor will stay till the same file is again placed in the monitored directory and the Job Chain ends without errors. That means, that a new file makes the Job Chain end without errors, does not mean that the error is recovered, since the file that has been processed is now another one.

Configuration:

  • XMLs
  • System Monitor

Workflow Execution takes too long

...

Handling: A timer for this Job Chain is set and the System Monitor will be notified about it. The expiration times for the Job Chains are configured with enough time for processing, that means, this is usually used for cases where the Job Chain hanged in a specific step.

Configuration:

  • XMLs
  • System Monitor

SFTP connection refused

Initial Situation: There is a Job Chain that uses SFTP for transferring files. You have a setback configured in this step of the Job Chain, so that if the connection to the SFTP server fails, this step is retried after some time.

...

Handling: The System Monitor will be notified to the service related to the Job Chain with the message error. (to be completed)

Configuration:

  • XMLs
  • System Monitor

Counting number of Workflow Executions

Initial Situation: A specific number of Workflow Executions have to be executed till some specific time. That is, a specific value has to be monitored in order to determine if this quote was reached.

Handling: A new service for History is configured, so that the workflow executions (Job Chains when talking about JobScheduler) send the information that they were executed and finished (with specific values if required) to the System Monitor.

Configuration:

  • XMLs with service_name_on_success
  • System Monitor