[Top] [Prev] [Next] [Bottom] [Contents]

Configuring the Default Tool Options Web Administration

 There is a default configuration file which holds the default options for any user of Sapphire/Web who doesn't have a configuration file in their home directory. Setting these options will help new users to get up and running. The configuration file is:

sapphire_home/config/Sapphire.cfg
A few of the more important Project Options are explained below. For further information on modifying this file, see the User's Guide.

Project Option Brief Description
Makefile.$SA_DEPLOY-MENT_TARGET With this option, you choose how you want your project application to be deployed: CGI, FastCGI, NSAPI, etc.
Makefile.exeSuffix Some web servers can be configured to allow only files with certain extensions (often .cgi) to be executed as CGI executables. This option permits Sapphire/Web to use the specified extension.
Test.CGI Path Location of project CGIs during the test phase. If this directory is local then specify its full path. If not, then it must be of the form hostname:/full_path/
Test.CGI URL This is the URL of a project CGI during the test phase. This URL must point to the same location as Test.CGI Path and must be a valid URL. If this directory is local then specify its full path. If not, then it must be of the form hostname:/full_path/
Test.HTML Path Location of project HTML files during the test phase. It must be of the form hostname:/full_path/
Test.HTML URL The URL of a project HTML file CGI during the test phase. It must point to the same location as the Test.HTML Path option and must be a valid URL.
Test.Database User Name The User ID assumed by the program generated by your Sapphire/Web project.
Test.Database User Password The password for the User ID assumed by the program generated by your Sapphire/Web project.
Test.NSAPI URL The URL where you wish project NSAPIs to be located.

When using World Wide Web applications, users do not generally have to log in with a username and password. Therefore, a server application that generates an HTML document needs a built-in user name and password. This guest user account should, in general, be very limited as far as what it can do to the database.

Remember that Project Options are default hard-coded values incorporated in the generated applications - you can change them any time Sapphire rebuilds the applications.

There are sample values in the Sapphire.cfg file that can be used for reference. It is strongly recommended that you use the #user and #proj keywords when defining these options.

Note: Beware of users overwriting each others' project and HTML documents. This will almost certainly happen if all of the documents are held in the same directory by the users. It is a good idea to have a separate directory for each user, and to incorporate a source code management system such as SCCS or RCS. Be sure the users know how to change Project Options for each project.

Configuring Support Tools Web Administration

 There are several shell scripts that come with Sapphire/Web which extend its power and flexibility. They permit the user to select an HTML Authoring tool, select a Web Browser, install applications and HTML documents, perform source control tasks, and more. See the User's Guide for a detailed explanation of these scripts as well as functions of the scripts delivered with the tool.

Browsers which do not support the GET<->POST method (like Mosaic 2.4) cannot be used. There are no plans for supporting this in the future. There are two reasons for this:

1. Submission without GET<->POST may corrupt data.

2. There is a lack of support on many operating systems

Note: Sapphire/Web includes the script bin/sabrowser.sh, which is currently configured for Netscape Navigator. If you do not have Netscape installed on your system you must change the sabrowser.sh script so that it works with your chosen browser. See the User's Guide for details.

[Top] [Prev] [Next] [Bottom] [Contents]

info@bluestone.com
Copyright © 1997, Bluestone. All rights reserved.