nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IWDatacapture.callServer and .ipl ENV variables??

Tim__D

I'm using a callout to get nodes from a DCR and display them in a dropdown list. Using formAPI I then register the onchange event and attempt to use IWDatacapture.callServer to call another .ipl script and popuate another field using formAPI. The problem I'm having is that when I call the .ipl file I cant seem to get any environment variables. For example:

my $wa = $ENV{"IW_WORKAREA"}; returns blank?

Any ideas on a quick and easy way to get these variables into my script?

Edited by Tim__D on 08/26/04 08:04 AM (server time).

Find more posts tagged with

Comments

Dwayne

The environment variables that you're describing are only set for an <inline> callout. They aren't available to a piece of CGI code. My guess is that you're going to have to pass any data that you may need like that as a part of the URL. So instead of http://myserver/iw-bin/myhandler.ipl, you might use something like http://myserver/iw-bin/myhandler.ipl?iw_workarea=/default/main/WORKAREA/test&iw_role=editor&...whatever else ...

--

Current project: TS 5.5.2/6.1 W2K

Tim__D

It must work in multiple branches and workareas? There must be a way?

Tim__D

Perhaps there is a .pm that I can use that would make this information available?

Dwayne

Perl modules (.pm files) aren't magic. They can't manufacture information that doesn't exist. You can get things like the location of iw-home, because they're global. The current workarea is not global, so the information has to come from the user (or their web browser, more likely) in some way

When you invoke callServer, you're asking the web server to run a CGI on your behalf. That CGI knows only what you tell it. So you need to read that information from the user's session somehow. I remember there being a thread not too long ago about getting the workarea via FormAPI. Search the archives and see what you can find. If you can get the workarea in JavaScript, then you can populate the data object that you pass to callServer with the information, and your CGI code can parse it.

--

Current project: TS 5.5.2/6.1 W2K

Tim__D

Thanks. When using IWDatacapture.callServer I have always used .ipl files should these indeed be .cgi files? If so whats the difference?

Michael

For example

function getCategoryAndType()
{
// Returns the category and type of the DCR
return( top.gTDT );
}

function getWorkarea()
{
// Returns the path down to the workarea
return( top._dcWin.gWorkarea );
}

function callingServerForSomething()
{
var params = new Object();
params.workareaPath = getWorkarea();
params.categoryAndType = getCategoryAndType();
params.dcrName = IWDCRInfo.getDCRName();

IWDatacapture.callServer ("/iw-bin/yaddah/foo.ipl",params);

}

Note that getCategoryAndType() and getWorkarea() aren't supported formAPI calls....use at own risk. Although I believe they work on 5.5.2 and 6.x

Hope that helps.

Cheers
Michael

Dwayne

The extension that you use isn't particularly important. What's important is that the web server knows what do DO with the URL. If your web server is configured to run .ipl files as a CGI program, then that's fine. If your web server needs to have the extension be .cgi in order for that to happen, then use .cgi (provided the web server knows to run that .cgi via the iwperl interpreter, if needed)

CGI isn't a file type. CGI is a specification for dynamic html generation. It's common (but not required) that programs intended to be run as CGI programs have the CGI extension, at least on Unix. Under Windows, it should really have the .ipl extension, because that's the only way Windows knows to run it with the Perl interpreter. Unix is smart enough to parse enough of the file to see that it should be run via the perl interpreter, regardless of the extension.

--

Current project: TS 5.5.2/6.1 W2K

bturns

this how I grab the values in TS 5.5.2. using the following .js

var dcFrame = top._dcWin;
var datacaptureForm = dcFrame.frames["formframe"].document.dcreditForm;
var vpath = datacaptureForm.area_path.value;
params.vpath = vpath;

IWDatacapture.callServer("http://"+server+"/iw-bin/validateImage.ipl", params, false);

then in the cgi you can grab the values using the following code:

my $cgi = TeamSite::CGI_lite->new();
$cgi->parse_data();

my $areaValue = $cgi->{form}{'vpath'};

lemme know if you have any more questions.

Edited by bturns on 08/27/04 03:22 PM (server time).