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; } } }

CGI task Workflow Modeler

System

I am trying to create a CGI script using perl. How do I convert my ipl into a .cgi file?

When I look in the TeamSite/http/iw-bin, I notice that all the other perl scripts have a corresponding .cgi file.

Find more posts tagged with

Comments

vpatel

You can call an ipl file directly from httpd/iw-bin through an URL. Just use the wrapper cgi.

Adam Stoller

You can call an ipl file directly from httpd/iw-bin through an URL. Just use the wrapper cgi.

You don't need a wrapper - you need to make sure the #! line is correct, and if on Unix you need to make sure the script is marked as executable.
In either case (OS-agnostic) you need to make sure the script is written as a CGI program.

You only need the iwcgi_wrapper.cgi is you want to try to ensure that the CGI script process is run by the logged in TS user as opposed to the TS server process owner -- which is moot if you are using non-OS users (but that's another story ;-)

Migrateduser

So i guess my question is:

1. Why does Interwoven have a matching .cgi file for every .ipl file?

For example. showEnv.ipl and showEnv.cgi. And the Workflow uses the script by calling the showEnv.cgi file.

2. How is the cgi file created?

It seems like the cgi file was generated from the .ipl file. Like .java gets compiled into .class.

I'm a java developer and this is my first perl/cgi script.

ISCBorisB

So i guess my question is:

1. Why does Interwoven have a matching .cgi file for every .ipl file?

For example. showEnv.ipl and showEnv.cgi. And the Workflow uses the script by calling the showEnv.cgi file.

2. How is the cgi file created?

It seems like the cgi file was generated from the .ipl file. Like .java gets compiled into .class.

I'm a java developer and this is my first perl/cgi script.

What you see is the obsolete (within TS anyway) way to make Windows script/interpreter association.

Check your cgi/ipl pairs, chances are you'll find out that all CGIs have the same size and timestamp.
For details look here. Re-read Ghoti's post carefully to see how you should be doing that today

Adam Stoller

To add a bit of historical information - prior to the introduction of iwwebd (apache) for managing the TS GUI - CGITasks and such were managed via the "customer web server" - and on Windows that tended to be IIS. IIS had a big problem dealing with running .ipl files as CGIs - and often, even if you named the script as .cgi it still had problems (although I believe this was due to most of the scripts being written with

#!iwperl

instead of the full path to iwperl, but I'm not sure). To get around this, Interwoven provided a single binary wrapper that everyone then just copied to the name of the .ipl files (changing the extension to .cgi) and everyone was "happy".

Since iwwebd was introduced, the usage of the "customer web server" got significantly reduced to just handling previews - and iwwebd (apache) is much better at handling .ipl files as CGIs.

However, Interwoven (now Autonomy Interwoven) never bothered to remove some of these archaic binary wrappers from the distribution - or they simply don't get removed during upgrades [?].