Page History

...

-AgentId <String>
A JS7 Controller cluster requires a one an Agent to be assigned the role of a cluster watcher.
Such an Agent will be considered if the JS7 Controller cluster decides about a fail-over situation withwhen
no a network connection being available between primary and secondary JS7 Controller instances is not available.

Therefore this setting is not considered when adding a Standalone Controller.
The
This parameter specifies a unique identifier for an Agent. This identifier cannot be modified during the lifetime of an the Agent.
In order to modify the Agent identifier the Agent has to be terminated and
journals have to be cleaned up.

...

-AgentName <String>
The name of an Agent is used e.g. in job assignments of a workflow. During deployment the Agent Name
is replaced by the respective relevant Agent ID for the Controller to which the workflow is deployed.
Should
If deployments of the same workflows be are performed to a number of Controllers then for each Controller
the same Agent Name has to be configured for each Controller (pointing to a different Agent ID from Agents' alias names).

...

-ControllerId <String>
Specifies the Controller ID that should be used if an existing Controller is re-registered.
When adding Controllers, the ControllerID should be empty, : when updating Controllers, the Controller ID has to be specified.

...

-AuditComment <String>
Specifies a free text that indicates the reason for the current intervention, e.g. "business requirement", "maintenance window" etc.

The Audit Comment is visible from the Audit Log view of the JOC Cockpit.
This parameter is not mandatory, however, the JOC Cockpit can be configured to enforce require Audit Log comments for all interventions.

...

Adds a Standalone Controller to JOC Cockpit that which is identified by its Url.

...

Updates an existing Standalone Controller that which is identified by its Url to a different URL or title.

...