Windows2003 Campus Web Server Frequently Asked Questions

At present, there are more and more schools using Windows 2003 as a web server. However, for users who are used to Windows 2000/NT, if they want to set up a complete, secure and reliable Windows 2003 servers may encounter many unexpected problems. Based on the experience of personal experience in the past two years, the author focuses on the characteristics of the more commonly used Web services in schools, and focuses on the differences between them and Windows 2000.

1. IIS 5.0 Isolation Mode

IIS 5.0 Isolation Mode manages application processes in a similar way to process management in IIS 5.0: all in-process applications run inside Inetinfo.exe, out-of-process applications Run in a separate DLL host.

2. IIS 6.0 Worker Process Isolation Mode

When configured to execute in worker process isolation mode, all application code runs in an isolated environment. This design eliminates some of the existing bottlenecks. Worker Process Isolation mode allows administrators to isolate any content (from a single Web application to multiple sites) into a separate worker process.

Windows 2003 supports two working modes at the same time. The default is ISS 6.0 worker process isolation mode. Worker process isolation mode greatly enhances the reliability of IIS by preventing one application or site from stopping and affecting another application or site. So how do you set up two working modes?

Start IIS Manager, right click on the website, select “properties & rdquo;, open the properties dialog (Figure 1). In IIS 6.0 worker process isolation mode, all application code runs in an isolated environment. How are they isolated? Windows 2003 has added an application pool, and worker process isolation mode allows customers to create multiple application pools, each of which can have different configurations. Because these application pools receive their requests directly from the kernel (not the WWW service), performance and reliability are enhanced. To isolate web applications that run on the same computer but belong to different websites, you need to create a separate application pool for each website.

Figure 1 Open IIS Properties Dialog Box

So, what is an application pool? This is a new concept from Microsoft: An application pool is a configuration that links one or more applications to one or more worker process collections. Because applications in an application pool are separated from other applications by worker process boundaries, applications in one application pool are not affected by problems that occur in applications in other application pools.

3. Create an application pool

In IIS Manager, open the local computer, right-click on "Application Pool" and select New "Application Pool" (you must create it in worker process isolation mode) Application pool). In the <quo;Application Pool Name” box, enter a new application pool name. If the ID (such as AppPool #1) that appears in the "Application Pool ID" box is not what you want, you can rename it. If you clicked “Use an existing application pool as a template”, right-click on the application pool you want to use as a template in the “Application Pool Name” box. Finally click [OK].

4. Assign an Application Pool

In IIS Manager, right-click the application for which you want to assign an application pool and click “Properties”. Click the “home directory' tab to confirm that the "application name" for the directory or virtual directory you are assigning has been filled out. If the "application name” box has not been filled out, click “Create” and enter a name.

In the "Application Pool" list box, select the name of the application pool you want to assign to it. Finally click [OK] (Figure 2).

Figure 2 Newly created application pool name