Executing owner IPL or CGI

Environment: Teamsite 6.7.2 no sp on windows XP Professional.

1. I Generate a page using iwgen from a callserver
2. For the generated page SYSTEM shows as Modified By instead of user who triggers call server.
3. I need to change that Modified By from SYSTEM to to the user who triggers callserver

To do this. I wrote a IPL file and used touch command to change Modified By attribute. Worked fine.

Then I went ahead and changed IPL which is used to generate page via call server and kept touch command in it. With this Modified By still shows asSYSTEM.

In TS 672 all IPls and CGIs execute under SYSTEM and when we try to run commands through those IPls or CGIs they also trying to take SYSTEM privelege from its parent, I mean its parent IPl or CGI.

Any pointers for the solution will be appreciated!

I need to modify Modified BY from SYSTEM to user who triggers call server from the ipl which is called from call server.

Thanks,
Sanjeev

Find more posts tagged with

Comments

Samir_Friend

not sure on this.... but can you try using a wrapper class to make a call to your IPL

iw_store

not sure on this.... but can you try using a wrapper class to make a call to your IPL

Could you please provide more details about it, may be with an example how to use it ?

Samir_Friend

Replace the URL path parameter for your IPL with below line where you invoke it:

"/iw-bin/iw_cgi_wrapper.cgi/sample.ipl"

Hope it works....

iw_store

Replace the URL path parameter for your IPL with below line where you invoke it:
"/iw-bin/iw_cgi_wrapper.cgi/sample.ipl"
Hope it works....

We have done something simillar, by having .htaccess file and keeping our CGIs and IPLs out of iw-bin folder, just under httpd. Not sure what exact difference they carry.

Samir_Friend

The idea is just to include a wrapper cgi before the ipl name in the URL path.

Need the experts to comment on the difference between keeping the IPL and CGI files out of iw-bin and inside it.

iw_store

Any other pointers will help me.

Thanks.

ISCBorisB

We have done something simillar...

Toilet paper and Sandpaper are also similar, they are both "papers" after all. Try it and you will see that there are certain
differences as well. Samir gave you a solid advise. Have you tried iw_cgi_wrapper? Not "something similar", the wrapper.
If you haven't, do that. If you have, what's the problem?

iw_store

Do I need to copy IPL or CGI under iw-bin folder to execute as iw_cgi_wrapper.cgi/filename.cgi or under a new folder within iw-bin ?

I have all my ipls or cgi under httpd/iw-tools/perlfiles/separatelook/

To execute ipls or cgi from that folder we have a .htaccess file which contains following code in it

Options +ExecCGI
Options +Indexes
IndexOptions FancyIndexing
AddHandler cgi-script .cgi .pl .ipl
#Do not modify this file, only deploy this file to any directory that is to serve up cgi's

For now what I did is, I copied iw_cgi_wrapper.cgi file to my CGIs folder (separatelook) and tried to execute but got error as,

TeamSite : Wrapper
Error: Error trying to open a pipe to E:\teamsite\iw-home\httpd\iw-bin\filename.cgi

I don't have any idea how the .htaccess file works.

Thanks,

ISCBorisB

Do NOT use a location with the "distributed configuration" (.htaccess) for this case. Do NOT copy iw_cgi_wrapper anywhere.
Keep it simple, make it work. If you have to, start tinkering with it AFTER the simple case is working. Here is the deal:

- Place your whatever.ipl (ipl, not cgi!) directly under /iw-home/httpd/iw-bin, that's where iw_cgi_wrapper expects it.

- Use the following syntax verbatim for the first callServer Parameter: "/iw-bin/iw_cgi_wrapper.cgi/whatever.ipl".
You do not need any server/port references before /iw-bin.

iw_store

When I keep my callserver code as,

IWDatacapture.callServer("/iw-bin/iw_cgi_wrapper.cgi/setEAToHtmlFiles.cgi",param);

Getting following error.

TeamSite : Wrapper
Error: Error trying to open a pipe to E:\teamsite\iw-home\httpd\iw-bin\filename.cgi (1).

