Manual configuration for IIS 7.x

Prerequisites

The installer needs some Internet Information Services (IIS) features to be activated:

• IIS Management Scripts and Tools
• ASP.NET
• .NET Extensibility
• ISAPI Extensions
• ISAPI Filters

To activate "IIS Management Scripts and Tools" on a Windows® Server 2008:

• Click on Start -> Control Panel -> Administrative Tools -> Server Manager -> Roles -> Web Server (IIS)
• Right Click -> Add Role Services
• Select "Management Tools"
• Check "IIS Management Scripts and Tools"
• Click the "Install" Button

Do the same for the other features.

Example:

To activate IIS Management Scripts and Tools on Windows 7

To activate IIS Management Scripts and Tools on Windows 7 and validate the basic IIS configuration requirements:

1. Verify IIS is installed. In Control Panel > Administrative Tools, you must have an entry called Internet Information Services (IIS) Manager.

   Figure: Control Panel with IIS Manager highlighted

   
   
   

2. Verify IIS is well-started. Open a browser and enter the URL: http://localhost. The IIS welcome screen displays.

   Figure: IIS Welcome Screen

   
   
   

3. Set the appropriate Windows Features. Go to Control Panel >> Programs and Features. Click Turn Windows features on or off.

   Figure: Turn Windows features on or off link

   
   
   

4. In the Windows Features dialog, select IIS Management Scripts and Tools, and verify that the ASP and the ISAPI options are also selected. When checking these options, other options may also be automatically checked. That is normal behavior, as they are combined options.

   Figure: Turn Windows features on or off dialog

   
   
   

Configuring IIS 7.x application pools

The application pool should be configured according to the kind of application the GAS ISAPI Extension will run. If the GAS ISAPI Extension runs only Web service applications, it is fully compatible with application pool parameters. If it runs Web or Desktop applications, IIS should drive all requests to the same worker process; therefore, a dedicated application pool should be created.

To create an application pool:

1. In IIS manager, right-click Application Pools and click Add Application Pool....
2. In the Add Application Pool dialog, enter a name for the application pool, for example "GASAppPool".
3. In the .NET Framework version box, select No Managed Code.
4. In the Managed pipeline mode box, select Classic.
5. Click OK.

   Figure: Completed application pool configuration

   
   
   

To configure the application pool to run Web and Desktop applications:

1. In IIS Manager, right-click the application pool, and click Advanced Settings...
2. In the Advanced Settings dialog, in the Process Model area, set the Idle Time-out (minutes) field to "0" or to a value that is greater than the USER_AGENT timeout value of 4GL applications that the application pool will run.
3. In the Process Model area, set the Maximum Worker Processes field to 1.
4. In the Recycling area, set the Disable Overlapped Recycle flag to True.
5. In the Recycling area, set the Disable Recycling for Configuration Changes flag to True.
6. Click OK.

The GAS ISAPI Extension will be executed on behalf of the user that is registered in the pool's properties. That user must have access to the FGLASDIR directory. To change the user identity that runs the GAS:

1. In IIS Manager, right-click the application pool, and click Advanced Settings...
2. In the Advanced Settings dialog, in the Process Model area, click the Identity field.
3. Click ... to open the Application Pool Identity dialog.
4. According to your security policy, either select a built-in account or set a custom account.
5. Click OK.
6. In the Advanced Settings dialog, click OK.
7. Finally, check that you have configured your application pool creation correctly. Right click the application pool (GASAppPool in our example), and click Advanced Settings... again. Compare your settings with the following screenshot.

   Figure: Compare your pool configuration setup

   
   
   

Configuring an IIS 7.x application

To create an application:

1. Create a directory on your disk that will be the Application root directory, the recommended directory is, for example, $FGLASDIR/ISAPI.
2. In IIS Manager, right-click the web site on which you want to add the application, for example "Default Web Site", and then click Add Application...
3. In the Add Application dialog, enter the alias of the application, for example "gas".
4. Enter the physical path to the directory created in step 1.
5. Click Select...
6. In the Select Application Pool dialog, select the application pool that has been defined previously.
7. Click OK.
8. In the Add Application dialog, click OK.

   Figure: Completed application configuration

   
   
   

The authentication configuration depends on your security policy. If all users have access to the application, the identity of the anonymous user should be configured as follows:

1. In IIS Manager, click the application on which you want to configure the identity of the anonymous user.
2. In the Features View panel, double-click the Authentication icon.
3. In the Authentication feature, select the Anonymous Authentication line.
4. Ensure that the status is Enabled.
5. In the Actions area, click Edit...
6. In the Edit Anonymous Authentication Credentials dialog, select Application pool identity.
7. Click OK.

   Figure: Configuration for anonymous authentication

   
   
   

To bind the application to the GAS ISAPI Extension:

1. In IIS Manager, select the application on which you want to bind the application to the GAS ISAPI Extension.
2. In the Features View panel, double-click the Handler Mappings icon.
3. In the Handler Mappings feature, in the Actions area, click Add Wildcard Script Map ...
4. In the Add Wildcard Script Map dialog, enter the path to the GAS ISAPI Extension DLL: $FGLASDIR\bin\isapidispatch.dll.
5. Enter a name for this mapping, for example "GAS ISAPI Extension".
6. Click OK.
7. To the question Do you want to allow this ISAPI extension?, click Yes.

   Figure: Completed Script Map configuration

   
   
   

8. In the Handler Mappings feature, in the Actions area, click View Ordered List...
9. Ensure that the GAS ISAPI Extension is at the top of the list.
10. Click View Unordered List...
11. In the Actions area, click Edit Feature Permissions...
12. In the Edit Feature Permissions, ensure that Script is selected and all other are unselected.
13. Click OK.

Although the GAS ISAPI Extension has been allowed automatically when you answered Do you want to allow this ISAPI extension? with Yes, to do it manually:

1. In IIS Manager, click the root node, the one that contains the host name.
2. In the Features View panel, double-click the ISAPI and CGI Restrictions icon.
3. In the ISAPI and CGI Restrictions feature, in the Actions area, click Add...
4. In the Add ISAPI or CGI Restriction dialog, enter the path to the GAS ISAPI Extension DLL: $FGLASDIR\bin\isapidispatch.dll.
5. Enter a description, for example "GAS ISAPI Extension".
6. Ensure that the Allow extension path to execute checkbox is selected.
7. Click OK.

   Figure: Completed ISAPI CGI restrictions configuration

   
   
   

Post requisites

After you have finished the installation, you now need to configure the GAS ISAPI Extension configuration file, see Finishing the installation .