Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Open Deploy in cgitask
sparc_69
Hi folks,
I am running Teamsite 5.5.2 with OpenDeploy 5.5.1.
I am experiencing a problem with Opendeploy in a workflow.
My script is generating a filelist and calling iwodstart at the end.
When running as an externaltask, iwodstart works fine.
Since I have to allow the end user some extra fileselection before the list is being written to disk, I have implemented a cgitask with a form where my customer can check or uncheck files.
Anyway, there are two deployments which have to be triggered (due to a special infrastructure on the live server).
The first one will deploy, the second one won't.
I think the clue may be, that iwui is the owner of the Deployment (since it is running as cgi).
Is there a way of telling Opendeploy, that the workflowowner is th owner of the deployment.
Find more posts tagged with
Comments
Adam Stoller
I believe that if you specify the cgitask command as:
<command v="iwcgi_wrapper.cgi/yourcgi.cgi"/>
That impersonation will kick in and it will effectively 'su' to the logged in TeamSite user to exec yourcgi.cgi
If that doesn't solve your problem - you'll have to post (as an attachment) a tar file consisting of:
1) the deployment configuration file
2) the cgitask script
3) the wft
4) the od.log
5) The src.* and rcv.* logs associated with the deployment(s) in question.
--fish
(Interwoven Senior Technical Consultant)
james1
If your CGI outputs an HTML form that POST's back to the same CGI, make sure that the subsequent hits are going through the iw_cgi_wrapper.cgi, which will provide you with user impersonation, so that the CGI process runs as the end user.
See the TechNote "A Sample CGI Task" for more information:
http://devnet.interwoven.com/site.fcgi/techlib/49747
Hope this helps.
-- James
--
James H Koh
Interwoven Engineering
sparc_69
I think I have it running now.
The whole thing appears to be a timing problem.
Closing the window on submit of the selected files caused the CGI process to abort.
The deployment runs fine when I leave the window open.
Thanks a lot.
Regards
Juergen