Previous PageNext Page

5.2.1 Defining ASP Applications

There are different methods for defining ASP applications depending on the underlying operating system.
 

5.2.1.1 Defining Applications on Windows NT

On Windows NT, Chili!Soft ASP allows you to define ASP applications by adding aliases or virtual directories to your Web server. Each alias or virtual directory is treated as an ASP application by Chili!Soft ASP. Different Web servers have different terminology for aliases or virtual directories.
 
  • With Apache, you may define an ASP application by adding an alias to the srm.conf or httpd.conf files (depending on the version of Apache you are using.)
  • With Netscape, you may define an ASP application by adding an "additional document directory" using the Netscape Server Administration tool.
  • With Lotus servers, you may define an ASP application by adding a pass directive to the httpd.conf configuration file.
For more information, see Appendix C: Supported Server Information.
 

5.2.1.2 Defining Applications on Unix

There are several different options available for defining ASP applications with Chili!Soft ASP for Unix.
 
With All Web Servers
With Chili!Soft ASP for Unix and any supported Web server, an ASP application can be defined with the following methods:
 
  • By adding an entry to the [applications] section of casp.cnfg
  • By adding an alias to the Web server's configuration file (only if use_aliases=yes in [applications] section of casp.cnfg.)
  • By adding an entry to the ASP User Configuration file. The name of this file is defined in the [applications] section of casp.cnfg, with Chili!Soft ASP looking for the file in the Web server's document root.
  • By adding an entry to the services.cnf file generated by FrontPage 2000. This file is located in the /_vti_pvt subdirectory of the Web server's document root.
With Apache Web Server and Virtual Hosts
If you are using the Apache Web server and you have configured it to provide virtual hosts support, this additional information applies. You may define ASP applications:
 
  • By adding an entry to the [applications] section of casp.cnfg. Applies to the "real host" only.
  • By adding an alias to the Web server's configuration file (only if use_aliases=yes in [applications] section of casp.cnfg.) If the alias appears outside a <virtualhost> ... </virtualhost> block, it applies to the "real host" only. If the alias appears inside a <virtualhost> ... </virtualhost> block, it applies to the virtual host.
  • By adding an entry to the ASP User Configuration file. The name of this file is defined in the [applications] section of the casp.cnfg file. Chili!Soft ASP looks for this file in the document root of each host, "real" or virtual. "Real host" entries apply to the "real host" only.
  • By adding an entry to the services.cnf file generated by Front Page 2000. This file is located in the /_vti_pvt subdirectory of the web root of each host, "real" or virtual. "Real host" entries apply to the "real host" only.
Important Notes
The following important notes apply to defining ASP applications to Chili!Soft ASP.
 
  • ASP applications defined in the ASP User Configuration or FrontPage 2000 services.cnf may only be defined using the application name (for example, "/appname"). The files that make up this application all must exist within the Web server's document root, and the Global.asa file, if present, must be located in the top-level directory. An application named /customers must correspond to a real top-level directory named customers in the Web server's document root.
  • ASP applications defined in the casp.cnfg file or as an alias in the Web server configuration files may contain files outside of the Web server's document root. The Global.asa file, if present, must be located in the top-level directory refenced by the ASP application.
  • ASP applications defined in the ASP User Configuration or FrontPage 2000 services.cnf files are recognized dynamically by Chili!Soft ASP.
  • ASP applications defined in the casp.cnfg file or as an alias in the Web server configuration files are not recognized dynamically. Chili!Soft ASP must be restarted to recognize these applications.
  • In case of naming conflicts between ASP applications defined in different locations, Chili!Soft ASP will honor application definitions in the following order: 1. Web server aliases, 2. casp.cnfg file entries, 3. FrontPage 2000 services.cnf file entries, and 4. ASP User Configuration file entries.
  • The ASP User Configuration file should contain an [applications] section, just like the casp.cnfg file. A sample of ASP User Configuration file contents appears below:

[applications]

/appname1

/appname2


Copyright © 2000 Chili!Soft

Previous PageTop Of PageNext Page