Page History
...
This brings forward the following popup window:
Explanation:
- The first group of input fields specifies the Agent Cluster:
- Agent ID: A unique identifier of the Agent Cluster. Uniqueness is required for all Standalone Agents and Agent Clusters assigned to a Controller. This identifier cannot be changed later on.
- Agent Cluster Name: The name of the Agent Cluster as displayed in the JOC Cockpit GUI. The name can be changed at any later point in time.
- Title: An individual description that can be searched for.
- Alias NameNames: The same Agent Cluster can appear with a number of alias names. This allows the use of different Agent Clusters, for example is available from a different name. This can be helpful if distinct Agent Names should be assigned the jobs, for example if more Agents are used in a production environment , to be mapped to the use of fewer Agent Clusters using alias names in a test environmentthat map to a smaller number of Agents in a non-production environment.
- Process Limit: Agents can execute an unlimited number of parallel processes. Users can limit parallel processes to prevent exhausting a server's resources and to make orders wait until the next process will be available.
- The second group of input fields specifies the Primary Director Agent:
- Subagent ID: A unique identifier of the Subagent. Uniqueness is required for all Director Agents and Subagents in the same Agent Cluster. This identifier cannot be changed later on.
- Title: An individual description that can be searched for.
- URL: The protocol HTTP or HTTPS, host name or IP address and port which the Controller can use to access the Director Agent.
- The third group of input fields specifies the Secondary Director Agent should Director Agents be clustered.
...
Overview
Content Tools