Restrict use of the same name for Agent Cluster, Agent ID, and Agent Name

Desired Uniqueness of Controller/Agent Configuration Items

• Controller
  • The Controller ID is unique within the scope of the JS7 inventory.
• Standalone Agents
  • The Agent ID is unique within the scope of the JS7 inventory.
  • The Agent Name is unique within the scope of a Controller.
• Cluster Agents
  • Cluster
    • The Agent Cluster ID is unique within the scope of the JS7 inventory.
    • The Agent Cluster Name is unique within the scope of a Controller.
  • Subagents
    • The Subagent ID is unique within the scope of the JS7 inventory.
  • Subagent Cluster ID
    • The Subagent Cluster ID is unique within the scope of a Controller.

Supported Use Cases

• Installation
  • Users can operate any number of Controllers using different Controller IDs with the same JOC Cockpit.
  • Users can use the unique Agent ID for deployments of Agents.
  • Agents can report to the JS7 Logging Service using their unique Agent ID, see JOC-1828.
• Deployment of Scheduling Objects
  • Users can deploy the same objects such as workflows to a number of Controllers provided that Agent Names assigned the Jobs and File Order Sources are available with each Controller.
    • This applies to Agent Names and to Alias Names used by Standalone Agents.
    • This applies to Agent Cluster Names and to Subagent Cluster IDs.
  • Users can rollout scheduling objects to environments such as dev->test->uat->prod without the need to change 
    • the Agent Name or Alias Name of a Standalone Agent assigned the Jobs and File Order Sources.
    • the Agent Cluster Name and Subagent Cluster ID assigned the Jobs and File Order Sources.