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)
CGI Callout and ASP
Annad
Hi,
I have a CGI Callout field in the DCT. I am trying to call an asp script when the user clicks on the cgi button. However, the asp program does not seem to execute. I am able to run the sample .ipl file through the callout.
Is there a reason as to why I can not do it? I believe this is an IIS configuration to enable asp scripts to run(???)
Thanks.
Anna
Find more posts tagged with
Comments
nipper
I have done this with a IPL wrapper, i.e. the callout runs a perl script which then kicks off the ASP. I have never tried to do the straight to ASP route/
Annad
Do you have the code for this.
I am interested in looking at it.
Thanks,
Anna.
nipper
I am certain there are a hundred ways to do it, but you can use this:
use IO:
ocket;
$socket = IO:
ocket::INET->new("localhost:81/foo.asp") or die $@;
You can also do something with LWP:
imple or URI::URL;
The socket is really basic (just connects to a process). LWP and URI will do GET and POST.
Annad
Thanks,
I will soon start working on this one.
-Anna-
Annad
Hi,
I tried your way of calling the ASP through the IPL script which worked ok. HOwever, I tried putting the asp script on the TeamSite server and on the cgi callout I am calling it directly.
The ASP script executes properly. When the user chooses a value on the page (generated by the asp script) I need to return the value to the DCR.
I know that in an IPL script, I can do this with the CGI interface. Is there a way to do this with simple javascript? I guess I have to make use of the DOM objects here ???
Thanks,
Anna
nipper
This is sounding like it should be a callserver from formapi rather than a CGI callout with the new requirement you just added.
However if you only want this to happen on DCT load and do not care if the load does not complete until the ASP is done, then it *should* work.
There should be a way to make the perl wait for data coming back on the socket you opened. It may be easier if you use LWP and were able to do GET/POST between the 2. Then have the perl output the XML needed for the DCT.
However, as you say more about what you are doing I certainly believe the callserver is the way to go. Use JS instead of ASP to get user input.
Good Luck
Andy