Starting Workflow from URL

Solaris, TS552

Hi,

We have a situation where a workflow is kicked off using the following command:

http://<interwoven-machine>/iw-bin/iwwft_instantiator.cgi?iw_user=iwadmin&iw_template_file=localisation.wft&iw_workarea=/default/main/Development/WORKAREA/myworkarea&iw_file=/templatedata/de_de-property/special_alert/data/rg_test7.dcr&childwft=localisation.wft

As you can see we are passing in the iw_user as iwadmin. However when we take this URL and try use it in a browser we get the following error:

Invalid workflow: ERROR:02422: No such TeamSite user

I have seen on other posts that this error message could be related to permissions of roles the user has. In this case iwadmin is a member of all roles, the iwwft_instantiator.cgi file has the correct permissions for the user to run it.
I was wondering if there was something we are missing? Does a session ID need to be passed? I think that the iwwft_instantiator.cgi script should generate a session ID if none is passed, but am not 100% sure.

While running the command in the browser we monitor some of the logs. In the iwui/error.log file we get the following error if it means anything to anyone?

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified

One other thing, when we set debug=1 and create the workflow xml file then run iwjobc and iwinvokejob on the xml file it works fine. My thinking is that this might be a permissions problem, but where?

If anyone knows where we are going wrong please let us know.

Thanks
Jeremy

Edited by Jeremy on 03/09/03 10:41 PM (server time).

Find more posts tagged with

Comments

Jeremy

Hi,

We managed to figure this out today! It seemed that iwjobc was eventually run as part of iwwft_instantiator.cgi - in a round about way. However, this command is not run as the user we were logged in as, but as iwui. We had checked to see if the user was a member of the master.uid file - it was. However, we are running with LDAP and did not realise that the user needed to be created in LDAP before it would work.
So the process now works!

Just thought I would post our solution in case anybody else came across something similar.

Jeremy