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)
Unable to call CGI though FormAPI
gsundeep
Hi ,
I incorporated FormAPI functionality into my Data Capture Template(DCT) .
When i am trying to call my CGI program as mentioned below, it seems to me that it is not called at all.
The CGI is passed a JavaScript object "parameters" .
IWDatacapture.callServer("/iw-bin/iw_cgi_wrapper.cgi/generateXML.cgi", parameters, true);
In above , the generateXML.cgi is not called.
Any help will be appreciated,
Thanks,
Sundeep
Find more posts tagged with
Comments
Jeremy
Hi,
Are you sure the CGI is called? Have a look at your iw-webd logs and see if it is recording anything in the errors.log file.
Otherwise maybe if you post the code?
HTH
Jeremy
Jens
Where have you put your CGI ?
If you call /iw-bin/MY_CGI.cgi the script should be in IWHOME/httpd/iw-bin/MY_CGI.cgi
deeps
did you give execute privilege to your cgi?
try chmod 755 xyz.cgi and running it.
disco
Your url path looks funny. Looks like it has two cgi scripts in it.
IWDatacapture.callServer("/iw-bin/iw_cgi_wrapper.cgi/generateXML.cgi", parameters, true);
Do you have a directory called "iw_cgi_wrapper.cgi" ? That may not be a good directory name.
Adam Stoller
iw_cgi_wrapper.cgi is a CGI program (binary), provided by Interwoven to allow that next [apparent] path argument '/****' to be run as-if it had been run by the logged-in-TS-user rather than being invoked as the user who own the TeamSite iwwebd process. As long as generateXML.cgi exists in IWHOME/httpd/iw-bin/ there shouldn't be any problem with respect to it *trying* to be run.
I'm not sure if it's needed in this context, but that's another issue.
Have you made sure that the generateXML.cgi script is at least syntactically correct (iwperl -w -c generateXML.cgi) ?
Have you looked at various logfiles to see if anything is getting logged that might help you resolve the problem?
Have you tried removing the iw_cgi_wrapper.cgi from the URI to see if that resolves the problem?
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
InnerTable alignment.ssd.zip
26949.docx
AKB
On Unix iw_cgi_wrapper works fine. On NT it throws me an error: TeamSite:wrapper wrapper error trying to open a pipe to c:\iw-home\httpd\bin\generatePage.cgi when I try to call iw-home\httpd\iw-bin\iw_cgi_wrapper.cgi\generatePage.cgi.
On Unix it works perfect. Wanted to know if anyone has used iw_cgi_wrapper.cgi on NT without any problems.
If I remove iw_cgi_wrapper.cgi on NT then the the page is generated but when we have the famous issue modified comes as SYSTEM...on the generated page....
Thanks
Adam Stoller
On NT it throws me an error: TeamSite:wrapper wrapper error trying to open a pipe to c:\iw-home\httpd\bin\generatePage.cgi when I try to call iw-home\httpd\iw-bin\iw_cgi_wrapper.cgi\generatePage.cgi.
I'll assume that the '\bin\' above is a typo on your part and that it was really '\iw-bin\' - yes?
Question: is generatePage.cgi a binary or a perl script?
If it's a Perl script - what does the first line of the file (the shebang line) look like?
If it's a Perl script - you *may* need to make it be a
.ipl
file and copy
show_env.cgi
to
generatePage.cgi
to provide a binary wrapper for the perl script (Windows - and especially IIS - have problems dealing with running Perl scripts where its expecting binaries)
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
AKB
yeah bin was a typo from my part. generatePage.cgi is a perl script and the first line is:
#!c:/iw-home/iw-perl/bin/iwperl
I did change it from cgi to ipl and looks like it is working. I will do some more testing.
I did nothing about copying show_env.cgi ...have u encountered issues where that needs to be done to overcome some issues ?
Adam Stoller
With the correct shebang line at the top - I believe just using the .ipl should work - the binary wrapper thing was mostly an IIS thing from pre-5.5.2 (probably pre-5.x) versions of TeamSite that used the "customer webserver" more extensively (TeamSite now uses iwwebd [apache] much more extensively and so avoids some of those bogosities).
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com