Migrating a Web Server to IIS 5.0
Migrating a Web Server to IIS 5.0 |
|
NES CGI applications can be ported directly to run on IIS 5.0, or they can be converted to ISAPI or ASP. For more information, see Migrating Web Applications.
Table 3.6 NES 3.5 Application Settings and Corresponding IIS Properties
NES 3.5 Configuration Setting |
Migrated by Wizard? (Y/N) |
IIS Metabase Property |
IIS Snap-in Configuration |
| CGI Directory | Yes | Not applicable | The wizard creates a CGI virtual directory and enables the CGI Execute permission. |
| CGI File Type | No | Not applicable | There is no corresponding property in IIS 5.0. |
| Java | No | Not applicable | The Java virtual machine is already enabled on IIS 5.0, so there is no need to migrate this setting. |
| Query Handler | No | Not applicable | There is no corresponding property in IIS 5.0. |
| Server Side JavaScript | No | Not applicable | IIS 5.0 includes server-side support for JScript and VBScript. There is no need to migrate a switch setting for these languages. |
| ShellCGI Directory | Yes | Not applicable | The wizard creates a ShellCGI virtual directory and enables the CGI Execute permission. |
| URL Prefix | Yes | Not applicable | The wizard creates a corresponding virtual directory. |
| WAI Management | No | Not applicable | This setting has to do with the Internet Inter-ORB Protocol (IIOP); IIS 5.0 uses the COM and DCOM object models. |
| WinCGI Directory | No | Not applicable | WIN CGI is not supported in IIS 5.0. |