iwjobc not working for Editor Role in TS721

we were using iwjobc command to invoke workflow from perl script in TS 6.5. It was working fine for all roles.

But since when we upgraded to TS 7.21 it is observed that iwjobc command can be executed when you login as Master and not for Editor.

Is there any change on permissions to execute this command? How to allow Editors to invoke the workflow using iwjobc? or Suggest any alternative solution

Appreciate your suggestions.

Find more posts tagged with

Comments

Adam Stoller

we were using iwjobc command to invoke workflow from perl script in TS 6.5. It was working fine for all roles.

But since when we upgraded to TS 7.21 it is observed that iwjobc command can be executed when you login as Master and not for Editor.

Is there any change on permissions to execute this command? How to allow Editors to invoke the workflow using iwjobc? or Suggest any alternative solution

Appreciate your suggestions.

iwjobc takes a job specification file, and I believe has always required Master privileges for invoking the job - however, iwwft_compile.ipl processes a WFT (you feed it parameters via XML input) and should not require Master privileges.

Neither works with WFMs - for that there's iwmodelc - but that CLT is sorely lacking in functionality, such that there is no good (IMO) mechanism for instantiating WFMs from either the command line or via CSSDK (which also requires job specifications)

jayantb

Thanks Ghoti.

But the strange thing is that iwjobc command working fine in the perl script called from a link in TeamSite but not working when the same is getting executed from the script as a part of workflow.

This behaviour is for one user having editor access only. Is there anything difference if it gets executed from workflow?

Adam Stoller

Thanks Ghoti.

But the strange thing is that iwjobc command working fine in the perl script called from a link in TeamSite but not working when the same is getting executed from the script as a part of workflow.

This behaviour is for one user having editor access only. Is there anything difference if it gets executed from workflow?

The owner of the process could be different. The link in the TeamSite UI, I have to assume is a custom menu item. As a custom menu item, it is most likely being run as a CGI script - and if it is not being run with iw_cgi_wrapper.cgi - it means that it runs as the owner of the TeamSite server process - a.k.a. "root", "iwts", "Administrator", or "SYSTEM" - and as such - has Master privileges.

Conversely, if you are running the script from a workflow, presumably as an External Task (rather than CGI task) - then the script is being run by the owner of the task, not the owner of the TeamSite server process - and hence, it's a matter of the user's role

jayantb

Thanks for the explanation.

If I change the task owner which calles the workflow invoke script as a Master will it work?
I tried it once but didn't work for me.

jayantb

I set the task owner as master and workflow is getting executed properly.

Adam Stoller

I set the task owner as master and workflow is getting executed properly.

Right - but is the job that's getting invoked owned by the person you want it to be owned by (the specific user rather than the Master user)?

Since it's a job specification file that's being processed - it probably should be fine as long as the job spec has the desired user listed as Owner and Creator of the job.