Tal Galili has started up a SAS blog aggregator. The more folks involved in SAS, the better, as far as I am concerned.
You can find it at:
SAS-X
This blog is designed to show various ways to use SAS with Microsoft technologies. Hopefully, I can illustrate ways to make these 2 technologies work together and help users out with integration concerns.
Sunday, November 28, 2010
Sunday, November 07, 2010
Getting SAS/IntrNet Operational on IIS7
IIS7 is a major change in IIS. Don Henderson contacted me and asked if I could help get it working. It really isn't hard but involves a few steps.
How do you get SAS/IntrNet operational.
1. Enable CGI Role on Server through the Server Manager.
2. Add in your website in IIS. Right-click the scripts or cgi-bin directory where
the broker.exe is located and select Convert to Application.
3. While still having the scripts/cgi-bin folder selected, double-click on the handler mappings icon on the right-hand side. There should already be a listing for *.cgi at the top. Double-click on it --> Request restrictions --> Mapping --> Invoke --> File or Folder, Access --> Execute.
4. Click on the machine name in IIS. Click on ISAPI and CGI restrictions. Click on Add..., specify the full path to the broker.exe.
5. Optional: set up a host header.
Click on the Default website or on the website name. On the far right-hand side of the screen, click on bndings. Specify a host header (demos.savian.net, for example).
See here for more details:
http://www.wrensoft.com/zoom/support/faq_cgi_iis.html
Good luck and contact me if you have issues.
Alan
How do you get SAS/IntrNet operational.
1. Enable CGI Role on Server through the Server Manager.
2. Add in your website in IIS. Right-click the scripts or cgi-bin directory where
the broker.exe is located and select Convert to Application.
3. While still having the scripts/cgi-bin folder selected, double-click on the handler mappings icon on the right-hand side. There should already be a listing for *.cgi at the top. Double-click on it --> Request restrictions --> Mapping --> Invoke --> File or Folder, Access --> Execute.
4. Click on the machine name in IIS. Click on ISAPI and CGI restrictions. Click on Add..., specify the full path to the broker.exe.
5. Optional: set up a host header.
Click on the Default website or on the website name. On the far right-hand side of the screen, click on bndings. Specify a host header (demos.savian.net, for example).
See here for more details:
http://www.wrensoft.com/zoom/support/faq_cgi_iis.html
Good luck and contact me if you have issues.
Alan
Subscribe to:
Posts (Atom)