Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Windows Server 2003, Windows Server 2003 with SP1
The applications that you deploy on a server might fit into several categories, based on your assessment of their importance, their demand for server resources, or their history of instability. Group your applications according to the following categories, or make up your own set of application categories, before assigning your applications to application pools:
Typical: The application is stable and is not subject to extremely high user demand.
High-demand: The application is expected to receive a large number of requests, putting stress on the resources of your server.
Mission-critical: Application availability is mandatory for business purposes.
Problem: The application must be isolated from other applications and Web sites due to known or anticipated unstable behavior. If you must run test versions of an application on the same server that runs production applications and Web sites, consider it a problem application that must be isolated from all of the other applications on the server.
Unique: The application requires a configuration that is different from other applications that you have categorized as typical. For example, an application might require an identity that has access to more system resources than the default identity.