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

Alternate directories for CGI...can this be done?

johnrc

I found these solutions in Devnet but has anything changed since these were posted? I use ContentCenter Professional 6.1.0 Service Pack 1. Is there a way to place CGI scipts in directories other than: iw-home/httpd/iw-bin ? Even a subdir of iw-home/httpd/iw-bin would work for me. Thanks.

cgi script location:
http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=DOWNLOADS_WORKFLOWS&Number=26397&page=&view=&sb=&o=&vc=1#Post26397

Executing CGIs Located in a TeamSite Workarea Requires Configuration of the CWS (Apache):
http://devnet.interwoven.com/site.fcgi/techlib/001243

Find more posts tagged with

Comments

Migrateduser

From my experience it seems like you at least have to have a "wrapper" in IWHOME/httpd/iw-bin - it can either call the Perl script from the right location, or it may create a hidden form and post to the real script. You can write a generic wrapper and pass URL parameters indiciating what real script you want to invoke, or write one stub for each real CGI you want to invoke. Passing URL parameters can be tricky in some contexts.

It seems like there must be a better way.

johnrc

Thanks john. That is something to try.

We are creating new external scripts and CGI's almost daily, with each file having very different objectives. The non-CGI external scripts can be placed in specific project directories which is what we want. I'd really like to do the same with the CGI scipts, even if it is just one additional directory to separate our own scripts from the ones that came with TeamSite.

JonathonG

At my client, the TeamSite server is shared by several distinct development groups. Each group's CGI files are stored in a separate sub-dir of iw-home/httpd/iw-bin. This seems to work fine, without any kind of wrapper necessary.

Jonathon
Independent Interwoven Contractor

Migrateduser

This works for custom menu items, DCT callouts and all other CGI types? Funny, I remember this being a problem for one customer in 5.5.2, but I don't remember the exact context. Do you have to put iw_cgi_wrapper.cgi in the URLs that invoke these CGIs? What version of TeamSite are you using?

JonathonG

We're using TS 5.5.2 on Windows.

I'm not sure about custom menu items. That may actually be an issue. I too recall seeing issues with doing this, but don't remember the exact case. Maybe its the CMIs. Since the server is shared, the group that maintains that global-level stuff is reluctant to add client-specific menu items.

But I know it works for CGI-callouts on DCTs, callServers from FormAPI, and even directly URL access to the CGI.

Jonathon
Interwoven Developer
Allstate, Inc.

nipper

One problem I noticed with this & can be shown with the sample CGI, is that
not all env variables were available if you we running in a sub dir.

So compare showenv.cgi from iw-bin and from iw-bin/sub/sub/sib/dir & see
what I mean.

Andy

jbonifaci

I don't see any differences when comparing the output of show_env.cgi when run in iw-bin or from within a subdirectory.

I'm at the same client as Jonathon and we have not run into any issues with using subdirectories here. Although, I do recall having some issue with it at other clients. Maybe it was related to custom menu items, which the client does not allow here.

JonathonG

Do you mean in a custom menu item context or in a DCT callout context? Like I said above, I haven't tested with custom menu items, but all of the env vars I've needed were passed in the DCT callout context.

Jonathon
Interwoven Developer
Allstate, Inc.

nipper

>I don't see any differences when comparing the output of show_env.cgi when run in iw-bin or from within a subdirectory.

May be fixed now (SP4) but when I started this project on 552 there was some data I could not get from showenv.cgi
when it was in the sub dirs (iw-bin/bus_unit/project) that I needed.

Of course I did my test again & it worked fine. Should not drink so many **** Mary's before work......

Andy

johnrc

Thanks. We are currently not concerned with CGI scripts relating to web page updating templates.

We are using TeamSite Workflow and passing vars between Workflow task objects and CGI's. A brief test of creating a subdir for Worflow CGI scripts did not work. I edited the httpd.conf file for that one. Has anyone done this with TeamSite Workflow?

JonathonG

I assume you mean for cgitasks?

I just tried this on a 6.1 system, and it worked fine. Here's my (somewhat sanitized for posting) cgitask definition:


<cgitask name="Test_Task"
         owner='OWNERID'
         description="test description"
         immediate="t">

       <areavpath v='__INSERT__("$area_vpath");'/>

       <successors>
               <successorset description="Email Reviewer">
                       <succ v="End"/>
               </successorset>
       </successors>

       <command v='/iw-bin/SUBDIR/CGINAME.cgi'/> 
</cgitask>

Jonathon
Interwoven Developer
Allstate, Inc.

johnrc

Yes, cgitasks.

Thanks JonathonG! That worked. There was no apparent difference in the show_env.cgi when placed in either dir so that was nice to discover.

JonathonG

Out of curiosity (because I remember at some point having problems with CGIs in sub-dirs), what were you trying before that wasn't working? And what kind of an error were you getting?

Jonathon
Interwoven Developer
Allstate, Inc.

Migrateduser

As far as I remember, only CMI CGI's need to be/have wrappers in IWHOME/httpd/iw-bin - everything else can be wherever.

johnrc

What happened before this was corrected was possibly a wrapper error which I haven't seen in weeks. Instead of this reference to the file:

<command v='/iw-bin/SUBDIR/CGINAME.cgi'/>

I think I used something like this which didn't work:

<command v='SUBDIR/CGINAME.cgi'/>

I'm sure it was that code line though.

JonathonG

Ok, that's ringing a bell. I think this is the exact issue I ran into. What's a bit misleading is that if you place your cgi directly in iw-bin, then you can code your command as:

<command v='CGINAME.cgi'/>

And it works fine. So, the obvious step when you create a sub-dir is just to add that sub-dir as you show in your second example. But that results in a wrapper error, which, IIRC, has some wording like "broken pipe" in it.

Anyway, glad to hear its working for you now, and thanks for satisfying my curiosity.

Jonathon
Interwoven Developer
Allstate, Inc.

johnrc

Just realized that done_page and full_redirect vars were not the same in subdirs, so the first one (only used that) had to be handled to work in each level. The show_env CGI showed that.