Page History
...
Restarts a JS7 Controller Instance and optionally performs cluster fail-over
SYNTAX
Restart-JS7ControllerInstance [[-Url] <Uri>] [[-Action] <String>] [-NoFailover] [-Service] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [-WhatIf] [-Confirm] [<CommonParameters>]
...
A JS7 Controller instance is restarted. In a JS7 cluster by default a fail-over
to the passive standby cluster member is performed by default.
The following REST Web Service API resources are used:
* /inventory/releasable
PARAMETERS
Url
-Url <Uri>
Optionally the Url of the Controller to be restarted can be specified.
Without this parameter the active Controller instance will be restarted.
Consider Note that restarting a passive standby Controller instance in a JS7 cluster cannot does not perform
a fail-over as the current cluster member is passiveoperation.
| Required? | false |
| Position? | 1 |
| Default value | |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
...
-Action <String>
Restarting a Controller instance includes the following actions:
* Action 'terminate' (Default)
** no new tasks are started.
** running tasks are continued to complete:
*** shell jobs will continue until their normal termination.
*** API jobs complete a current spooler_ process () callstep.
** JS7 Controller terminates normally.
* Action 'abort'
** no new tasks are started.
** any running tasks are killed.
** JS7 Controller terminates normally.
...
-NoFailover <SwitchParameter>
This switch prevents a fail-over to happen from happenning when restarting the active Controller instance
in a cluster. Instead, the restarted Controller instance will remain the active cluster member.
...
-Service <SwitchParameter>
Retarts the JS7 Windows service.
Without
When this parameter being is not specified JS7 will be started in
its respective the appropriate operating mode, i.e. service mode or dialog mode.
...
-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, however, the JOC Cockpit can be configured to enforce require Audit Log comments for any all interventions.
| Required? | false |
| Position? | 3 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
-AuditTimeSpent <Int32>
Specifies the duration in minutes that the current intervention required.
This information is visible with 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.
...
-AuditTicketLink <Uri>
Specifies a URL to a ticket system that keeps track of any interventions performed for JS7.
This information is visible with shown in the Audit Log view of JOC Cockpit.
It can be useful when integrated with a ticket system that logs interventions with JS7.
...
Terminates and restarts the JS7 Controller. In a cluster the active cluster member is restarted and a fail-over takes place to the passive standby cluster member. Use -of the -NoFailover switch prevents the switch-over.
...
PS > Restart-JS7ControllerInstance -Url (Get-JS7ControllerStatus).Active.Url
Retarts Restarts the JS7 Controller active cluster member or standalone instance.
...
PS > Restart-JS7ControllerInstance -Url (Get-JS7ControllerStatus).Passive.Url -NoFailover
Retarts Restarts the JS7 Controller passive standby cluster member. Consider use of the -NoFailover switch as a passive standby cluster member cannot switch-over to an active cluster member.
...
PS > Restart-JS7ControllerInstance -Service
Retarts Restarts the JS7 Controller Windows service.
Overview
Content Tools