"#!`iwgethome`/iw-perl/bin/iwperl not working

Aghosh

Hi When ever i put the value "#!`iwgethome`/iw-perl/bin/iwperl
" instead of "#!/opt/Interwoven/TeamSite/iw-perl/bin/iwperl" in my ipl file , its not working properly , log file is not getting generated but when i put the value as ""#!/opt/Interwoven/TeamSite/iw-perl/bin/iwperl" all works fine.

Can any one help why it is not working? i have tried everything from my end ?

I am calling the ipl through a datacapture.cfg like this :

var urlserver = server+"/iw-bin/STcom/Test.ipl
IWDatacapture.callServer(urlserver,params,true);

Code:

#!`iwgethome`/iw-perl/bin/iwperl
#-----------------------------------------------------------------------------
# File sample_cgi_task.ipl
#
# Use A sample program for use with a CGI task. This can be used
# as a starting point for a new CGI task, or as an aid in debugging
# an existing CGI task.
#
# Copyright 2003-2005 Interwoven Inc.
# All rights reserved.
#-----------------------------------------------------------------------------

use strict;
use warnings;
use TeamSite::Config;
use TeamSite:CRnode;
use TeamSite:CRparser;
use Encode;
use XML:OM;
use CGI;
use HTML::Entities;


my $in = new CGI;

my $localeValue = $in->param('DCTPath');
open(FILE,">>/opt/Interwoven/TeamSite/httpd/iw-bin/custom/bac_enterprise/please.log");
print FILE "This is file $localeValue";
close(FILE);

print qq~

ISCBorisB

Unfortunately this can not be done. Script's Shebang is interpreted by your shell upon script's execution.
Shebang is used verbatim, without any evaluation. Thus, shebang is not portable.

There are several more or less workable tricks to circumvent this limitation and make your script (not shebang!)
setting portable regardless of the interpreter placement. They are just that though, tricks. They usually exploit
some factual or assumed user account settings, $PATH value, etc...

Tricks themselves may not be portable across different shells, may introduce a security breach, etc...