Installing ScriptEase:WebServer Edition
This chapter is designed to help you get ScriptEase:WebServer Edition up and running on your Web server. This chapter provides general installation instructions that apply to all servers and installation configurations. For specific instructions for your operating system and server platform see the README.DOC file that came with the ScriptEase:WebServer Edition installation files.

This chapter uses the allfield.jse CGI script as a mechanism for making sure that ScriptEase:WSE is properly installed on your Web server. Once installed, all the other sample scripts should work and you can begin developing your own applications.

To test your ScriptEase:WSE installation you need a Web server running that supports an interface extension, such as CGI, ISAPI, or ACGI (most do). Once you have ScriptEase:WSE installed, you will reference it with an Uniform Resource Locator (URL) to make sure it is functioning properly.

Installation Files
On all platforms, ScriptEase:WSE is installed using the SESETUP program. If you're installing from floppy disks, SESETUP will be found on the first disk and can be executed directly from there. If you're installing from a download compressed file (e.g.: zip, tar), create a temporary directory and uncompress all of the files into that temporary directory.

The files on your installation disks or in the installation directory will be similar to these (some operating systems do not use the ".EXE" extension for executable files):

These additional files are used for remote development and debugging:

Note that the installation program (SESETUP) will not copy any of these files except for those in the SEWSE?.BIN files. All of the other files are used for administering or debugging ScriptEase:WSE and you can keep these files on the disk or copy them to a more useful location.

Installation Instructions: SESETUP
To install ScriptEase:WSE on your system, you must first determine where your Web server requires binary executables to be placed. If this is your own site, this is straight forward and configurable. If you are using an Internet Service Provider (ISP) it may require getting to know your local WebMaster. Most commercial Web sites from an ISP give you cgi-bin access. If you have any trouble please contact your ISP for assistance.

Once you have located the bin directory on your Web server (often this is called cgi-bin, although it can have any name) you will need to install the ScriptEase:WSE files. The SESETUP program copies all of the files to your server automatically. Note that SESETUP must be executed from the server (or from a remote shell on the server) and not from a web browser.

SESETUP runs in a slightly different form on all operating systems. But the questions that must be answered are the same across platforms. This chapter will use the 32-bit Windows version as an example.

When you run SESETUP, you will first see a licensing agreement to read and accept, and then a window similar to the one pictured in figure 2.1 (as seen in the 32-bit Windows version). The window asks for the following information

