Invoking a workflow from command line

Is it mandatory to have an Master role to invoke a workflow from command line?

As soon as the user clicks Finish an ipl is invoked in which a workflow is invoked in /iw-bin/iw_cgi_wrapper.cgi/yourscript.ipl and in yourscript.ipl we have the below command:

----------------------------------------------
# /iw-home/teamsite/bin/iwwft_compile.ipl -i < /iw-home/local/config/wft/hn/mhneap/wfParams.xml

ERROR: failed starting job
You must be a master to run iwjobc.

Any help is appreciated.

Thanks,
Tirrudev

Find more posts tagged with

Comments

ISCBorisB

Is it mandatory to have an Master role to invoke a workflow from command line?

As soon as the user clicks Finish an ipl is invoked in which a workflow is invoked in /iw-bin/iw_cgi_wrapper.cgi/yourscript.ipl and in yourscript.ipl we have the below command:

----------------------------------------------
# /iw-home/teamsite/bin/iwwft_compile.ipl -i < /iw-home/local/config/wft/hn/mhneap/wfParams.xml

ERROR: failed starting job
You must be a master to run iwjobc.

Any help is appreciated.

Thanks,
Tirrudev

Whether you run iwjobc directly or through iwwft_compile.ipl with the invoke option you need master privileges.
Before going into more complex options simply try to remove "iw_cgi_wrapper.cgi" (eg, remove impersonation)
from action's url, that *may* help

tirrudev

Thanks for the response Borris.

Can u please let me know how to remove the iw_cgi_wrapper.cgi from the actions url?

Where can i do that/

Thanks,
Tirrudev

Adam Stoller

Whether you run iwjobc directly or through iwwft_compile.ipl with the invoke option you need master privileges.
Before going into more complex options simply try to remove "iw_cgi_wrapper.cgi" (eg, remove impersonation)
from action's url, that *may* help

Actually, I believe that iwwft_compile.ipl was created, in part, to get around the need to be a "master" to instantiate a WFT. iwjobc / iwinvoke job does require "master" privileges.

So if the code in question is using iwjobc and/or iwinvokejob - try changing it to use iwwft_compile.ipl (run perldoc on the script for detailed information about the usage) - and see if that resolves the problem.

ISCBorisB

Actually, I believe that iwwft_compile.ipl was created, in part, to get around the need to be a "master" to instantiate a WFT. iwjobc / iwinvoke job does require "master" privileges.

So if the code in question is using iwjobc and/or iwinvokejob - try changing it to use iwwft_compile.ipl (run perldoc on the script for detailed information about the usage) - and see if that resolves the problem.

Whatever the original intention was, iwwft_compile.ipl with -i flag calls iwjobc on your behalf
(through TeamSite::WFsystem CreateWorkflow Method). And as far as I can tell, neither iwwft_compile
nor TeamSite::WFsystem tries to (re)set effective uid/gid.

Adam Stoller

Whatever the original intention was, iwwft_compile.ipl with -i flag calls iwjobc on your behalf
(through TeamSite::WFsystem CreateWorkflow Method). And as far as I can tell, neither iwwft_compile
nor TeamSite::WFsystem tries to (re)set effective uid/gid.

I cannot state categorically that it works (it's been a while since I've personally tried using it for non-master invocation of workflows), I do seem to recall that it did work, and the project I'm currently working on is using it through various scripts that get called through FormAPI callserver processes - which perhaps are running as "master" but not "intentionally" so.

The other [obvious?] intention of iwwft_compile.ipl was to allow setting instantiation variables for WFTs - in place of my very ancient iwjobcc script - which attempted to do the same, in a far less elegant manner, before the introduction of iwwft_compile.ipl.

Regardless - I suggest that tirrudev try using it and report back whether it does / does not resolve the specific issue that was being seen.

condition.png

Adam Stoller

Okay - it turns out that this is the site where I'm working, and just a little while ago I performed some tests and verified that I was wrong (I admit it) - Using iwwft_compile.ipl does not remove the requirement of being a master user.

Side note: On Windows - running

iwwft_compile.ipl -i < params.xml

in a command prompt does not seem to work at all, but writing a little perl script that does the same, does work - at least as far as being able to have iwwft_compile.ipl read the parameters file. Running the command directly in the command prompt gives you a parsing error making it look like there's something wrong with the XML in the parameters file.

For those looking for context - the issue here is somewhat convoluted:

This should allow the initial save to be done without an error, the workflow to be instantiated, and the language-specific DCRs to be owned by the actual user.I'm not saying it's trivial - but I think it just might work....