...

The Agent's journal is available from a number of files in the following locationlocations:

• Unix: /var/sos-berlin.com/js7/agent_<port>/state
• Windows: C:\ProgramData\sos-berlin.com\js7\agent_<port>\state
• Users can choose different locations Note that a different location may have been specified when setting up an the Agent.

When an Agent's journal is deleted or damaged then this indicates means a severe loss:

• If a Controller was connected to the Agent then the Controller will know the respective orders and status information.
• If no a Controller was has not been connected to the Agent for some time then there is no way in knowing what jobs have been executed by the Agent for the time between the loss of the connection loss with the Controller and the loss of the Agent's journal.
  • The Agent's agent.log file holds information about orders and jobs being processed.
  • For each job a pair of temporary files for output to the stdout and stderr channels is created in the Agent's JS7_AGENT_DATA/work/tmp directory. These files are dropped after job execution if the Agent can report back execution results to a Controller and otherwise remain in place.

Initial Operation

Find information from Issues occurring during initial operation are described in the JS7 - How to troubleshoot Agent Initial Operation article.

...

• Problem: If initial operation is successfully completed for an Agent has been completed successfully and due to some weird reason the Agent's journal is deleted later on is deleted , then this may fail the cause coupling between Controller and Agent to be lost.
  • The JOC Cockpit will report the Agent status "Shutdown". When hovering the Agent status with the mouse then the full error message will be displayed, for example
    • AgentNotDedicated: This Agent has not been created yet.
• Solution: This problem can be resolved by restarting the Agent. At the point in time of Agent restart at which the Agent is restarted the JOC Cockpit and Controller have to be active and connected. In case that If the problem to couple with coupling the Agent persists, then re-register the Agent from the JOC Cockpit using the "Edit" action menu and submit the same settings for the Agent as before.
• Implication: This operation includes to loose  This operation does not recover information about past job executions that have not yet been added to the JOC Cockpit history.

...

• Problem: Assume that initial operation is successfully completed for an Agent and due to some weird reason the Agent's journal later on is damaged.  This This may fail the cause coupling between Controller and Agent to be lost.
  
  • The JOC Cockpit will report the Agent status "Coupling failed" or "Shutdown". When hovering the Agent status with the mouse then the full error message will be displayed, for example
    • AgentNotDedicated: This Agent has not been created yet.
• Solution: This problem can be resolved by removing any files in the Agent's JS7_AGENT_DATA/state directory. At the point in time of Agent restart at which the Agent is restarted the JOC Cockpit and the Controller have to be active and connected. In case that If the problem to couple with coupling the Agent persists, then re-register the Agent from the JOC Cockpit using the "Edit" action menu and submitting submit the same settings for the Agent.
• Implication: This operation includes to loose  This operation does not recover information about past job executions that have not yet been added to the JOC Cockpit history.

...

If an Agent can be accessed by the Controller but cannot be coupled then the JOC Cockpit will display this a status, for example indicating such as "Coupling failed", "Shutdown" or similar status information.

Reset

Using the "Reset" operation from the Agent's action menu in the JOC Cockpit "Manage Controllers/Agents" page performs the following operations:

...

Note: This operation includes the danger of unintentionally choosing an Agent that is registered with a different Controller, for example if different Controllers for production and non-production environments are used. This operation includes effectively means that the Controller hijacks the Agent and drops any journal information of for that Agent. This operation can safely be used if no workflows and tasks are present with an Agent and for example the Controller ID should be changed.

...

After deleting the Agent from the JOC Cockpit and from the Controller the Agent can be restarted and can be registered with the same steps as described for initial operation.