• Local-Path of BIN/Executable: Enter the full path name of the directory to put the ScriptEase:WebServer Edition executables in. SESETUP will not create this directory and so it must already exist. Most web servers are already pre-configured with a path for placing script executables. On many systems this directory has the name "cgi-bin". On systems supporting Win-CGI there may be a directory named "wcgi-bin" for placing Win-CGI scripts, and "cgi-bin" for placing standard CGI scripts; ScriptEase:WSE will support either interface (remember which you chose in installation for the following configuration settings).
• URL of BIN/Executable: Enter the full URL of the path described above in Local-Path. Most web servers have a configuration program for mapping physical directories to URLs. Consult your webserver configuration program for determining the URL for the BIN/Executable directory.
• Local path for sample files: Enter the path (SESETUP will create the path if it doesn't already exist) of a folder or directory for SESETUP to put the many ScriptEase:WSE sample scripts into. This must be a directory within a path that your WebServer is configured to have available for web pages. A good place to put this scripts is just below the directory where you have a home page.
• URL of that sample directory: Enter the URL needed to access that sample directory. For example, if the your homepage is local path C:\web and its URL is http://www.mysite.com/ and if your local sample path was C:\web\sewse then the URL for the sample path is http://www.mysite.com/sewse.
• Local path for data files: Enter a path that the ScriptEase:WSE samples are free to write data into. This can be the same directory as the local path for sample files. You may want to specify a different directory here if you are running a system with potential security problems, such as a multi-user UNIX system with ftp and telnet capabilities. These directories will be created if they don't already exist.
• Use long filenames (.html instead of .htm): The ScriptEase:WSE sample files can be copied using the .htm or .html extension. The longer name is standard on must UNIX-type systems. If your system does not support long filename (e.g., Win-16 or OS/2 on a FAT partition) then specify the shorter name.
• User Key: The security key that allows ScriptEase:Webserver Edition to be fully functional. This was supplied when you purchased this software. If you are evaluating ScriptEase:WSE, a key is not required. A simple reminder will be entered in all the html documents you produce.

After you supply this information, SESETUP will copy all of the sample files onto your server system. Finally, SESETUP will remind you of the URL to specify in any browser to view the sample pages; remember this URL (e.g. http://www.mysite.com/sewse/sewse.html).

When SESETUP is finished, it will automatically start the configuration program (SEWSECFG). It is launched for both the debuggable version of sewse and the faster nondebuggable version.

Configuration Instructions: SEWSECFG
SEWSECFG is the program to configure ScriptEase:WebServer Edition. SEWSECFG will run after the installation program (SESETUP) is run. SEWSECFG can be executed again any time after installation. It is not installed by default but can be found in the installation distribution. It is a self contained executable and you can put it whereever you wish.

SEWSECFG varies between operating systems, but the input it uses is the same across all system. Here is an example from the Windows 32 SEWSECFG.EXE (these explanations apply to all version of SEWSECFG):

• Password: Enter a password to be used when remote-debugging ScriptEase:WSE. This password will prevent other users from getting access to the powerful features and commands that the debugger allows you to execute directly on the server from a remote location. If this field is left blank then there will be no password.
• SecurePath: Enter the path or paths from which ScriptEase:WebServer Edition will be permitted to execute .JSE scripts. ScriptEase:WSE will only permit scripts to be executed if they are contained within the tree described by this path. More than one path can be specified by separatingthe paths with semi-colons.
• JSEPath: Enter the default path or paths where ScriptEase:WSE will automatically search for files included with #include and #link statements.
• WinCGI (windows only): Select this item if the Executable/BIN directory you copy SEWSE.EXE or SEWSEDB.EXE to is configured to use the Win-CGI protocol instead of the standard CGI protocol. Note that this option is only available for Win16 and Win32 (not including ISAPI) versions of ScriptEase:WebServer Edition.
• User Key: The security key that allows ScriptEase:Webserver Edition to be fully functional. This was supplied when you purchased this software. If you are evaluating ScriptEase:WSE, a key is not required. A simple reminder will be entered in all the html documents you produce.

After this data has been entered, the SEWSE executable will be stamped with this new configuration information.

Un-Installing (Removing) ScriptEase:WebServer Edition
ScriptEase:WebServer Edition does not modify any existing system files. So to remove ScriptEase:WSE you only need to delete the files that the installer copied to your disk. These file will be the SEWSE*.* files that SESETUP copied to the BIN/Executable directory (c:\web\cgi-bin in our example) and the sample and data files contained in the paths specified in SESETUP (c:\web\sewse and c:\web\sewsedat in our example). All that is required to uninstall ScriptEase:WSE is to delete these executables and the directory trees created.

Testing Installation and Configuration
After installation verify that the main sample page was installed correctly by viewing it from any browser using the URL and names specified when running SESETUP. From any browser enter the URL for the SEWSE.HTML sample page. In our example this would be http://www.mysite.com/sewse/sewse.htm. If the main ScriptEase:WebServer Edition page (it has "ScriptEase" in large letters at the top) does not load, check the following:

• the server is running,
• you entered the correct URL

the URL matches the sample path defined in SESETUP.

If there was an error in SESETUP then delete then uninstall SE:WSE (see previous section) and run SESETUP again.

The sample page contains very many scripts to demonstrate the use of ScriptEase:WebServer Edition. The first script to try from your browser is the "Verify" script found just below the "Miscellaneous" header. "Verify" runs ScriptEase:WSE with no parameters. You should get text back looking like this:

     You have executed ScriptEase:WebServer Edition
     (SEWSE 4.0 Standard version) with no parameters.
     To learn about ScriptEase visit Nombas.

If this text does not show then verify that the URL entered is the one you specified for the BIN/Executable URL in SESETUP and the BIN/Executable path in SESETUP matches that URL.

The final script to test configuration is just below "Verify", and is "Show CGI Input server fields". Click on this URL to verify that all of the server parameters are returned and available to ScriptEase:WebServer Edition.

Now try all the examples. They're yours to modify, learn from, and to play with. Have fun.

Specific Installation Instructions
See the README.DOC file in your installation files for updated instructions on installing, configuring, and testing ScriptEase:WebServer Edition, and for instructions specific to operating systems and web servers. If you run into any problems, don't hesitate to call or email Nombas.