But, when I keep as IWDatacapture.callServer("/iw-bin/setEAToHtmlFiles.cgi",param);

works fine without serving my purpose.

The code of my IPL is
[HTML]
#!e:/teamsite/iw-home/iw-perl/bin/iwperl
use CGI;
use strict;
$| = 1;
my $cgi = new CGI;
my $fileType = $cgi->param('fileType');
my $dcrHTML = $cgi->param('dcrHTML');
my $topNavigationFile = $cgi->param('topNavigationFile');
my $leftNavigationFile = $cgi->param('leftNavigationFile');
my $footerfile = $cgi->param('footerfile');
my $cssfile = $cgi->param('cssfile');
my $areaPath = $cgi->param('areaPath');
my $dcrFullPath = $cgi->param('dcrFullPath');
my $tpl = $cgi->param('pt');
my $dcrPath = $cgi->param('dcrPath');
my $nameDCR = $cgi->param('nameDCR');
my $formType = $cgi->param('formType');
print "Content-type: text/html\n\n";
my $topNAVExtAttrKey = "topNavigationFile";
my $leftNAVExtAttrKey = "leftNavigationFile";
my $footerExtAttrKey = "footerFile";
my $cssExtAttrKey = "cssFile";
if ($dcrHTML =~ /^\/(.*)/) {
$dcrHTML = $dcrHTML;
} else {
$dcrHTML = "/".$dcrHTML;
}
if ($dcrHTML =~ /(.*).html$/) {
$dcrHTML = $dcrHTML;
} else {
$dcrHTML = $dcrHTML.".html";
}
my $outPutFile = $areaPath.$dcrHTML;
$outPutFile = "Y:".$outPutFile;
open FILEHANDLE,">$outPutFile";
close FILEHANDLE;
if($topNavigationFile !~ /^\//) {
$topNavigationFile = "/".$topNavigationFile;
}
if($leftNavigationFile !~ /^\//) {
$leftNavigationFile = "/".$leftNavigationFile;
}
if($footerfile !~ /^\//) {
$footerfile = "/".$footerfile;
}
if($cssfile !~ /^\//) {
$cssfile = "/".$cssfile;
}
$topNavigationFile =~ s/^\/docs//;
`e:/teamsite/iw-home/bin/iwextattr -s $topNAVExtAttrKey=$topNavigationFile $outPutFile`;
$leftNavigationFile =~ s/^\/docs//;
`e:/teamsite/iw-home/bin/iwextattr -s $leftNAVExtAttrKey=$leftNavigationFile $outPutFile`;
$footerfile =~ s/^\/docs//;
`e:/teamsite/iw-home/bin/iwextattr -s $footerExtAttrKey=$footerfile $outPutFile`;
$cssfile =~ s/^\/docs//;
`e:/teamsite/iw-home/bin/iwextattr -s $cssExtAttrKey=$cssfile $outPutFile`;
my $mytpl = $areaPath."/templatedata/".$formType."/presentation/".$tpl;
my $outputhtml = "$areaPath"."$dcrHTML";
my $cmd = "e:/teamsite/iw-home/bin/iwgen -t $mytpl -r $dcrPath $outputhtml";
`$cmd`;
[/HTML]

But the show_env.cgi works both way when I try from browser.

ISCBorisB

Have you bothered to read my previous post? No? Then let me try one last time

...Place your whatever.ipl (ipl, not cgi!) directly under ...
...syntax verbatim "/iw-bin/iw_cgi_wrapper.cgi/whatever.ipl"...

Good luck

iw_store

Have you bothered to read my previous post? No? Then let me try one last time
...Place your whatever.ipl (ipl, not cgi!) directly under ...
...syntax verbatim "/iw-bin/iw_cgi_wrapper.cgi/whatever.ipl"...
Good luck

Thank you very much for your help. I did do this. I think I am messing somewhere. The last option I have to play around show_env.cgi and try to have that in my call server with a different name.

