Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'Usage Notes' moved back to end

...

Note that the node parameters - param3 and param4 are set and edited using JOE's XML editor, which is accessed using the OpenXML button shown in the screenshot.
(See also the Example in Detail section below.)

Usage Notes

This flexible use of parameters cannot be achieved using normal order parameters. It could be achieved by using job parameters, but if the same job is used at multiple steps in a job chain or in different job chains you would have to define multiple instances of that job, although it is the same job implementation.

For example, if a job chain consisted of three steps:

  • 1.transfer a file by FTP to host a,
  • 2.transfer a file by FTP to host b,
  • 3.delete file.

You could use the same job for steps 1 and two using different parameters for each job.

In the current example we use the same job twice, but as you have seen from the log, with different parameters.

The example in detail:

When using hot folders, the configuration monitor looks for the job chain parameter file in the current hot folder and expects the name job_chain_name.config.xml. So in this case, the name of the job chain parameter file is chain_a.config.xml.

...

  • The second <params> element is a child of <process state="second">. It configures parameters for the second node (called "second") of the job chain. It overwrites the param2 parameter and sets it to xyz. param3 is not set at all, thus it doesn't appear in the log for state second
  • param4 is defined in the same way as in state first, but this time the resulting value is different because param2 has been overwritten for this state.

Usage Notes

This flexible use of parameters cannot be achieved using normal order parameters. It could be achieved by using job parameters, but if the same job is used at multiple steps in a job chain or in different job chains you would have to define multiple instances of that job, although it is the same job implementation.

For example, if a job chain consisted of three steps:

  • 1.transfer a file by FTP to host a,
  • 2.transfer a file by FTP to host b,
  • 3.delete file.

You could use the same job for steps 1 and two using different parameters for each job.

In the current example we use the same job twice, but as you have seen from the log, with different parameters.

Scope / Application

In job chain parameter files the ${paramname}-syntax can be used to reference:

...