Introduction

• The outage of an Agent will stop the execution of workflows with that Agent. Workflows running with Agents that remain available are unaffected.
• Workflows that miss their scheduled execution date will be executed when the Agent becomes available.

• Testing by SOS includes to perform successful tests for the scenario when an Agent becomes unavailable for 24 hours. The test includes to move the Agent's journal files to a new Agent after the 24 hours outage and to modify the Agent registration with JOC Cockpit. Then the new Agent executes the any outstanding workflows from of the previous day and any newly added orders.

• For information about the behavior in case of outages see JS7 - FAQ - What happens to workflows in case of outage of an Agent?

Troubleshooting

The Agent is the component in JS7 that executes the workflow, stores information about execution results and order state transitions in its journal and passes results to the Controller. The outage of an Agent prevents execution of workflows.

An Agent outage can be handled either by resolving the issue with the current Agent, e.g. by restarting, or by relocating the ./state directory to a different Agent provided that access to the same scripts and programs is available that should be executed. The journal of the Agent is stored in the ./state directory. To relocate the journal to a different Agent copy the journal files to the target Agent.

Relocating the Agent's Journal

If Agent1 is facing an outage and Agent2 is running (- on the same server or on a different server ) - then follow the below steps to relocate the Agent's journal from Agent1 to Agent2:

...