Introduction

the File Transfer configuration is managed by the JOC Cockpit GUI from the Configuration->File Transfer sub-view,
the File Transfer configuration - typically an *.xml file - is deployed to Agents that execute File Transfer jobs and is made available from a temporary file.
the File Transfer jobs indicate which File Transfer configuration to use.

JOC offers simplified deployment of File Transfer configuration files (*.xml) to Agents:

Assignment of Job Resource

A File Transfer configuration is assigned a Job Resource like this:

Explanation:

The tree in the left panel holds the Configurations top level element. Using the action menu of this element allows to add a JobResource child element.
Having added the child element the right panel offers to select one of the JS7 - Job Resources that should used to deploy the File Transfer configuration.

Explanation:

Having selected the respective Job Resource two more attributes have to be added:
- variable: the attribute specifies to the name of a variable in the Job Resource that indicates the File Transfer configuration.
- environment_variable: the attribute specifies the name of an environment variable by which the File Transfer configuration is accessible to File Transfer jobs.

The status of a File Transfer configuration is indicated like this:

Explanation:

valid / invalid: the XML document is valid if it complies to the underlying XSD schema. The Validate button is used to perform validation of the XML document. A valid XML document is required for further deployment.
in sync / not in sync: the status indicates if the File Transfer configuration is in sync with the assigned Job Resource. If users modify the File Transfer configuration then such changes are not automatically deployed while editing but result in a not in sync status. The Check button can be used to check if the XML document is in sync.
deployed / not deployed: the status indicates if the File Transfer configuration has previously been deployed. Changes to the File Transfer configuration as indicated by a not in sync status can be deployed with the assigned Job Resource by a use of the Deploy button.

When a File Transfer configuration is deployed then the assigned Job Resource is populated as follows.

The Job Resource is available from the Configuration->Inventory view. By default the Arguments tab is displayed like this:

Explanation:

The Arguments tab shows the name of the Job Resource Variable that holds the File Transfer configuration. The name of the variable corresponds to the respective name indicated with the XML document of the File Transfer configuration specified with the above step Assignment of Job Resource.
The assigned value is the XML document of the File Transfer configuration. Technically the function toFile() is used to indicate that the value should return the path to a file that holds the XML document.
Users do not have to modify the Job Resource variable - the variable and its value are automatically populated when deploying the File Transfer configuration.

The Environment Variables tab is available for a Job Resource like this:

Explanation:

The name of the environment variable corresponds to the respective name indicated with the XML document of the File Transfer configuration specified with the above step Assignment of Job Resource.
The value takes a reference to the name of the variable as specified with the Arguments tab. The name is preceded by a $ character.

File Transfer jobs reference the Job Resource environment variable in a File Transfer job like this:

Explanation:

The -settings argument accepts the path to a File Transfer configuration file.
The YADE_XML environment variable holds the path to a temporary file that is created by the Job Resource variable.
Consider that the same Job Resource is assigned a number of workflows/jobs and Agents.
- If specific Agents should have knowledge of File Transfer configurations only that are applicable to that Agent then manage the File Transfer configurations in tabs per Agent and assign a Job Resource to jobs running for this Agent only.