Page History

...

Controller Registration using JOC Cockpit as Cluster Watch

Starting from release 2.5.3 and 2.6.0 JOC Cockpit is always used as Cluster Watch, no additional options are offered:

Controller Registration using a Cluster Watch Agent

Starting from release 2.5.3 and 2.6.0 JOC Cockpit is always used as Cluster Watch, no additional options are offered:
 

This dialog allows the Primary Controller instance, the Secondary Controller instance and an Cluster Watch to be specified.

...

This opens the following popup window:

Image RemovedImage Added

Explanation:

• Agent ID: A unique identifier of the Agent. Uniqueness is applied for all Agents registered with the same Controller. This identifier cannot be changed later on.
• Agent Name: The name of an Agent is used, for example, when assigning the Agent to jobs. Similarly to the Agent ID,the Agent Name has to be unique but can be changed later on.
• Title: An individual description which can be searched for.
• Alias Names: The same Agent 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 that map to a smaller number of Agents in a non-production environment.
• Process Limit: Agents can execute an unlimited number 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.
• URL: The HTTP or HTTPS protocol, host name or IP address and port with which the Agent can be accessed from the Controller.

...