This shows you the differences between two versions of the page.

Link to this comparison view

en:user_advanced:greenstone2_with_iis [2015/05/04 13:30] (current)
Line 1: Line 1:
 +====== Running greenstone2 using IIS ======
 +// Note: we don't use IIS, test Greenstone with it, or recommend it. Greenstone binaries come with Apache included. Apache has a much better security record, and of course it's open source. //
 +// Note: These notes are quite old (written for version 2.82), but included here just in case... //
 +After installing the web library version of Greenstone, configure IIS by following these steps:
 +  - Visit ''​http://​localhost''​ in a web browser to check that IIS is running
 +  - Run the IIS configuration program (Control Panel -> Administrative Tools -> Internet Information Services)
 +  - Double-click on the local computer, then Web Sites. Right-click on Default Web Site, choose New -> Virtual Directory. Set the Alias to "​gsdl"​ for 2.80/2.81 and earlier versions (and to "​greenstone"​ in or after 2.82), the Content Directory to the directory where you installed Greenstone (eg. C:\Program Files\Greenstone),​ and allow "​Read"​ and "​Browse"​ permissions only.
 +  - Open the new "​gsdl"​ entry, right-click on the "​cgi-bin"​ folder and choose Properties. Enter "​Greenstone"​ as the Application name and choose "​Scripts and Executables"​ for Execute Permissions. Untick "​Directory browsing"​.
 +  - IIS 6: Copy the gsdlsite.cfg file from the Greenstone "​cgi-bin"​ folder into the main Greenstone folder. If you have only gsdlsite.cfg.in there (may happen in 2.82), copy it to main folder and rename to gsdlsite.cfg. Edit it and modify the gsdlhome variable to be the location of your top level greenstone folder.
 +  - IIS 6: expand Local Computer, click "Web Service Extension",​ then right-click "All Unknown CGI Extensions"​ and choose Allow. (Thanks to Victor T. Jones, Jr.)
 +  - Close the IIS configuration program.
 +  - Make the Greenstone "​etc\error.txt",​ "​etc\key.db"​ (or key.gdb) and "​etc\users.db"​ (or users.gdb) files world-writeable by opening a DOS prompt (Start -> Run -> cmd.exe) then running: ​
 +  cacls "​C:​\Program Files\Greenstone\etc\error.txt"​ /P Everyone:F
 +  cacls "​C:​\Program Files\Greenstone\etc\key.db"​ /P Everyone:F
 +  cacls "​C:​\Program Files\Greenstone\etc\users.db"​ /P Everyone:F
 +</​code> ​
 +If error.txt not there, add an empty file called error.txt and change permissions as described.
 +You should now be able to access your Greenstone library at http://​localhost/​gsdl/​cgi-bin/​library.exe,​ or, for versions since 2.81, at http://​localhost/​gsdl/​cgi-bin/​library.cgi
 +  * Additional notes for 2.82, thanks to Diego Spano and Sridhara B
 +    *  Make sure in cgi-bin you have gsdlsite.cfg not gsdlsite.cfg.in. It may be better to rename the file in IIS:
 +  - Go to IIS
 +  - Default website
 +  - click on cgi-bin virtual directory.
 +  - In the right side cgi-bin files are found and rename gsdlsite.cfg.in to gsdlsite.cfg.
 +Then edit the values like the following: (this assumes installation into C:​\greenstone2)
 + ​gsdlhome ​   c:​\greenstone2
 + ​httpprefix ​ /gsdl
 + ​httpweb ​    /​gsdl/​web
 + ​gwcgi ​      /​gsdl/​cgi-bin/​library.cgi