nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

instantiating workflow model and attaching files

padmanabh

Hi,

I am currently working on TeamSite 671 on Linux. I am using workflows created using workflow modeler.

My goal is to

1. Start a workflow (model) from a perl script automatically.

2. Attach files to it before instantiating the workflow so that the postprocessor can run on them.

I went through the command line guides and to me it appears that using iwjobc and iwinvokejob may be the way to start the target workflow. Calling iwjobc needs a Job Specification File of the target workflow. One method to get the Job Specification File of the workflow is to run it in Debug mode and get the xml that is generated just before instantiating the job. Once we get this Job Specification File (say jsf.xml), we can call

My $Wfid = iwjobc jsf.xml

This will return the workflow id.

Then we can call

Iwinvokejob $wfid and this will start the job.

This looks quite straight forward however, I could not find a way to add files to this workflow.

Then I looked at the workflow modeler guide and it talks about Pre-Processor and Post-processor java code (chapter 9). I can use this custom java code to attach files to the workflow in the in process state. However I am not sure how to pass the target files names from the perl script to this code yet. Also it’s not known to me how a JobSpecificationFile can be generated at runtime from a perl script. I need to find out if there is any command line utility that allows us to create job specification file for a workflow model.

Please let me know if this is a correct way to achieve the above goal. I would really appreciate if you could explain me the correct steps with a simple example.

Thanks a lot for your help!

Find more posts tagged with

Comments

Adam Stoller

I am less familiar with the means of initiating a WFM from the command line, other than I believe it is the iwmodelc CLT that you should use in that case.

If you do start from a job specification file - you can edit the file and include your own <files>...</files> element within the specification of the start task, include the list of files there (area-relative paths) and then run iwjobc -i on the file (the

-i

flag incorporates the iwinvoke part within the running of iwjobc instead of two separate commands)

padmanabh

Hi Ghoti,
Thank you very much for your quick response and thanks for reminding me of the iwjobc -i option!

The issue here is that iwmodelc doesn't accept parameters. We set these parameters (like attaching the file) on the first task, after the wf has been kicked-off. However it's required to use these parameters before instantiating the workflow, so that post-processor can use it.

If command line is not the best option, could you please suggest me an alternative that'll work better in this situation?

Also is there any way to generate Job Specification Files from workflow models? If yes, please tell me how? If no, then how iwjobc works with workflow models?

Thanks for your help!

RajatChopra

Hi Ghoti,
....

Also is there any way to generate Job Specification Files from workflow models? If yes, please tell me how? If no, then how iwjobc works with workflow models?

Thanks for your help!

Hi,
Were you able to find a way to generate an XML Specification for a wfm? I wasn't able to get anything from the manuals.

-Rajat

Adam Stoller

Hi,
Were you able to find a way to generate an XML Specification for a wfm? I wasn't able to get anything from the manuals.

-Rajat

The subject line and the post content do not match. To generate the job specification file, you need to enable

debug="true"

in the available_models.xml file, for the particular WFM. When the job is instantiated it will display the job specification within the browser window from which you can copy/paste into a file (it might actually put it into a file too, not sure)