JS7 JobScheduler

Space shortcuts

Page tree

Name

Set-JS7Controller

SYNOPSIS

Registers a Controller and Agents

SYNTAX

Set-JS7Controller [-Controller] <PSObject[]> [[-AgentId] <String>] [[-AgentName] <String>] [[-AgentUrl] <Uri>] [[-ControllerId] <String>] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [-WhatIf] [-Confirm] [<CommonParameters>]

DESCRIPTION

The cmdlet registers a Controller either for a Standalone Controller instance or for
a primary and a secondary Controller Cluster instance.
A Controller Cluster requires an Agent to be added that acts as a cluster watcher.

The following REST Web Service API resources are used:

* /controller/register

PARAMETERS

Controller

-Controller <PSObject[]>
Specifies an array of Controller instances that will be added:

* For a Standalone Controller a single instance is specified
* For a Controller Cluster a primary instance and a secondary instance are specified

Controller instance objects can be created from the New-JS7ControllerInstance cmdlet.

Required?true
Position?1
Default value
Accept pipeline input?false
Accept wildcard characters?false

AgentId

-AgentId <String>
A JS7 Controller cluster requires 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 when
a network connection between primary and secondary JS7 Controller instances is not available.

Therefore this setting is not considered when adding a Standalone Controller.

This parameter specifies a unique identifier for an Agent. This identifier cannot be modified during the lifetime of the Agent.
In order to modify the Agent identifier the Agent has to be terminated and
journals have to be cleaned up.

Required?false
Position?2
Default value
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

AgentName

-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 relevant Agent ID for the Controller to which the workflow is deployed.

If deployments of the same workflows are performed to a number of Controllers then
the same Agent Name has to be configured for each Controller (pointing to a different Agent ID from Agents' alias names).

Required?false
Position?3
Default value
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

AgentUrl

-AgentUrl <Uri>
Specifies the URL for which the Agent is available. A URL includes the protocol (http, https), hostname and port
for which an Agent is operated.

Required?false
Position?4
Default value
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

ControllerId

-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.

Required?false
Position?5
Default value
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

AuditComment

-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 require Audit Log comments for all interventions.

Required?false
Position?6
Default value
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

AuditTimeSpent

-AuditTimeSpent <Int32>
Specifies the duration in minutes that the current intervention required.

This information is shown in the Audit Log view. It can be useful when integrated
with a ticket system that logs the time spent on interventions with JS7.

Required?false
Position?7
Default value0
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

-AuditTicketLink <Uri>
Specifies a URL to a ticket system that keeps track of any interventions performed for JS7.

This information is shown in the Audit Log view of JOC Cockpit.
It can be useful when integrated with a ticket system that logs interventions with JS7.

Required?false
Position?8
Default value
Accept pipeline input?true (ByPropertyName)
Accept wildcard characters?false

WhatIf

-WhatIf <SwitchParameter>

Required?false
Position?named
Default value
Accept pipeline input?false
Accept wildcard characters?false

Confirm

-Confirm <SwitchParameter>

Required?false
Position?named
Default value
Accept pipeline input?false
Accept wildcard characters?false

about_JS7

EXAMPLES

-------------------------- EXAMPLE 1 --------------------------

PS > Set-JS7Controller -Controller ( New-JS7ControllerInstance -Url https://controller-standalone.sos:4443 -Title 'STANDALONE CONTROLLER' )

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

-------------------------- EXAMPLE 2 --------------------------

PS > Set-JS7Controller -Controller ( New-JS7ControllerInstance -Url https://controller-standalone.sos:4443 -Title 'SOLO CONTROLLER' ) -ControllerId jobscheduler

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

-------------------------- EXAMPLE 3 --------------------------

PS > $primary = New-JS7ControllerInstance -Url https://controller-primary.sos:4443 -Title 'PRIMARY CONTROLLER'
$secondary = New-JS7ControllerInstance -Url https://controller-secondary.sos:4443 -Title 'SECONDARY CONTROLLER'
Set-JS7Controller -Controller $primary,$secondary -AgentId 'agent_001' -AgentName 'primaryAgent' -AgentUrl https://agent-primary.sos:4443

Creates two cluster members and adds the Controller Cluster to JOC Cockpit. In addition, an Agent is added that acts as cluster watch.

  • No labels