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

First line in Perl code

jiten

Hi,

All our Perl code in TeamSite, we need to inlcude

 
#!c:\Interwoven\TeamSite/iw-perl/bin/iwperl

Here the iw-home path is hardcoded. So is there any way we can get the iw-home path in this.

Regards
Jitendra

Find more posts tagged with

Comments

jbonifaci

I'm fairly certain you must include the full path in the shebang and there is no way to use any kind of variable in it. So you're pretty much stuck with hard coding the path to iw-perl there.

My next question is what environment are you using? In Windows, you only need to include the shebang line in perl cgi scripts.

~Jeff

Adam Stoller

There are some very convoluted ways to (try to?) dynamically incorporate the path to IWHOME in your scripts - but usually that's only needed if poor planning was done with respect to installation on multiple servers (e.g. DEV, TEST, PROD servers with different IWHOME paths -- bad)

On Windows - if the PATH environment is set correctly and the file associations are set correctly I believe you can actually just use:

 #!iwperl

without the path, though I do believe that for CGI scripts you want the full path if you want to be able to call the .ipl script directly - otherwise you can copy show_env.cgi (a binary wrapper for show_env.ipl) to your_script_name.cgi (to act as a binary wrapper for your CGI .ipl script)

m_rajani

In Windows environ, you need not add the first line. Just invoke the script with %IWHOME%iw-perl inperl < SCRIPT> IWHOME should point to Teamsite home directory.

baskar

Hi..
u can try this and reply...

#!__IW_HOME__/iw-perl/bin/iwperl

Adam Stoller

Hi..
u can try this and reply...

#!__IW_HOME__/iw-perl/bin/iwperl

Do you have any idea on what you are suggesting / asking?

On Windows:

#!__IW_HOME__/iw-perl/bin/iwperl
#!/usr/iw-home/iw-perl/bin/iwperl
#!d:/iw-home/iw-perl/bin/iwperl
#!d:\iw-home\iw-perl\bin\iwperl

will all work if you are running the script from the command line and have the scripts' extension configured correctly to be associated with iwperl (TeamSite does this during installation) or if you explicitly run the script by saying:

iwperl scriptname
(if iwperl is on you PATH or in the current working directory)
d:\iw-home\iw-perl\bin\iwperl scriptname

Where the path in the #! line matters on Windows is with respect to CGI programs run through the web server (and I don't recall if it's Apache / iwwebd or the customer web server [normally] IIS) - but there have been cases where if you did not specify the correct path in the

line that the script would not run and you'd get strange errors in the web server logs.

Going back to the suggestion made

__IW_HOME__

- the reason you've probably seen that is that IWOV ships perl scripts with that in the #! line and uses another perl script (IWHOME/install/iwperlmunge.ipl) to find and change all occurrences of "

__IW_HOME___

" to the actual path of the TeamSite installation directory. It is not a "magic" variable or environment string.

wild123

There are some very convoluted ways to (try to?) dynamically incorporate the path to IWHOME in your scripts - but usually that's only needed if poor planning was done with respect to installation on multiple servers (e.g. DEV, TEST, PROD servers with different IWHOME paths -- bad)

On Windows - if the PATH environment is set correctly and the file associations are set correctly I believe you can actually just use:
 #!iwperl
without the path, though I do believe that for CGI scripts you want the full path if you want to be able to call the .ipl script directly - otherwise you can copy show_env.cgi (a binary wrapper for show_env.ipl) to your_script_name.cgi (to act as a binary wrapper for your CGI .ipl script)

I am on TS 6.7.2 (windows 2003) . The she bang line

 #!iwperl

works for some ipls and cgi's but not for 1 particular cgi file. What can be the reason? I am connecting to DB from my DCT inline call to fetch some values for a dropdown on my dct. The above shebang line works for this ipl. I have a formsAPI call to a CGI through call server to load another drop down in the dct . this time the she bang line in the cgi script doesnt seem to be working while it works for yet another CGI script performing something similar. WHat can be the reason?

Adam Stoller

I am on TS 6.7.2 (windows 2003) . The she bang line
 #!iwperl
works for some ipls and cgi's but not for 1 particular cgi file. What can be the reason? I am connecting to DB from my DCT inline call to fetch some values for a dropdown on my dct. The above shebang line works for this ipl. I have a formsAPI call to a CGI through call server to load another drop down in the dct . this time the she bang line in the cgi script doesnt seem to be working while it works for yet another CGI script performing something similar. WHat can be the reason?

There are any number of reasons why you might be seeing different behavior from scripts invoked through different means - and, on Windows, if you have script names that are not unique within the first 8 characters of the file name, you are at the mercy of Microsofts' 8.3 naming semantics (this is particularly true if you try to create CGI binary wrappers for IPL scripts).
If just using #!iwperl doesn't work - try putting the full path to iwperl on the sh-bang line - if that doesn't work, there's probably some other problem that needs to be resolved.

nipper

Also, change it from iwperl to iwperl.exe

Every few months someone creates an empty iwperl file that is taken over the iwperl.exe by DOS. Note, this would only be the problem if the ones that work have iwperl.exe and the ones that break are iwperl.