To install an application is as easy as to upload a file to the "appl" directory on your website.  If the file extension is ".bs", it will be picked up by the Prelude (pt%prelude).  For all other extensions, the file will be picked up by the Application (pt%application).

For example, if you upload "appl/myappl.bs" and "appl/myappl.htm", when you enter, say, http://www.mysite.com/myappl.htm, the myappl.bs will run in the Prelude section and myappl.htm the Application section.

If you want to include files other than the implicit ones, you may define the scheme file "appl" (scheme%appl&).  For example:

Prelude:/showacc.htm=~/acc/readdb.bs
Application:/showacc.htm=~/acc/listdb.htm

That means /showacc.htm will pick up acc/readdb.bs in the Prelude section and acc/listdb.htm in the Application section.  ~/ stands for the website home directory.  Without it, it will search through the normal include path.  You can even include an application in the Portal Object.  For example, "portal/appl/cart.htm".

You may wonder why can't we name listdb.htm as showacc.htm and upload as /showacc.htm?  Well, you can, but that means the page will become an "actual" page by itself, and all the virtual page features will not be available, while mapping /showacc.htm to acc/listdb.htm will cause acc/listdb.htm runs inside the Application section of the virtual page.

You may map the whole path.  Here is another example:

Application:/news/=appl/newsreader.htm

In the "/news/" application, the file "appl/newsreader.htm" will process the path (pt%SP) to determine which news to display.  For example, /news/20041102.htm may lead newsreader.htm to retrieve items from the "news" table where key equals to 20041102 or like.

You may have more than one path mapping to the same application file.  For example, if you have

Application:/whether/=appl/newsreader.htm

and /whether/20041102.htm is accessed, the newsreader.htm will access the "whether" table instead.