Starting a workflow from withing a perl script

Hello,

I'm trying to initiate a workflow from a perl script using the CreateWorkflow($spec) function. Does anyone know what should the $spec variable contain? The manual just says $spec should contain a workflow specification in the form of a string. But should that string be a path to a job options file, or should $spec contain the full job option XML as one string? Nothing I tried seemed to work.

Thank you very much for any help with this CreateWorkflow function!

Find more posts tagged with

Comments

Adam Stoller

Hello,

I'm trying to initiate a workflow from a perl script using the CreateWorkflow($spec) function. Does anyone know what should the $spec variable contain? The manual just says $spec should contain a workflow specification in the form of a string. But should that string be a path to a job options file, or should $spec contain the full job option XML as one string? Nothing I tried seemed to work.

Thank you very much for any help with this CreateWorkflow function!

For those playing along from home - this is TeamSite::WFsystem's CreateWorkflow() method.

Pandora - it means the latter - a full XML job specification. Note - this is not a WFT, it is what the result of processing a WFT by the instantiator would produce (pure XML, no Perl).

As an alternative - if you have a WFT - consider looking at iwwft_compile.ipl (run perldoc on it for more information)

ISCBorisB

Hello,

I'm trying to initiate a workflow from a perl script using the CreateWorkflow($spec) function. Does anyone know what should the $spec variable contain? The manual just says $spec should contain a workflow specification in the form of a string. But should that string be a path to a job options file, or should $spec contain the full job option XML as one string? Nothing I tried seemed to work.

Thank you very much for any help with this CreateWorkflow function!

I've illustrated a mechanism [post=79356]here[/post] - quite some time ago.
As pointed by Ghoti, "iwwft_compile" represents more traditional way to do this sort of things.

pandora

Thank you very much, ghoti and ISCBorisB. Both ways - running iwwft_compile.ipl and using the script ISCBorisB wrote - work as a charm if the user has a shell account. I was just trying to find an alternative way to initiate a workflow without having to use the command line. The thing is this workflow is being initiated from within another workflow's external task. And when the user doesn't have an access to the command line, the initiation fails. I thought maybe using the CreateWorkflow method will help to get around it but it's still not working.

Thank you very much for your help, much appreciated.

Adam Stoller

Thank you very much, ghoti and ISCBorisB. Both ways - running iwwft_compile.ipl and using the script ISCBorisB wrote - work as a charm if the user has a shell account. I was just trying to find an alternative way to initiate a workflow without having to use the command line. The thing is this workflow is being initiated from within another workflow's external task. And when the user doesn't have an access to the command line, the initiation fails. I thought maybe using the CreateWorkflow method will help to get around it but it's still not working.

Thank you very much for your help, much appreciated.

Are you talking about non-OS users or something else?
If you're working with non-OS users, you pretty much have to use Java - or make the tasks you want to do this kind of thing owned by an actual OS user account.

pandora

Are you talking about non-OS users or something else?
If you're working with non-OS users, you pretty much have to use Java - or make the tasks you want to do this kind of thing owned by an actual OS user account.

Yes, I mean non-OS users...

I ended up forcing the outer workflow to be owned by an OS user. That worked perfectly (thanks ghoti, it's actually disturbing that I didn't think of that earlier). I just have to see now if it'll fly with the client...

Thank you all very much!