Sun Chili!Soft ASP Sun Chili!Soft
ASP Sun Microsystems

 

Defining Applications on UNIX

This topic describes the options that are available for defining Sun Chili!Soft ASP applications on UNIX-based systems. Some options might not be available on Cobalt platforms.

Caution

Take great care when making the changes described in this section. Changes you make could require a complete reinstall of Sun Chili!Soft ASP, and could void your eligibility for customer support. You should back up your data before making any changes.

Most of the configuration settings described in this section are easily accessed from the Sun Chili!Soft ASP Administration Console. It is strongly recommended that you use the Administration Console whenever possible, as described in "Using the Administration Console" in this chapter.

With Sun Chili!Soft ASP running on a UNIX system with any supported Web server, you can define an ASP application by using the following methods:

   Adding an entry to the [applications] section of the Sun Chili!Soft ASP configuration file, casp.cnfg. For more information, see "Editing the Sun Chili!Soft Configuration File" in this chapter.

   Adding an alias to the Web server configuration file (only if use_aliases=yes in the [applications] section of casp.cnfg).

   Adding an entry to the services.cnf file generated by FrontPage, located in the /_vti_pvt subdirectory of the Web server document root directory.

The ASP Server dynamically recognizes ASP applications that are defined in the Sun Chili!Soft ASP User Configuration file or the FrontPage services.cnf file. These applications must be defined by using the application name (for example, "/appname"). An application named /customers must correspond to a real top-level directory named "customers" in the Web server document root directory. The files that make up this application must all exist within the Web server document root directory. The global.asa file, if present, must be located in the top-level directory.

The ASP Server does not dynamically recognize ASP applications that are defined in the Sun Chili!Soft ASP configuration file, casp.cnfg, or that are defined by using an alias in the Web server configuration files. The ASP Server must be restarted to recognize them. ASP applications defined in the casp.cnfg file or by creating an alias in the Web server configuration files can include files outside of the Web server document root directory. The global.asa file, if present, must be located in the top-level directory referenced by the ASP application.

If there are naming conflicts between ASP applications that are defined in different directories, the ASP Server honors application definitions in the following order:

1.   Web server aliases

2.   casp.cnfg file entries

3.   FrontPage services.cnf file entries

4.   ASP User Configuration file entries

Note

Sun Chili!Soft ASP for UNIX- and Linux-based systems dynamically recognizes ASP applications created by FrontPage, but only if the application is not in a nested sub-Web. If the application (and its associated global.asa file) is located in a directory that is not a top-level directory of the Web server document root directory, you must define this application using either the [applications] section of Sun Chili!Soft ASP casp.cnfg file, or by adding an alias to your Web server configuration. For more information, see "Editing the Sun Chili!Soft Configuration File" in this chapter.

Defining an Application on iPlanet Web Server

For the purpose of defining Application and Session scope, the ASP Server considers all .asp files located in a virtual directory to be part of one application. You can use the NameTrans parameter in the obj.conf file to define an application. The following example defines an application called "/dosperros":

NameTrans fn="pfx2dir" from="/dosperros" dir="/opt/casp-net30/caspsamp/dosperros"

If you are using the Web server's Administration tool, you can define an ASP application by adding an "additional document directory."

Defining an Application on Apache Web Server

For the purpose of defining Application and Session scope, the ASP Server considers all *.asp files located in a virtual directory to be part of one ASP application. You can use the Alias parameter in the srm.conf file (in httpd.conf for Apache 1.3.4, 1.3.6, or 1.3.9) to define an ASP application. The following example defines an application called "/caspsamp":

Alias /caspsamp "/[C_ASP_INSTALL_DIR]/samples"

where [C-ASP_INSTALL_DIR] is the directory in which Sun Chili!Soft ASP is installed.

If you have configured support for virtual hosts, you can define ASP applications on Apache Web Server as follows:

   By adding an entry to the [applications] section of casp.cnfg. This applies to the "real host" only.

   By adding an alias to the Web server configuration file (only if use_aliases=yes in the [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. Sun Chili!Soft ASP looks for this file in the document root directory 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 FrontPage. This file is located in the /_vti_pvt subdirectory of the root directory of each host, "real" or virtual. "Real host" entries apply to the "real host" only.

Copyright 2002 Sun Microsystems, Inc. All rights reserved. Legal Notice.