Samir_Friend

Thank you very much for your help. I did do this. I think I am messing somewhere. The last option I have to play around show_env.cgi and try to have that in my call server with a different name.

The files iw_cgi_wrapper.cgi and your.ipl should both be together in the iw-bin(same) directory.

This should work perfectly as in a standard env.

If you've already implemented this, what was the error?

iw_store

Now I made it to work with following code,

IWDatacapture.callServer("/iw-bin/iw_cgi_wrapper.cgi/myPerlFile.ipl",param);

Now the generated files are coming with Modified By as by the name of the user who triggers the ipl.

Thank you to both of you.

I found below stuff in TS document.

[HTML]
What is this iw_cgi_wrapper.cgi?
This wrapper facilitates TeamSite impersonation. When a request is received of the form
/iw-bin/iw_cgi_wrapper.cgi/program, the wrapper program iw_cgi_wrapper.cgi is
executed. The wrapper looks at the request for a TeamSite session string that may be either
a request parameter named session or a cookie named session. The wrapper then
executes the wrapped program specified in the URL while impersonating the user indicated
by that session string and gives that program a request that includes the parameters from the
original request. The wrapper relays the response from the wrapped program back to the
client.
The net result of this impersonation is that the CGI program is run by the same user who
started the task (such as the process is owned by that user). If any files are created or
modified by the CGI program, the work appears to have been done by the user. Without
this impersonation, all CGI tasks would appear to be run by the owner of the Web server
process – iwui on UNIX, or SYSTEM on Windows.
[/HTML]

Is it possible to take my ipl (myPerlFile.ipl) to my origional place i.e under httpd/iw-tools/perlfiles/separatelook/myPerlFile.ipl ? with iw_cgi_wrapper.cgi. Or if I want to execute under the control of iw_cgi_wrapper.cgi do I need to have my ipl inside iw-bin directory ?

When I copy iw_cgi_wrapper.cgi to my folder and try to execute my ipl with http://servername/iw-tools/perlfiles/separatelook/iw_cgi_wrapper.cgi/myPerlFile.ipl, it tries to find myPerlFile.ipl inside iw-bin directory.

Adam Stoller

Is it possible to take my ipl (myPerlFile.ipl) to my origional place i.e under httpd/iw-tools/perlfiles/separatelook/myPerlFile.ipl ? with iw_cgi_wrapper.cgi. Or if I want to execute under the control of iw_cgi_wrapper.cgi do I need to have my ipl inside iw-bin directory ?

If you want to write your own binary wrapper - yes. If you want to use the OOTB iw_cgi_wrapper.cgi - no - the scripts need to be placed within IWHOME/httpd/iw-bin/ because that (as you've already found out) is where it looks for the scripts that it is going to run.

Putting the scripts in IWHOME/httpd/iw-bin/ is generally the way to go - just prefix the names of the scripts in a uniform manner so that you can easily find and/or recognize them as being custom.

iw_store

Thank you. This will help me. In my working company Teamsite has been established 10 years back :-). They have't kept any files inside iw-bin directory. Our Infra Team don't allow us to keep files inside iw-bin to maintain uniformity or maintaince perspective.

Even I don't have write access to iw-bin directory on dev TS. I used a CGI to copy files from my working directory to iw-bin to test this and removed them after my test.

Will spend some time to write my own binary wrapper or will try to convience our infra team.

Thanks again.

Adam Stoller

Thank you. This will help me. In my working company Teamsite has been established 10 years back :-). They have't kept any files inside iw-bin directory. Our Infra Team don't allow us to keep files inside iw-bin to maintain uniformity or maintaince perspective.

Even I don't have write access to iw-bin directory on dev TS. I used a CGI to copy files from my working directory to iw-bin to test this and removed them after my test.

Will spend some time to write my own binary wrapper or will try to convience our infra team.

Thanks again.

Let your Infra[structure] team know that placing custom CGI scripts within IWHOME/httpd/iw-bin is the supported practice for TeamSite - they can check with IWOV Support too.