1Catalyst::Manual::DeploUysmeerntC:o:nItIrSi:bC:uaFttaeasdltyCPsGetIr:(l:3M)Daoncuuamle:n:tDaetpiloonyment::IIS::FastCGI(3)
2
6 Catalyst::Manual::Deployment::IIS::FastCGI - Deploying Catalyst with
7 Microsoft IIS
8
10 Probably the best way to deploy a Catalyst application on IIS is by
11 using IIS as a front end proxy. However if you positively must use
12 FastCGI (say due to internal IT policies) then this manual shows you
13 how.
14 It is possible to run Catalyst under IIS with FastCGI, but only on IIS
16 6.0 (Microsoft Windows 2003), IIS 7.0 (Microsoft Windows 2008 and
17 Vista), and (hopefully) its successors.
18 FastCGI is sometimes said to be supported on IIS 5.1 (Windows XP), but
20 some features (specifically, wildcard mappings) are not supported. This
21 prevents Catalyst applications from running on the server.
22 Let us assume that our server has the following layout:
24 d:\WWW\WebApp\ path to our Catalyst application
26 d:\strawberry\perl\bin\perl.exe path to perl interpreter (with Catalyst installed)
27 c:\windows Windows directory
28 Setup IIS 6.0 (Windows 2003)
30 Install FastCGI extension for IIS 6.0
31 FastCGI is not a standard part of IIS 6 - you have to install it
32 separately. For more info and the download, go to
33 Lhttps://www.iis.net/downloads/microsoft/fastcgi-for-iis>. Choose
34 the appropriate version (32-bit/64-bit); installation is quite
35 simple (in fact no questions, no options).
36 Create a new website
38 Open "Control Panel" > "Administrative Tools" > "Internet
39 Information Services Manager". Click "Action" > "New" > "Web
40 Site". After you finish the installation wizard you need to go to
41 the new website's properties.
42 Set website properties
44 On the tab "Web site", set proper values for: Site Description, IP
45 Address, TCP Port, SSL Port, etc.
46 On the tab "Home Directory" set the following:
48 Local path: "d:\WWW\WebApp\root"
50 Local path permission flags: check only "Read" + "Log visits"
51 Execute permitions: "Scripts only"
52 Click "Configuration" button (still on Home Directory tab) then
54 click "Insert" the wildcard application mapping, and in the next
55 dialog set:
56 Executable: "c:\windows\system32\inetsrv\fcgiext.dll"
58 Uncheck: "Verify that file exists"
59 Close all dialogs with "OK".
61 Edit fcgiext.ini
63 Put the following lines into
64 c:\windows\system32\inetsrv\fcgiext.ini (on 64-bit system
65 c:\windows\syswow64\inetsrv\fcgiext.ini):
66 [Types]
68 *:8=CatalystApp
69 ;replace 8 with the identification number of the newly created website
70 ;it is not so easy to get this number:
71 ; - you can use utility "c:\inetpub\adminscripts\adsutil.vbs"
72 ; to list websites: "cscript adsutil.vbs ENUM /P /W3SVC"
73 ; to get site name: "cscript adsutil.vbs GET /W3SVC/<number>/ServerComment"
74 ; to get all details: "cscript adsutil.vbs GET /W3SVC/<number>"
75 ; - or look where are the logs located:
76 ; c:\WINDOWS\SYSTEM32\Logfiles\W3SVC7\whatever.log
77 ; means that the corresponding number is "7"
78 ;if you are running just one website using FastCGI you can use '*=CatalystApp'
79 [CatalystApp]
81 ExePath=d:\strawberry\perl\bin\perl.exe
82 Arguments="d:\WWW\WebApp\script\webapp_fastcgi.pl -e"
83 ;by setting this you can instruct IIS to serve Catalyst static files
85 ;directly not via FastCGI (in case of any problems try 1)
86 IgnoreExistingFiles=0
87 ;do not be fooled by Microsoft doc talking about "IgnoreExistingDirectories"
89 ;that does not work and use "IgnoreDirectories" instead
90 IgnoreDirectories=1
91 Setup IIS 7.0 (Windows 2008 and Vista)
93 Microsoft IIS 7.0 has built-in support for FastCGI so you do not have
94 to install any addons.
95 Necessary steps during IIS7 installation
97 During IIS7 installation, after you have added role "Web Server
98 (IIS)" you need to check to install the role feature "CGI" (do not
99 be nervous that it is not FastCGI). If you already have IIS7
100 installed you can add the "CGI" role feature through "Control
101 panel" > "Programs and Features".
102 Create a new website
104 Open "Control Panel" > "Administrative Tools" > "Internet
105 Information Services Manager" > "Add Web Site".
106 site name: "CatalystSite"
108 content directory: "d:\WWW\WebApp\root"
109 binding: set proper IP address, port etc.
110 Configure FastCGI
112 You can configure FastCGI extension using commandline utility
113 "c:\windows\system32\inetsrv\appcmd.exe"
114 Configuring section "fastCgi" (it is a global setting)
116 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
117 Configuring proper handler (it is a site related setting)
119 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
120 Note: before launching the commands above, do not forget to
122 change the site name and paths to values relevant for your
123 server setup.
124 Setup of your application
126 Note that you MUST have the config setting "use_request_uri_for_path"
128 set to true to work in IIS7 - if you do not have this then all sub
129 paths in your application (e.g. /foo/bar) will resolve to the root
130 path, i.e. /
131
133 Catalyst Contributors, see Catalyst.pm
134
136 This library is free software. You can redistribute it and/or modify it
137 under the same terms as Perl itself.
138perl v5.34.0 C2a0t2a1l-y0s7t-:2:2Manual::Deployment::IIS::FastCGI(3)