The IIS server uses a virtual directory from which the clients run the applications. Using the Microsoft Management Console (MMC), run the Virtual Directory Wizard to create your virtual directories, as follows:
Start the Virtual Directory Wizard by locating the Default website (if you are running MMC on the same machine as the IIS server) or choosing the name of the server (if MMC is on a different machine to the IIS server). Right-click the item and select New then Virtual Directory on the popup menu.
Type an alias. This is the name that users select to start their application, so choose a meaningful name.
Note: The applicationName in the Global.asa file and the virtual directory name must be the same for the system to work.
Supply the physical path of the directory in which you stored the generated ASP.NET Forms, for example d:\inetpub\ICETEST.
Set the permissions. You must choose “Allow Script Access”.
Press Finish and the wizard creates the virtual directory.
After the virtual directory is created, you need to customize it for use with the ASP.NET Forms. Select the virtual directory, and choose Properties from the right-click or Action menu. Set the properties as follows:
Select the Virtual Directory tabbed page, select Run in separate memory space (isolated process) in the Application Settings section, and set Permissions to Script or Execute.
Note: When you run an application as an isolated process, you can press
Unload to stop the application and remove it from the cache. You might need to do this if you have updated any of the ASP.NET Forms and copied them to the server, or if you want to copy new versions of the .jar files to the server.
Select the Documents tabbed page, select Enable Default Document and specify your default document name. The document you specify is opened when you use a URL without a specific document, for example, www.unisys.com/ICETEST/. There is a default.htm file supplied in the package, that shows you how to open a new browser window for your application, without the browser menus or buttons. If you do not want to open a new window, but want to run the system directly, enter default.asp your default document.
Return to the Virtual Directory tabbed page, press Configuration to access the Configuration Settings tabbed window.
Select the App Mappings tabbed page and check “Cache ISAPI applications”.
Select the App Options tabbed page and check “Enable session state”. Set the Session timeout to a reasonable limit, so that you conserve your resources if a web user has become inactive. Set the ASP.NET Script timeout to a value such as five minutes (300 seconds). This limit only applies when the host application is starting up. You can lower this value if your application is always active or if it starts up quickly.
Select the Process Options tabbed page and check “Cache all requested ASP.NET files”. Performance suffers if this is left unchecked.
Select the App Debugging tabbed page. If are be customizing the ASP.NET Forms for your site, check “Enable ASP.NET server-side script debugging” and “Enable ASP.NET client-side script debugging”. If you do not want to send detailed ASP.NET errors to the client, check “Send text message to client” and type an appropriate error message for the users.