{= include("docs.util"); start_docs_page(docs.technical_manual.page_titles.newsletters); =}
![]() |
Sawmill Newsletter February 28, 2011 |
Start with IIS 7.0 installed and
running. You must have administrative privileges on the Windows
2008 server to perform the steps below.
1. Download and install the latest Sawmill 8 release on Windows
Download the latest Sawmill 8
production release, and install by double clicking the Sawmill
package. You'll be directed through the processes of installing
Sawmill using the Windows installer. Sawmill, by default, will
install in web server mode & will setup a Windows service that
runs Sawmill as a Service. Installing in web server mode is
necessary to unpack the Sawmill executable & supporting files.
As part of this process UN-CHECK the Sawmill 8
Windows Service When doing the install, and click Install.
From there you will get the option to Show Sawmill 8 now (by a web
browser URL). Un-check this box, and click FINISH.
Once the installer completes, you’ll have the core pieces to move
into place within the IIS 7.0 framework to use Sawmill as a CGI
process.
UN-CHECK the Sawmill 8 Windows
Service check box, and click Install:
Un-check the Show Sawmill 8
now (by a web browser URL) box, and click FINISH.
2. Move Sawmill 8 into the IIS 7
directory
From Windows Explorer, create the folder: C:\inetpub\cgi-bin\
Right click the C:\inetpub\cgi-bin
directory, select properties from the context menu and
then select the Security tab.
For each Group and user, change permissions to allow modify, read, write and execute permissions (Full control.)
Next, move the directory containing the Sawmill supporting files, the Sawmill binary into place.
Move
C:\Program Files\Sawmill 8\LogAnalysisInfo and
C:\Program Files\Sawmill
8\Sawmill.exe
C:\Program Files\Sawmill
8\libeay32.dll
C:\Program Files\Sawmill
8\ssleay32.dll
To:
C:\inetpub\cgi-bin\
Next, Highlight the LogAnalysisInfo
folder, right click and select properties from the
contextual menu. Click on the Security tab and change
permissions to modify, read, and write
permissions for all users and groups.
3. Integrate Sawmill into the IIS 7.0 framework
Open the Internet Information
Services (IIS) Manager by clicking on the Windows Start
Menu, Administrative Tools, Internet Information
Services (IIS) Manager. Expand the Server’s IIS
configuration by clicking on the + next to the name of your
server, and then expand the Web Sites folder from within the IIS
control panel. Highlight the website you want to add a cgi-bin
directory to.
Right click for the contextual menu, and select Add Virtual Directory.
The Virtual Directory Creation Wizard
window will appear. The wizard is used to add the cgi-bin
directory to the website. In the wizard, create a virtual
directory Alias cgi-bin and the physical path to the cgi-bin
folder on the server, in this case I’ll point to the web server
root directory, C:\inetpub\cgi-bin.
Once you create the virtual directory path to the cgi-bin folder in your web server root directory using the wizard, you’ll need to edit the permissions by right clicking the cgi-bin directory. The correct permissions will be read, execute, and write (Allow full control.) There maybe be a security warning when you select write permissions, and execute permissions, and you’ve completed adding the virtual directory.
Now we will need to add Sawmill.exe
as a web service in the IIS control panel. To do this you’ll click
on the Server Names (SAGE in this example) in the left
pane of the IIS server menu. In the right pane double click ISAPI
and CGI Restrictions.
Next, click on the Add
button, and browse to the location of the C:\inetpub\cgi-bin\Sawmill.exe,
(you will need to change the file types pull down to
display all files) and open Sawmill.exe, and click
OK to add the file. On the same window you’ll see an option
for Allow extension path to execute, check the box next to
the option to enable the web service extension, and click on OK.
After you click Add, you will see the
dialog box below.
When you click the browse (...) icon
you'll get the dialog box below. You will need to set the file
times as shown below to get Sawmill.exe to show.
Once you Select the Sawmill.exe
executable, optionally add a description of the web service you
are adding, and check the box next to Allow extension path to
execute.
You’ve now added Sawmill.exe as a web
services extension for your site, and you’ll see the web service
in the list of ISAPI and CGI Restrictions with a status of Allowed.
Now go back to Server page, and click on the server name, then
double click on Handler Mappings.
Check if the CGI-exe handler is
enabled, if not enabled, select this setting by Edit Feature
Permissions for the handler.
In the Edit Feature Permissions
dialog box check Execute and click OK.
Now the Handler Mappings will show
the CGI-exe, enabled.
Now for the moment of truth. You now
should be able to access your CGI install directly via http://www.yourdomain.com/cgi-bin/Sawmill.exe.
If you see a "page not found error" that's bad news, and it’s
likely that the cgi-bin directory is not correctly linked to the
site URL. If you see something about not having permissions or
internal server error (error 500) then this is good news because
the browser is resolving your install, however, something still
needs to be fixed in terms of permissions (or DLLs) to get things
running. See the troubleshooting section below. If everything goes
as expected you will see the Welcome to Sawmill setup screen. From
here you’ll be guided through a quick set up of Sawmill, including
creating an administrative user. Once setup is complete you can
begin analyzing your logs by clicking on the Start here link.
Troubleshooting
There are instances where Windows
2008 and IIS 6.0 have increased security measures enabled. If this
is the case you will get a 403-permission denied error when trying
to access your Sawmill CGI install. If this occurs follow the
information in the Microsoft Knowledge base article below.
http://support.microsoft.com/kb/904056
If you continue to get 500 errors,
make sure you've copied the two DLLs from the Sawmill installation
to the cgi-bin folder. The Sawmill.exe binary may not be able to
run without those two DLLs in its folder.