Using the User Configuration File

In a shared Web hosting environment, rather than requiring the system administrator to define each ASP application (as described in Adding ASP Applications), you can enable ASP developers to define their own ASP applications in a User Configuration file. To do this, the system administrator must first edit the Sun ONE ASP configuration file, casp.cnfg, so that the ASP Server recognizes applications that are defined in the User Configuration file. Then ASP developers can create the file and define their ASP applications within it.

To enable developers to define their own ASP applications, take the following steps:

In the [applications] section of the Sun ONE ASP configuration file, casp.cnfg, specify the path name of the User Configuration file (.aspconf) that defines the ASP applications.

[applications]

config_name=.aspconf

When you do this, the ASP Server looks for this file in the document root of the Web server and each virtual host. For more information about editing casp.cnfg, see Editing the Sun ONE ASP Configuration File.

Create a User Configuration file. It should be a plain text file named .aspconf. Within this file, specify the ASP application name to define as follows:

[applications]

/[appname]

where [appname] is the ASP application name. The ASP application name must be the same as the name of the ASP application root directory, which is contained in the document root of the virtual host.

Any applications defined in the User Configuration file are dynamically recognized, without requiring the ASP Server to be restarted.

There are two limitations on applications defined in the User Configuration file:

The application directory containing the global.asa file must be directly below the top-level directory of the Web server or virtual host document root.

If the User Configuration file appears in the document root of a virtual host, the ASP applications are applied only to that virtual host, and not to others.