The Windows NT Option Pack provides services for managing ASP applications on the Web server. For example, Internet Service Manager gives the application developer an easy-to-use administration tool to set application properties. In addition, Active Server Pages provides scripting features that enable your applications to store global data. This topic briefly introduces some of these application management features and provides links to more detailed information.
An application starts the first time the Web server receives a request for an ASP page in that application. An application ends when the Web server is shut down or when you stop an application using the Unload button in Internet Service Manager. You can only use the Unload button on applications that are running in a separate memory space (isolated) from the Web server process. For more information, see Stopping Isolated Applications.
ASP applications normally run in the same memory space, or process, as the Web server. While this improves the performance of an ASP application, it places the Web server process at risk if the application fails. You can isolate an application by running it in a separate memory space from the Web server. If the ASP application fails, other applications and the Web server itself are protected. For more information, see Isolating Applications.
When you are writing applications, you may need to make information pertaining to an application available to all users of the application. For example, you might want to create variables that enable system administrators to customize an application for their site by setting a different greeting or changing the title font on all ASP pages. These changes will be seen by any user who visits the site.
You can make data available to all users of an application from all pages of an application in several ways. The most frequently used is to give a variable or an object instance application scope by storing it in the ASP Application object. Application scope is useful for global data, such as a global counter, or global application configuration information, such as information stored in the registry or metabase. To learn how to give variables application scope, see Using Variables. To learn how to give objects application scope, see Setting Object Scope.
You may also need to write scripts that are run whenever an application starts up or shuts down. For information on defining these application-start or application-end events, see Global.asa Reference.