Introduction

If an Agent should no longer be used, then it can be taken out of operation. This is a process that is not limited to deleting an Agent but requires taking a few prerequisite steps.

The JS7 Controller keeps track of a consistent inventory of scheduling objects such as Workflows:

• If an Agent should be deleted that is assigned a Job in an existing Workflow, then the Controller will deny deletion of the Agent as otherwise Workflows would become inconsistent.
• If Orders exists for a deployed Workflow then the Controller will deny removal of the related Workflow as otherwise Orders would become inconsistent.
• An Agent can be deleted only after no Workflows and no File Order Sources referencing the Agent are available with the Controller.

Taking an running Agent out of Operation

The operation to take an Agent out of operation includes to cleanup references to the Agent from existing scheduling objects.

• Cleanup is performed while the Agent is running and is connected to the Controller.
• Deletion of the Agent is performed after cleanup.

Cleaning up Agent References

Agents can be deleted only if no Jobs and no File Order Sources are assigned the given Agent.

How to identify Agent References

The Workflows view offers to filter workflows by Agents:

• In the left panel the tree view offers the (chevron down) icon at folder level that will display all workflows of the current folder and of any sub-folders recursively in the right panel.
• The right panel offers the Agents filter button that allows to select one or more Agents for which workflows are displayed.
  
  

How to bulk update Agent References

Users can apply the Search & Replace operation for Agent assignments at workflow level that is available in the JS7 - Workflow Editor.

• When displaying the workflow in the Inventory sub-view the Search & Replace operation is offered from the right upper corner of the view.
• The operation allows to select one or more Agents that should be replaced.
• The operation expects an Agent to be selected that acts as the replacement.
  
  

Users can apply the JS7 - Inventory Search function to replace Agent assignments across workflows:

• Search for the return type: workflows
• Open the Advanced search criteria and select the Agent that should be replaced across workflows.
  • Optionally specify one or more folders where to look up workflows.
  • Optionally specify that deployed/released objects only should be considered.
• Hit the Search button to get the list of resulting workflows that reference the Agent.
  
  

The list of resulting workflows can look like this:

• Select desired workflows from the result lislt.
  
  

When hitting the Update Job button a popup window is displayed that allows to specify values that will be updated in all jobs of the selected workflows:

• Select the Standalone Agent or Subagent Cluster that should act as a replacement.
• Consider that the checkbox rigth to the Agent selection has to be checked to activate the replacement.
  
  

How to deploy/revoke objects holding Agent References

Users first should check if orders are assigned existing versions of Workflows and File Order Sources. Such orders should be completed or should be cancelled as they prevent deletion of old versions of Workflows and File Order Sources from the Controller.

Users can deploy changes to Agent references or can revoke related objects from the Controller:

• Agent references in Workflows and File Order Sources can be modified manually or by bulk operations explained above. Such changes to Workflows and File Order Sources have to be deployed to a Controller to make changes effective. 
• As an alternative, users can revoke Workflows and File Order Sources from a Controller. The objects will be deleted from the Controller but will remain with the inventory in draft status.

Deleting/Revoking an Agent

Users find the following options in the Manage Controllers/Agents page:

• Each Agent's action menu offers the delete and revoke operation. A number of Agents can be selected for the bulk operation to delete/revoking an Agent.
• If the Agent is deleted, then it will be removed from the Controller and from the inventory.
• If the Agent is revoked, then it will be removed from the Controller and will remain in the inventory in undeployed status.

Taking an uninstalled Agent out of Operation

Users should avoid this scenarion and should take Agents out of operation while they are running.