To publish an ASP application, you save the application files in the directory defined for that application on your Web server (be sure that the directory has either Script or Execute permission enabled). Your administrator can set up the ASP application directory on the server by using the procedure in "Adding an ASP Application" in "Chapter 3: Managing Sun Chili!Soft ASP." For more information about how ASP applications are structured, see "Creating the Basic ASP Application" in this chapter.
To verify that an ASP page is displaying properly, you can request the page with your browser by typing its URL. (Remember, ASP pages must be served, so you cannot request an *.asp file by typing its physical path.) After the page loads in your browser, you will notice that the server has returned an HTML page. This may seem strange at first, but remember that the ASP Server parses and executes all server-side scripts prior to sending the file. The user always receives standard HTML.
When publishing ASP pages created in FrontPage, be aware that if the EnableParentPaths configuration setting is no, the default, CreateObject ("Scripting.FileSystemObject") calls generated in the global.asa file by FrontPage will not work. Your system administrator must either change EnableParentPaths to yes, or else you must change the code that FrontPage generated in the global.asa file to Server.CreateObject ("Scripting.FileSystemObject"). For more information, see "Configuring File System Access" in "Chapter 3: Managing Sun Chili!Soft ASP."
Copyright 2002 Sun Microsystems, Inc. All rights reserved. Legal Notice.