3 Catalyst::Manual::Deployment::IIS::FastCGI - Deploying Catalyst with Microsoft IIS
7 It is possible to run Catalyst under IIS with FastCGI, but only on IIS
8 6.0 (Microsoft Windows 2003), IIS 7.0 (Microsoft Windows 2008 and
9 Vista), and (hopefully) its successors.
11 FastCGI is sometimes said to be supported on IIS 5.1 (Windows XP), but
12 some features (specifically, wildcard mappings) are not supported. This
13 prevents Catalyst applications from running on the server.
15 Let us assume that our server has the following layout:
17 d:\WWW\WebApp\ path to our Catalyst application
18 d:\strawberry\perl\bin\perl.exe path to perl interpreter (with Catalyst installed)
19 c:\windows Windows directory
21 =head2 Setup IIS 6.0 (Windows 2003)
25 =item Install FastCGI extension for IIS 6.0
27 FastCGI is not a standard part of IIS 6 - you have to install it
28 separately. For more info and the download, go to
29 L<http://www.iis.net/extensions/FastCGI>. Choose the appropriate version
30 (32-bit/64-bit); installation is quite simple (in fact no questions, no
33 =item Create a new website
35 Open "Control Panel" > "Administrative Tools" > "Internet Information Services Manager".
36 Click "Action" > "New" > "Web Site". After you finish the installation wizard
37 you need to go to the new website's properties.
39 =item Set website properties
41 On the tab "Web site", set proper values for: Site Description, IP
42 Address, TCP Port, SSL Port, etc.
44 On the tab "Home Directory" set the following:
46 Local path: "d:\WWW\WebApp\root"
47 Local path permission flags: check only "Read" + "Log visits"
48 Execute permitions: "Scripts only"
50 Click "Configuration" button (still on Home Directory tab) then click "Insert"
51 the wildcard application mapping, and in the next dialog set:
53 Executable: "c:\windows\system32\inetsrv\fcgiext.dll"
54 Uncheck: "Verify that file exists"
56 Close all dialogs with "OK".
58 =item Edit fcgiext.ini
60 Put the following lines into c:\windows\system32\inetsrv\fcgiext.ini (on 64-bit
61 system c:\windows\syswow64\inetsrv\fcgiext.ini):
65 ;replace 8 with the identification number of the newly created website
66 ;it is not so easy to get this number:
67 ; - you can use utility "c:\inetpub\adminscripts\adsutil.vbs"
68 ; to list websites: "cscript adsutil.vbs ENUM /P /W3SVC"
69 ; to get site name: "cscript adsutil.vbs GET /W3SVC/<number>/ServerComment"
70 ; to get all details: "cscript adsutil.vbs GET /W3SVC/<number>"
71 ; - or look where are the logs located:
72 ; c:\WINDOWS\SYSTEM32\Logfiles\W3SVC7\whatever.log
73 ; means that the corresponding number is "7"
74 ;if you are running just one website using FastCGI you can use '*=CatalystApp'
77 ExePath=d:\strawberry\perl\bin\perl.exe
78 Arguments="d:\WWW\WebApp\script\webapp_fastcgi.pl -e"
80 ;by setting this you can instruct IIS to serve Catalyst static files
81 ;directly not via FastCGI (in case of any problems try 1)
84 ;do not be fooled by Microsoft doc talking about "IgnoreExistingDirectories"
85 ;that does not work and use "IgnoreDirectories" instead
90 =head2 Setup IIS 7.0 (Windows 2008 and Vista)
92 Microsoft IIS 7.0 has built-in support for FastCGI so you do not have to
97 =item Necessary steps during IIS7 installation
99 During IIS7 installation, after you have added role "Web Server (IIS)"
100 you need to check to install the role feature "CGI" (do not be nervous
101 that it is not FastCGI). If you already have IIS7 installed you can add
102 the "CGI" role feature through "Control panel" > "Programs and
105 =item Create a new website
107 Open "Control Panel" > "Administrative Tools" > "Internet Information Services
108 Manager" > "Add Web Site".
110 site name: "CatalystSite"
111 content directory: "d:\WWW\WebApp\root"
112 binding: set proper IP address, port etc.
114 =item Configure FastCGI
116 You can configure FastCGI extension using commandline utility
117 "c:\windows\system32\inetsrv\appcmd.exe"
121 =item Configuring section "fastCgi" (it is a global setting)
123 appcmd.exe set config -section:system.webServer/fastCgi /+"[fullPath='d:\strawberry\perl\bin\perl.exe',arguments='d:\www\WebApp\script\webapp_fastcgi.pl -e',maxInstances='4',idleTimeout='300',activityTimeout='30',requestTimeout='90',instanceMaxRequests='1000',protocol='NamedPipe',flushNamedPipe='False']" /commit:apphost
125 =item Configuring proper handler (it is a site related setting)
127 appcmd.exe set config "CatalystSite" -section:system.webServer/handlers /+"[name='CatalystFastCGI',path='*',verb='GET,HEAD,POST',modules='FastCgiModule',scriptProcessor='d:\strawberry\perl\bin\perl.exe|d:\www\WebApp\script\webapp_fastcgi.pl -e',resourceType='Unspecified',requireAccess='Script']" /commit:apphost
129 Note: before launching the commands above, do not forget to change the
130 site name and paths to values relevant for your server setup.
136 =head3 Setup of your application
138 Note that you B<MUST> have the config setting C<use_request_uri_for_path> set to true
139 to work in IIS7 - if you do not have this then all sub paths in your application
140 (e.g. /foo/bar) will resolve to the root path, i.e. /
144 Catalyst Contributors, see Catalyst.pm
148 This library is free software. You can redistribute it and/or modify it under
149 the same terms as Perl itself.