Technical White Paper Web Server Configuration Internet Information Service (IIS) The following web server configuration instructions apply to UnitySync, Profiler, and Infocanon. While we use UnitySync as an example throughout the document, the configuration is very similar for all programs. It will be clear in the instructions where and how they differ. If you have any questions at all, please contact support@dirwiz.com for clarification and assistance. Table of Contents Web Server Configuration Internet Information Service (IIS)... 1 Internet Information Services (IIS) version 6... 2 IIS 6: Add Virtual Directory...2 IIS 6 Server: Configure Web Service Extensions...7 Allow All Unknown CGI Extensions...7 Configure Individual CGI Extensions... 7 Access Your Program Using IIS 6...8 Internet Information Services (IIS) version 7... 9 IIS 7 Server: Add Virtual Directory...9 IIS 7 Server: Configure Web Service Extensions...17 Allow All Unspecified CGI Modules... 17 IIS 7 Server: Handler Mappings...20 IIS 7 Server: Edit Default Error Behavior...23 Access Your Program Using IIS 7...26 Internet Information Services (IIS) version 8... 27 IIS 8 Server: Add Virtual Directory...27 IIS 8 Server: Configure Web Service Extensions...34 Enable All Unspecified CGI Modules... 34 Configure Individual CGI extensions...36 IIS 8 Server: Handler Mappings...37 IIS 8 Server: Edit Default Error Behavior...40 Access Your Program Using IIS 8...43 Appendix A: Configure individual.cgi...45 IIS 6...45 IIS 7 or IIS 8...46 Appendix B: Program-specific.cgi files...52 InfoCanon...52 Profiler...52 UnitySync...52
Internet Information Services (IIS) version 6 NOTE: Current versions of UnitySync and Profiler will not run on 32-bit servers and, therefore, will not likely run on any server with IIS 6. We have retained the instructions here for use with InfoCanon and the convenience of clients that are still running previous versions of UnitySync and Profiler. If you are installing either of the latter programs for the first time, however, please refer to the up-to-date server requirements for UnitySync or Profiler. IIS 6: Add Virtual Directory First, you must add a virtual directory for the program. 1. Start the IIS Manager found under Start > Administrative Tools. 2. Expand Web Sites 3. Right click on Default Web Site a. Select New b. Select Virtual Directory... NOTE: The path to add a virtual directory after you right click the Default Web Site may be simply Add Virtual Directory. 4. Click Next> when the Virtual Directory Creation Wizard starts.
5. Type in the Alias you wish to use to access the program. NOTE: In this example, UnitySyncX is used, resulting in the following URL: http://localhost/unitysyncx Use a descriptive name. For instance, if you are working with Profiler or InfoCanon, you will likely want to use the specific program name for an alias. 6. Select the Path to the virtual directory. This should be the cgi file folder within your program files. a. Click Next>
NOTE: In the example, c:\unitysync\cgi is used. The designation of the cgi folder is important for security reasons. DO NOT simply use c:\unitysync. 7. Select Execute to allow CGI programs to execute. NOTE: If you do not wish to allow all unknown CGI extensions to execute due to security concerns, you must configure the needed CGI files one by one. Instructions to do so are included in Appendix A. Simply skip these step 5 instructions if that is your situation. a. Click Next> b. Click Finish
8. Return to IIS and locate the virtual directory that you just created. Right-click and select Properties. 9. Select the Directory Security tab, then click Edit... in the Authentication and access control section. 10. If selected, unselect Enable anonymous access. Then, under Authenticated access, select
Integrated Windows authentication. 11. Click OK to save those selections. 12. Click OK on the virtual directories Properties page. You have successfully added your virtual directory.
IIS 6 Server: Configure Web Service Extensions Required CGI programs must be allowed to execute. In IIS 6 you are given the option to allow all unknown CGI extensions while you are configuring a new virtual directory (step 7 in the Add A Virtual Directory section). If you did not, and now need to, instructions are included to do this in one of two ways. Allow All Unknown CGI Extensions This is the quickest way to allow CGI programs to execute. 1. Start the IIS Manager found under Start > Administrative Tools. 2. Expand Web Sites. 3. Select Web Service Extensions: a. Click to select All Unknown CGI Extensions in the right window pane b. Click the Allow button on the left side of the right window pane 4. Click Yes to allow all CGI extensions to execute. You have successfully configured web service extensions.
Configure Individual CGI Extensions If you do not wish to allow all unknown CGI extensions to execute due to security concerns, you must configure the required.cgi files one by one. For instructions to configure individual CGI extensions, please see Appendix A.
IIS 6: Access Your Program Your IIS 6 configuration is complete! To access your program, open a browser window and type the alias address you selected in step #3 of Add a Virtual Directory (i.e., http://localhost/unitysyncx) and you should see the program interface. If you do not, please double check all configuration steps to ensure they have been completed, then contact support@dirwiz.com if any questions remain.
Internet Information Services (IIS) version 7 NOTE: Current versions of UnitySync and Profiler will not run on 32-bit servers. Therefore, IIS 7 is the minimum requirement for these programs. IIS 7 Server: Add Virtual Directory First you must add a virtual directory for the program. 1. Start the IIS Manager found under Start > Administrative Tools. 2. Expand Web Sites. 3. Right-click on Default Web Site. a. Select Add Virtual Directory... 4. Type in the Alias you wish to use to access the program. NOTE: In this example, UnitySync is used, resulting in the following URL: http://localhost/unitysync Use a descriptive name. For instance, if you are working with Profiler or InfoCanon, you will likely want to use the specific program name for an alias. Also, select where you would like the virtual directory to point to. This should be the cgi
folder within your program files. NOTE: In the example, c:\unitysync\cgi is used. The designation of the cgi folder is important for security reasons. DO NOT simply use c:\unitysync. Click OK. 5. Confirm the CGI role service is enabled in IIS. a. Go to Start > Administrative Tools > Server Manager
b. The Server Manager will open. Expand Roles, then Web Server (IIS) c. Scroll through the sections under Summary in the right window pane until you find Role Services d. Click Add Role Services e. Make sure that CGI is selected under Application Development. If it is, simply click Cancel to exit the window and proceed to step 6. If it is not, select CGI and click Next>.
f. You will be asked to confirm installation of your selection. Click Install. g. The next window will show you the progress of your installation. Nothing is click-able in this window. h. Finally, your installation results will appear. Once complete, click Close.
6. Return to the IIS Manager found under Start > Administrative Tools. 7. Expand Sites. 8. Expand Default Web Site. a. Locate the virtual directory that you just created. In our example, it is unitysync. Highlight the virtual directory and in the Features View menu that appears in the center pane, find Authentication (in the IIS section) and double-click it.
9. If Anonymous Authentication is Enabled, click Disable in the Actions pane. 10. If Windows Authentication is Disabled, click Enable in the Actions pane. You have created a virtual directory with the necessary configuration.
IIS 7 Server: Configure Web Service Extensions Required CGI programs must be allowed to execute. This can be done in one of two ways. Allow All Unspecified CGI Modules While this is the quickest way to enable CGI, you will only be able to execute All Unspecified CGI Modules if you are running IIS 7 in ISAPI mode. This feature is not available if you are running IIS in Integrated mode. If you are running IIS 7 in Integrated mode, or if you prefer to configure individual CGI, proceed to Appendix A. 1. Go to the IIS Manager (Start > Administrative Tools) and select the primary server to open the server Home page. 2. Under the IIS section in the main window pan, double-click ISAPI and CGI restrictions.
NOTE: This icon might be found under Security instead. 3. The window will change to show ISAPI and CGI extensions that are permitted on the web server. Click Edit Feature Settings... in the right pane. 4. Select Allow unspecified CGI modules, then click OK.
Configure Individual CGI Extensions If you do not wish to allow all unknown CGI extension to execute due to security concerns, you must configure the needed CGI files one by one. For instructions to configure individual CGI extensions, please see Appendix A.
IIS 7 Server: Handler Mappings 1. Return to the IIS Manager (Start > Administrative Tools) and select the primary server to open the server Home page. 2. Find the icon for Handler Mappings this may be found under IIS or Server Components and double-click it to open. 3. Right-click CGI-exe, then click Edit Feature Permissions...
4. Make sure that Execute is checked. If it is not, select Execute then click OK. 5. Double-click CGI-exe. Make sure the Request path is *.cgi. If it is not, fill in the Request path field with *.cgi and click OK.
Handler mappings are now configured.
IIS 7 Server: Edit Default Error Behavior This configuration step allows detailed error messages to be presented when accessing the Program from other than the local server. 1. Go to the IIS Manager (Start > Administrative Tools) and select the primary server to open the server Home page. 2. Expand the Sites folder. 3. Click on the Default Web Site to select, then double-click the Error Pages icon in the IIS section.
4. Find error 500 in the list and click on it to highlight. Then, click Edit Feature Settings... in the right pane. 5. The default setting for this error is Detailed errors for local requests and custom error pages for remote requests. This default setting will result in a generic error if you access the program from a remote server.
6. Instead, select Detailed errors then click OK to save the selection.
IIS 7: Access Your Program Your IIS 7 configuration is complete! To access your program, open a browser window and type in the alias address you selected in step #4 of Add a Virtual Directory (i.e., http://localhost/unitysync) and you should see the program interface. If you do not, please double check all configuration steps to ensure they have been completed, then contact support@dirwiz.com if any questions remain.
Internet Information Services (IIS) version 8 IIS 8 Server: Add Virtual Directory First you must add a virtual directory for the program. 1. Start the IIS Manager. From the Start page, go to Server Manager, then highlight IIS in the left pane. Right-click the default server shown in the Servers section on the right side of the window, then select Internet Information Services (IIS) Manager. 2. In the IIS Manager window, expand Sites. 3. Right-click on the Default Web Site. 4. Select Add Virtual Directory... 5. Type in the Alias you wish to use to access the program.
NOTE: In this example unitysync is used, resulting in the following URL: http://localhost/unitysync Use a descriptive name. For instance, if you are working with Profiler or InfoCanon, consider using the program name for the alias. 6. Select where you would like the virtual directory to point to. This should be the cgi folder in your program files. NOTE: In the example, c:\unitysync\cgi is used. Pointing to the cgi folder is important for security reasons. DO NOT use c:\unitysync. 7. Click OK. 8. Confirm the CGI role service is enabled in IIS.
a. Go back to the Server Manager and select IIS in the left column of the window. b. Scroll through the pane on the right side of the window until you find Roles and Features. c. Is CGI listed there? If so, it is enabled. You may proceed to step 10. If it is not, please continue. 9. Click the TASKS drop-down just above the Roles and Servers section on the right and select Add Roles and Features. a. The Add Roles and Features Wizard will appear. Select Role-based or feature-based installation and click Next. b. On the Server Selection page, click Select a server from the server pool, then find your server in the Server pool window below and click Next>.
c. On the Server Roles page, expand down to Application Development (Web Server (IIS) > Web Server > Application Development) and click on the unselected CGI, then click Next>. d. Click Next> on the next window, Features, to proceed.
e. Finally, click Install. f. The next window will show you the installation progress. Once it completes, click Close.
g. If you'd like to confirm the installation, go back to steps 6a, b and c and confirm CGI is now listed. 10. Return to the IIS Manager. From the Start page, go to Server Manager, then highlight IIS in the left pane. Right-click the default server shown in the Servers section on the right side of the window, then select Internet Information Services (IIS) Manager. a. Expand Sites b. Expand Default Web Site c. Locate the virtual directory that you previously created. In our example, it is unitysync. d. Highlight the virtual directory. e. In the Features View menu that appears in the center pane, double-click Authentication. The icon for Authentication is found in the IIS section.
11. If Anonymous Authentication is Enabled, click Disable in the Actions section in the right pane. 12. If Windows Authentication is Disabled, click Enable in the Actions section in the right pane.
You have successfully added the virtual directory.
IIS 8 Server: Configure Web Service Extensions CGI programs must be allowed to excute. This can be done in one of two ways. Enable All Unspecified CGI Modules While this is the quickest way to enable CGI, you will only be able to execute All Unspecified CGI Modules if you are running IIS 8 in ISAPI mode. This feature is not available if you are running IIS in Integrated mode. If you are running IIS 8 in Integrated mode, or if you prefer to configure individual CGI, proceed to Appendix A. 1. Start the IIS Manager. From the Start page, go to Server Manager, then highlight IIS in the left pane. Right-click the default server shown in the Servers section on the right side of the window, then select Internet Information Services (IIS) Manager. 2. Under the IIS section in the main window pane, double-click ISAPI and CGI restrictions.
NOTE: This icon might be found in the Security section. 3. The window will change to show ISAPI and CGI extensions that are permitted on the web server. Click Edit Feature Permissions... in the right pane. 4. Select Allow unspecified CGI modules, then click OK.
You have successfully allowed CGI to execute. Configure Individual CGI extensions If you do not wish to allow all unknown CGI extensions to execute due to security concerns, you must configure the needed CGI files one by one. For instructions to configure individual CGI extensions, please see Appendix A.
IIS 8 Server: Handler Mappings 1. Return to the IIS Manager (Server Manager > IIS > right-click the default server shown in the Servers section on the right side of the window, and select Internet Information Services Manager) and select the primary server to open the server Home page. 2. Double click the Handler Mappings icon found under either the IIS or Server Components section. 3. Right-click CGI-exe, then click Edit Feature Permissions...
4. Make sure that Execute is checked. If it is not, select Execute then click OK. 5. Double-click CGI-exe. Make sure the Request path is *.cgi. If it is not, fill in the Request path field with *.cgi and click OK.
You have successfully set up Handler Mappings.
IIS 8 Server: Edit Default Error Behavior This configuration step allows detailed error messages to be presented when accessing the Program from other than the local server. 1. Return to the IIS Manager (Server Manager > IIS > right-click the default server shown in the Servers section on the right side of the window, and select Internet Information Services Manager) and select the primary server to open the server Home page. 2. Expand the default server and then Sites folder. 3. Click on the Default Web Site to select, then double-click the Error Pages icon in the IIS section.
4. Find error 500 in the list and click on it to highlight. Then, click Edit Feature Settings... n the right pane. 5. The default setting for this error is Detailed errors for local requests and custom error pages for remote requests. This default setting will result in a generic error if you access the program from a remote server.
6. Instead, select Detailed errors then click OK to save the selection. You have successfully edited default error settings.
Access Your Program Using IIS 8 Your IIS 8 configuration is complete! To access your program, open a browser window and type in the alias address you selected in the Add Virtual Directory setup (i.e., http://localhost/unitysync) and you should see the program interface. If you do not, please double check all configuration steps to ensure they have been completed, then contact support@dirwiz.com if any questions remain.
Appendix
Appendix A: Configure individual.cgi IIS 6 1. Go to the IIS Manager (Start > Administrative Tools). Expand the default server and Web Sites, then click to select Web Service Extensions. 2. The New Web Service Extension window will appear. You'll need to: a. Type in an Extension name we suggest using the actual program and.cgi name b. Browse to the file in the cgi directory c. Select Set extension status to Allowed, then click OK. NOTE: There are several.cgi files that you will need to allow, and you'll need to go through the above steps for each of them. Please refer to Appendix B: Program-specific.cgi files for a complete list of the files for each program.
IIS 7 or IIS 8 1. Start the IIS Manager. From the Start page, go to Server Manager, then highlight IIS in the left pane. Right-click the default server shown in the Servers section on the right side of the window, then select Internet Information Services (IIS) Manager. 2. Under the IIS section in the main window pane, double-click ISAPI and CGI restrictions. 3. The window will change to show ISAPI and CGI extensions that are permitted on the web server. Click Add... in the right window pane.
4. In the Add ISAPI or CGI Restriction window: a. Browse to the cgi directory for the program you are configuring. b. In the lower right corner of the Browse window, use the drop-down to view All Files.
c. This step enables you to see the.cgi files you need to configure, as shown below. 5. Select one of the necessary.cgi files (as detailed in Appendix B).
a. Once you've opened one of the.cgi files needed, fill in a Description. We suggest using the program and cgi file name in our example, this is UnitySync config cgi. b. Click the check box next to Allow extension path to execute. c. Click OK. NOTE: There are several.cgi files that you will need to allow, and you'll need to go through the previous steps 4 & 5 for each of them. Please refer to the Program-specific.cgi files listed in Appendix B for a complete list for the program you are configuring. 6. Once you have added all of the necessary.cgi files, the Restrictions window will now show them with a status of Allowed. If any are listed as Not Allowed, it means you neglected to check Allow extension path to execute. You'll need to highlight those lines, right-click to Edit..., check the appropriate box, and then click OK.
7. See below how the list will look when all.cgi files are properly configured.
Appendix B: Program-specific.cgi files InfoCanon cgi-test.cgi config.cgi editor.cgi infocanon.cgi Profiler config.cgi profiler.cgi UnitySync config.cgi csv.cgi ldap.cgi logview.cgi odbc.cgi proc.cgi smtp.cgi