Page History

...

File transfer configuration objects can be stored to JOC Cockpit. The configuration is passed on from an XML
object and is converted by the cmdlet to its native JSON reperesentation.

The following REST Web Service API resources are used:

* /xmleditor/schema/assign
* /xmleditor/apply
* /xmleditor/store
* /xmleditor/validate

PARAMETERS

Name

-Name <String>
Specifies the name of the file transfer configuration.
The name is used to display the subtab holding the file transfer configuration in the JOC Cockpit GUI.

...

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

...

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

...

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

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

...

PS > $xml = Get-JS7FileTransferItem -Name 'primaryAgent'
Set-JS7FileTransferItem -Name 'newConfig' -Configuration $xml

Stores the file transfer configuration object to a new entry and name.

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

[xml] $xml = '<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <Configurations/>'
Set-JS7FileTransferItem -Name 'newConfig' -Configuration $xml

Stores the given XML file transfer configuration to the JOC Cockpit inventory.