Manual configuration for IIS 6.0

These are the instructions for the manual configuration of the ISAPI dispatcher for IIS 6.0.

Configuring IIS 6.0 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 then click New and Application Pool...
  2. In the Add New Application Pool dialog, enter a name for the application pool ID, for example "GASAppPool".
  3. Click OK.

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

  1. In IIS manager, right-click the application pool, and then click Properties.
  2. Click the Recycling tab.
  3. Ensure that all checkboxes are unchecked.
  4. Click the Performance tab.
  5. In the Idle timeout section, ensure that the Shutdown worker processes after being idle for checkbox is unchecked, or that its value is greater than the USER_AGENT timeout value of 4GL applications that the application pool will run.
  6. In the Web garden section, ensure that the value of Maximum number of worker process is 1.
  7. Click OK.

The GAS ISAPI Extension will be executed on behalf of the user that is registered in thepool'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 then click Properties.
  2. Click the Identity tab.
  3. According to your security policy, either select a built-in account or set a custom account.
  4. Click OK.
Note: In order to configure application pools according to the type of applications that will be run, two different virtual directories, each with its own application pool, may be created on the same instance of IIS - one that will run only Web service applications, and another thatwill run only Web and Desktop applications.

Configuring an IIS 6.0 application

To create a virtual directory:

  1. Create a directory on the disk that will be the application root for the application. For further details about IIS-related vocabulary, see Microsoft's documentation for IIS 6.0.
  2. In IIS Manager, right-click the web site on which you want to add the virtual directory, for example "Default Web Site", and then click New and Virtual Directory...
  3. Click Next on the first sheet of the Virtual Directory Creation wizard.
  4. Enter the alias of the virtual directory, for example "gas". This name will be the virtua ldirectory part of the URLs accessing the GAS. Click Next.
  5. Enter the path to the directory created in step 1. Click Next.
  6. On the Virtual Directory Access Permissions sheet, uncheck the Read checkbox and check Run scripts (such as ASP). Click Next.
  7. Click Finish.

On IIS 6.0, to bind the virtual directory to the GAS ISAPI extension:

  1. In IIS Manager, right-click the virtual directory previously created, and then click Properties .
  2. Click the Virtual Directory tab.
  3. In the Application settings area, click Configuration..., and then click the Mappings tab.
  4. Optionally, in the Mappings tab, remove all predefined application extensions.
  5. In the Wilcard application maps area, click Insert...
  6. Enter the path to the GAS ISAPI Extension DLL: FGLASDIR\bin\isapidispatch.dll.
  7. Uncheck the Verify that file exists checkbox.
  8. Click Ok.
  9. In the Application Configuration dialog, click Ok.
  10. In the Properties dialog, click Ok.

On IIS 6.0, to allow the GAS ISAPI Extension to run:

  1. In IIS Manager, click Web Service Extensions.
  2. Click Add a new Web service extension...
  3. Enter an extension name, for example "Genero Application Server".
  4. Click Add...
  5. Enter the path to the GAS ISAPI Extension DLL: FGLASDIR\bin\isapidispatch.dll.
  6. Click Ok.
  7. Check the Set extension status to Allowed checkbox.
  8. Click Ok.

To finish the installation, see the Finishing the installation section.