Re: Moving to IIS

I haven't tried this on PWS as I only keep it on my laptop for use when
really bored in hotels, but this is what you need to do first, in IIS.

Configuring a Script Interpreter
IIS provides built-in JScript and VBScript interpreters. However, to run CGI
scripts written in another language, such as Perl, you must install and
configure a Win-32 compatible version of the script interpreter. To do so,
take the following steps:
 1. Obtain the script interpreter. The following Web sites provide Win32
implementations of Perl, TCL, Python, and REXX:
� Perl: http://www.activestate.com/
� TCL: http://www.scriptics.com/
� Python: http://www.python.org/windows/
� REXX: http://www2.hursley.ibm.com/orexx/

 Note    The ActiveState Tool Corporation provides three Perl interpreters
of interest to IIS developers: Perl for Win32 (Perl.exe), Perl for ISAPI
(PerlIS.dll), and PerlScript, an Active Scripting interpreter for PerlScript
code in ASP pages.
 2. Install the script interpreter. Extract the script interpreter archive
into a new directory on your hard drive, for example, c:\perl. Be sure
directory names are expanded from the archive. Follow the instructions
provided by the vendor to build the script interpreter from the source code
package and install the files. If the script interpreter package contains
files with long file names, when downloading from the Internet, be sure to
use a zip file handler that opens them correctly, such as WinZip or Info-Zip
Unzip.
 Note    Before running install.bat, you might want to change directory to
the DOS version of your directory if you gave it a long file name. This will
ensure that readable paths are listed in the registry.
 3. Set permissions. In Windows Explorer, set NTFS permissions on the
directory containing the script interpreter by giving Execute permissions to
the Everyone account. Next, set permissions on the directory containing the
actual scripts. For testing purposes, you can give Read access permissions
to the Everyone user account. Otherwise, you should set access permissions
to Script, and disable Read access permissions. In the Internet Services
Manager (ISM), set Script only permissions on the scripts virtual directory.
 4. Set application mappings. In the ISM, map the extension for the script
file(s) to the executable for the script interpreter. For example, you might
map the extension .py to Python.exe, the executable for the Python script
interpreter.
 Note   For the ActiveState Perl script interpreter, the extension .pl is
associated with PerlIS.dll by default. If you want to change the association
of .pl to perl.exe, you need to change the application mapping. In the
mapping, you must add two percent (%) characters to the end of the pathname
for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s.
 5. Set permissions on the script interpreter executable directory. In the
ISM, edit the application configuration for the home directory to recognize
the script interpreter executable.

You also need to make sure that the script returns the right headers -
something like
print "HTTP/1.0 200 OK\n";

as the first line.

Then check out these on support.Microsoft .com or wherever TechNet has moved
to today.
Q158732
Q186801
Q150629
Q226518



----- Original Message -----
From: Steve Bassler <bassmstr(at)westol.com>
To: HWG Servers <hwg-servers(at)hwg.org>
Sent: Sunday, January 30, 2000 10:06 PM
Subject: Re: Moving to IIS


> "Harold A. Driscoll" wrote:
> >
> > At 18:02 29-01-00 , Steve Bassler wrote:
> >>Putting aside how I feel about everything Micro$oft, I'm going
> >>to have to deal with this, and I think I need some help.
> >>
> >> Is it [PWS] similar enough to IIS to do this, or is it a
> >> different animal altogether?
> >
> > Yes. To both. It is a crippled IIS, and you'll be able to test most
> > of the features. It has most of the bloat, most of the administration
> > capability, and complexity, and some of the ways it (PWS v. IIS) is
> > crippled perhaps only Redmond could understand.
> >
> > Also, the Win 98 version is somewhat more limited than the NT version
> > of PWS... and of course Perl is similarly limited to what the toy O/S
> > wannabee is able to do.
>
> OK, I downloaded PWS last night and got it running.  There's some decent
> documentation included, so I know how to rewrite my SSI's now.  However,
> there's just a cursory mention of perl, and I really don't see any way
> to configure PWS to call perl.  When my page call a perl script, PWS
> tries to serve it up as a downloadable file rather than execute it.  Has
> anyone done this, or know how, or know where to point me?
>
> BTW, I don't expect there'll be a problem with the public Web site - the
> hosting service has all the bells and whistles installed on IIS, it's
> just setting up a local development platform that concerns me.
>
> The PWS docs are a bit confusing, like someone was charged with
> modifying the IIS doc to 1) convert all mention of IIS to PWS and 2)
> yank out everything that wasn't included in PWS, and then they quit
> halfway through the job.  Probably not an implausible scenario.  ;->
>
> Again, thanks,
> Steve
> ___________________________________________________________________
> Steve Bassler
> email: bassmstr(at)westol.com, WebServant(at)pdinet.org, Bassler(at)lolc.org
> Visit PDI Ministries at http://www.pdinet.org
>  Lord of Life Church at http://www.lolc.org
>  or my own home page at http://www.westol.com/~bassmstr
>
> There's a wideness in God's mercy I cannot find in my own,
> And He keeps His fire burning to melt this heart of stone,
> Keeps me aching with a yearning, keeps me glad to have been caught
> In the reckless raging fury that they call the love of God.
>                                      - Rich Mullins,  1955-1997
>

HWG: hwg-servers mailing list archives, maintained by Webmasters @ IWA