Page History
...
Download (upload .json): pdfFileVariablessetResourceJob.workflow.json
You can use the job wizard like this:
Explanation:
- Add an empty job from the instruction panel.
- Specify a name and a label for the job.
- Select an Agent.
In a next step invoke the job wizard that you find in the upper right corner of the job property editor. The wizard brings up the following popup window:
Explanation:
- From the list of available job templates select the SetJobResourceJob.
Then hit the "Next" button to make the job wizard display available arguments:
Explanation:
- There are optional arguments for this job to identify the file carrying variables:
- if the job is used in a workflow to which orders are added from JS7 - File Watching then the job will use the internal
file
variable that specifies the incoming file and does not require an argument. - if the job is used in a workflow not subject to File Watching then the
js7_source_file
argument is used to specify the path to the file carrying variables.
var1
argument which translates to the fact that from the incoming file a line is expected to specify the variable like this:var1=some value
Controller to which the Job Resource should be deployed:- The default Controller is the one that is currently selected by the user.
- if the job is used in a workflow to which orders are added from JS7 - File Watching then the job will use the internal
- Select the check box provided with each argument if you want this argument to be added to the arguments of the FileOrderVariablesJob SetJobResourceJob template.
When hitting the Submit button the wizard adds the required arguments to the job which should look like this:
Documentation
The Job Documentation including the full list of arguments can be found under: https://www.sos-berlin.com/doc/JS7-JITL/SetJobResourceJob.xml
...
Name | Required | Default Value | Purpose | Example |
---|---|---|---|---|
job_resource | yes | The path to the Job Resource that should be created or updated. Both specification of a path and specification of the name can be used. | /resources/my_vars | |
| yes | The name of the variable in the Job Resource (case-sensitive). | var1 | |
value | yes (one of file or value is required.) | The value of the variable:
| ||
file | yes (one of file or value is required.) | The name of a file: The content of the file will be used as value in the job resource. The content is stored with to_file(). Additionally the variable
| ||
time_zone | no | If a Java data pattern is specified for the The time zone is specified from a string, for example "GMT", "Europe/London". Valid time zone strings as explained with https://en.wikipedia.org/wiki/List_of_tz_database_time_zones can be specified. If this parameter is omitted then the time zone that the Agent is operated for will be used. | ||
environment_variable | no | The name of an environment variable in the Job Resource that should automatically be populated with the value specified for the | ||
controller_id | no | The Controller ID identifies the Controller to which the updated Job Resource will be deployed. | ||
encipherment_certificate | no | The certificate The CA signed or self-signed X.509 certificate. Alternatively the public key can be specified. This variable is normally provided via a job resource that is managed with the certificate management. When this variable is set the value will be encrypted. The encrypted value will contain:
When the certificate is specified the value will be encrypted and then added to the job resource. |
Further Resources
- JS7 - JITL Common Variables
- JS7 - How to make a global Business Date variable available to jobs
- JS7 - How to update a Job Resource using the REST Web Service API from the Unix Shell