Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The incoming file can hold pairs of names and values similar to the temporary file available from the JS7_RETURN_VALUES environment variable for return values of shell jobs: <name>=<value>.
    • pairs of names/values are separated from each other by EOL which can be CR, CRLF or LF.
    • The <value> can include any Unicode characters.
  • For the handling of incoming files the following applies:
    • If the incoming file holds pairs of names and values for variables then they are added to the order as return values from the JITL FileOrderVariablesJob template.
    • If the incoming file is empty then no return values are created and no error occurs.
    • If the incoming file includes content that does not match name/value pairs then an error is raised.

The JITL job does not use any arguments to specify its processing mode. Instead, users can add any arguments to this job that are expected to match the name of a name/value pair in the incoming file:

  • Arguments Job arguments that are not assigned a value are considered optional for the incoming file. Respective return values are created only if the incoming file provides the variable. This includes that the incoming file specifies an empty value for the variable.
  • Arguments Job arguments that are assigned a value are considered optional.
    • If the incoming file does not provide the variable then a return value with the JITL Job's default value is created.
    • If the incoming file provides a variable - optionally with an empty value - then a return value with the value from the incoming file is created.
  • For pairs of names/values for which no arguments are specified the JITL Job will raise an error.
  • Example of an incoming file:

    var1=value1
    var2=value2
    var3=

    • The variables var1 and var2 will be created with their respective values. For var3 an empty value will be returned from the JITL Job.

Display feature availability
StartingFromRelease2.4.01

Usage

When defining the job either:

...

NameRequiredDefault ValuePurposeExample
js7_source_fileno

Specifies the path to the incoming file:

  • If the workflow in use is subject to File Watching then this argument is not required as the internal file variable will be used.
  • If the workflow is not subject to File Watching then the path to the incoming files has to be specified with the js7_source_file variable

Desired state of the JS7 component: 

  • inactive:  indicates a switch-over operation by which the component is set to the inactive state.
  • active:  indicates a switch-back operation by which the component is set to the active state.
/tmp/file/some_file.csv

<variable>

yes

Specifies the identifier of a Standalone Controller or Controller Cluster

  • if the controller_host argument is used and
  • a variable that is expected from the incoming file:

    • If a value is specified then it is applied as a default value in case that the incoming file will not provide the variable.
    • If no value is specified then then incoming file is required to specify the variable and otherwise an error is raised.

    Any number of variables can be specified like this

    if the JOC Cockpit is connected to more than one Controller

    .

    var1

    Further Resources