http://www.perlmonks.org?node_id=1071813


in reply to How to Configure parsable path on Windows2008R2 IIS7

First, clarify your question for us!

I suspect the reference to cgi is gratuitous; that you're merely trying to cascade commands (in the local OS) on a single machine rather than to work thru Apache or some other server ap that uses CGI.

If I'm wrong, please correct me as part of your clarification. You'd also make this easier to understand with a simple ASCII flow-chart or a narrative that makes it clear what you mean by...

"I have added C:\Inetpub\wwwroot\perlscripts to my PATH System variables ... how to I configure Perl now to see that ?"

Simply put, you don't configure your Perl64 "to see that" -- AFAIK, you can't, except inside your scripts (on a per script, per execution basis). In any case, Perl doesn't care much, unless you are calling an executable from other than your current working directory,in which case, the smart way to do it is to code the executable's full path into the script calling the executable.

And, of course, if you're talking about setting some environmental variables that are needed by the (hypothesized) executable (or cascaded script), you have a whole different can of worms.

So -- please, help us to help you. Clear up the mysteries.

Come, let us reason together: Spirit of the Monastery

Replies are listed 'Best First'.
Re^2: How to Configure parsable path on Windows2008R2 IIS7
by jaaronanderson (Initiate) on Jan 24, 2014 at 14:56 UTC
    thanks for the response. sorry I was not clear.

    • CGI Im expecting is perhaps required or leveraging what Ive learned with ISAPI on the aforementioned IIS Windows platform.


    • My GOAL is to send an https string from a remote server on the same network to this IIS Server which I want to run a perl process against that string.


    • I am trying to set up Perl on IIS7. I have added my Mapping Handler and tried creating *.pl to the path C:\Perl64\bin %s %s and tried both with and without ISAPI support. I do not know what I am missing.


    • I also made sure the Read, script & execute permissions are set within the enabled Handler Mapping for *.pl


    • as far as >>"I have added C:\Inetpub\wwwroot\perlscripts to my PATH System variables ... how to I configure Perl now to see that ?"
      I have no idea what you mean about "provide an ascii flowchart" to further describe that i made sure I had set the Windows Server Environmental Variable PATH.


Re^2: How to Configure parsable path on Windows2008R2 IIS7
by jaaronanderson (Initiate) on Jan 28, 2014 at 15:37 UTC

    ok so I figured out v5.18 does NOT have supporting dependencies

    ref. https://twitter.com/bacongobbler/status/427865300587929600 ...

    but appears 5.14 does until I got stuck on <nmake>. See below:

    It would appear that you add perl to PATH environment variables ( I set mine to c:\Perl64\bin; )

    add a File Mapping in IIS7 for Perl file ext create .pl mapping for Perl C:\Perl64\bin\perl514.dll

    ( /!\ Note no %s %s cause Im using ISAPI : Yes )

    In order to prepare to cleanly install SOAP::Lite I focused on Perl/ActiveState child DEPENDENCIES

    I ran in CLI :: ppm install IO-SessionData

    twice then CLI returns “No missing packages to install”

    next

    I ran in CLI :: ppm install Class-Inspector

    It noted to me I FIRST must install Class::SSLeay

    so

    I ran in CLI :: ppm install Crypt::SSLEAY

    twice then CLI returns “No missing packages to install”

    then REBOOT seemed to fix a legacy wrong version of ExtUtils installed here...

    reran in CLI :: ppm install Class-Inspector

    reran to confirm prompt now “No missing packages to install”

    next

    I ran in CLI :: ppm install ExtUtils-MakeMaker

    twice then CLI returns “No missing packages to install”

    then

    moving onto installing SOAP::Lite

    cd to C:\InstallSOAPDirpkgDownload\

    perl MakeFile.PL (FINALLY ran fine)
    BUT

    when I goto nmake following this link http://soaplite.com/install.html

    nmake brings me back an error

    syntax error at -e line 1, near "'755')
    please help