Host Software Installation for Progress

Overview

The following items must be installed and configured on your host server(s). You are also strongly encouraged to create a site-specific installation reference notebook in which you can note the directory locations, option choices and other information from each step of the installation process. Doing this can prove to be very useful in subsequent steps and for future reference. For quick checklists you can use to install on a Windows NT or Windows 2000 server, see the Installation Checklist documents.
 
• DNS name server (Unix systems only)
• Progress database server
• Web server that supports CGI, ISAPI or NSAPI interfaces
• Progress WebSpeed Transaction Server with CGI or ISAPI/NSAPI interface configuration

--OR--
• Progress V9 AppServer and the Jargon Tunnel Broker, plus a Progress client
• Scripts to manage database and middleware servers/brokers/agents
• Host Procedure Files

For Unix hosts, verify that Domain Name Service (DNS) is correctly installed. Most Unix web servers require DNS to be installed before you can install the web server.

Warning: do not include entries for network printers and similar devices in the DNS tables which map host names to IP addresses. Problems have been seen with entries for Lexmark Marknet printer adapters which somehow caused network failures when the Netscape FastTrack web server and Webspeed were subsequently installed.
 

V2 WebSpeed agents can connect to Version 6, 7 or 8 databases.
V3 WebSpeed agents can connect to Version 8 or 9 databases.
V9 AppServer servers can connect to Version 8 or 9 databases.

In general, the WebSpeed or AppServer version that you use can only connect to "older" database server versions, not newer ones, and may require the use of client networking (with the "-H", "-S" and "-N" startup options) if the versions of the two products being connected are not of the same "vintage". Please check with our sales team for specific configurations that are known to work, before ordering any Progress products.

If your Progress database is not installed on the same host as WebSpeed or AppServer, you must install the Client Networking option for Version 7 and higher versions.

For Version 6 databases, you must always use the host/service connection method, even if the database and WebSpeed are on the same system. There is also an undocumented "-Nv 12" parameter that must be used.

Example of "sports.pf" file for a Version 6 database connection:

-db sports
-H jargonsoft.com
-S sports_svc
-N tcp
-Nv 12

When using host/service connections, be sure to add the host and service entries to the appropriate system files.

• On Unix, these are usually "/etc/hosts" and "/etc/services".
• On Windows NT/2000 systems, they are also called "hosts" and "services" but are buried several levels deep in system subdirectories, usually "C:\winnt\system32\drivers\etc".

Be careful to select a service number that is not being used by any other application. This is the purpose of documenting all such service selections in the "services" file, to avoid collisions.

A Web server is required in order to be able to:

• use the Progress WebSpeed Transaction Server
• use the Progress AppServer with the Jargon Tunnel Broker
• use Jargon Reader to deploy your application
• provide online documentation via HTML files served from your host.

If using WebSpeed, or AppServer with the Jargon Tunnel Broker, you must install a Web server that supports any of the CGI, ISAPI or NSAPI interfaces. This will typically be on a Unix or Windows NT/2000 host system. On NT systems, you may use the IIS server included with the NT software. On Unix systems, you may use a purchased Web server or download the "apache" freeware server from the http://apache.org/ site.

Determine which interface you will use, if more than one is available. On Unix systems, CGI is normally used. On NT systems, ISAPI is normally used. NSAPI is also available on both Unix and NT with Netscape web servers.

Web servers will usually ask for several directory configuration options. Make a note of these as you will need them later:

1. Document root directory. This is the base directory under which HTML files, image files and Java files will be located by the web server. On Unix systems, this may default to "/html", but it can be any directory. On NT and Win2000 systems using IIS, the default value is "C:\inetpub\wwwroot".

2. Scripts root directory. For CGI interfaces on Unix systems, this often defaults to "/cgi-bin". For ISAPI interfaces on NT and Win2000 systems, the default value is "C:\inetpub\scripts".

Create a subdirectory called "temp" under the Document Root Directory.  On Unix systems, be sure that the name is all lowercase. On NT systems, it doesn't matter. This directory is where various Jargon Software programs will create temporary web pages that are used to display logs, reports etc. to clients on their web browser. On both unix and NT, make sure that this directory has read/write permissions for all users.

Install the Progress WebSpeed Transaction Server software on the same host as the web server if possible. This will allow you to use the "Quick install" option. If not, you must use the "Custom install" option.

When installing on Unix systems, be sure that scripts for existing Progress applications will not be affected if you choose to copy the WebSpeed startup scripts to "/usr/bin". If in doubt, just say "no".

If you install WebSpeed on a different system than the one running the Web server, you must also install the WebSpeed Messenger program for the appropriate operating system on the Web server system, so that the Web server can communicate correctly with WebSpeed. If the operating system of the host used for the Web server is different than that of the host used for WebSpeed, the appropriate Messenger may not be included with your WebSpeed software. However, you can download it from the Progress Software support site at: http://www.progress.com/support/downloads/p90b-ws30b.htm in the "Support - Downloads" section.

Create a working directory for each application that will be running on the host system(s). These directories will contain your 4GL programs and include files, and may also include the Jargon Writer, Jargon Replicator and Jargon Building Blocks source file subdirectories ("jsi/", "jrep/" and "jsx/").

If your 4GL programs will need to create or write to remote shared network directories on a Win2000 server, note that the WebSpeed broker should be configured using a DOMAIN/account with a valid userid and password. See Progress Knowledge Base Solution ID# P26491, Title: Error 98 with errno = 13 writing a file on a network resource using Webspeed.

For detailed installation instructions, refer to the Progress documentation. Installation steps vary depending on the version and operating system that you are using.
 

Configure the CGI script to use the correct pathnames for the Webspeed directory and for the "webspeed.cnf" configuration file for each application. Install these scripts in the appropriate directory for your specific Web server (this will vary). On many unix Web servers, this will be a "cgi" or "cgi-bin" subdirectory, under the web server's home directory. Set the appropriate execute permissions.

Configure the "webspeed.cnf" file for each application. See examples and comments within the webspeed.cnf file for detailed instructions. Install this in the working directory for its application (or as otherwise specified in the CGI script that was configured in the previous step). Also create the "logs/" subdirectory in the directory specified in the webspeed.cnf file for the error and session log files. These log files will be created automatically by WebSpeed upon startup, if the correct subdirectory exists and has the correct permissions for WebSpeed to write into it.
 

Use the service manager utilities provided with the ISAPI or NSAPI software to configure the WebSpeed broker and agent parameters. Consult the Progress WebSpeed installation guide for more information. If you have only one service broker for WebSpeed applications, you can make it the default, so that it does not have to be specified in the Jargon Software "system/preferences.ini" properties. On ISAPI, also determine whether the WebSpeed broker service will be started automatically each time the system is rebooted, or manually. Backup scheduling may affect this choice.

Install the Progress V9 AppServer software on one or more hosts. The "name server" must be on the same subnet as the AppServer(s), but can be on a different host. If you use the default installation rather than doing a custom install, all components will be installed on one host, using default UDP and TCP port numbers.

When installing on Unix systems, be sure that scripts for existing Progress applications will not be affected if you choose to copy the AppServer startup scripts to "/usr/bin". If in doubt, just say "no".

Create a working directory for each application that will be running on the host system(s). These directories will contain your 4GL programs and include files, and usually will also include the Jargon Writer and Replicator source file subdirectories ("jsi/" and "jrep/").

If your 4GL programs will need to create or write to remote shared network directories on a Win2000 server, note that the AppServer broker should be configured using a DOMAIN/account with a valid userid and password. See Progress Knowledge Base Solution ID# P26491, Title: Error 98 with errno = 13 writing a file on a network resource using Webspeed. (Also applies to AppServer).

For detailed installation instructions, refer to the Progress documentation. Installation steps vary depending on the version and operating system that you are using.

Install the tunnel broker software on the same host that is running the Web server, or you can install it on another host in the network if you wish to, for performance or security reasons.

For a unix host, extract the "tunnel.tar" archive.

For an NT or Win2000 host, unzip the "tunnel.zip" archive.

For either type of host, select a parent directory of your choice, and extract the archive under this parent directory, using the subdirectories in the archive. All files in the archive will be extracted into a "tunnel" subdirectory, with various files and subdirectories under that.

After extracting the archive, see the detailed installation instructions in the "tunnel/doc/readme.txt" file for further information and the latest release notes. A copy of these instructions is also available in the Jargon Tunnel Broker online docs. The "tunnel/doc" subdirectory also includes a Windows NT/2000 installation checklist, a debugging guide, and examples of ReaderX startup web pages that use the Tunnel Broker.
 

If you are using the V9 AppServer, all Progress programs (".p" files) should be precompiled to object (".r") files. This requires a Version 9 4GL, ProVision, or Provision Plus client license, or a V3 WebSpeed Workshop license, in order to run a Progress editor session so that you can compile and save all programs that will be run by the AppServer, including any programs that update the database.

After completing all client and host installation steps, you can compile and save your programs by starting a Progress editor session. First, enter the following statement and press GO (F1 or F2 or CTRL-X):

compile util/rdu3.p save.

This initial step will compile the RDU3 utility, so that you can now run it. You may find it simpler to use RDU3 (Remote Development Utility V3) for all other compiling tasks, rather than having to start a host editor session each time a compile is needed.

To use RDU3 to compile programs, see the Compiling Strategies document.

Scripts

Set up scripts (or services on NT) to start the database servers and WebSpeed or AppServer brokers and agents for each application, and make sure they have the correct execute permissions. Model scripts for Unix systems are included with the Jargon Software host software. These scripts may be copied and modified as needed. Place these scripts in the application's working directory, or in a directory that is in your "PATH".

You may also wish to include these scripts in your system's startup and shutdown command sequences, so they are started and stopped automatically when the system is brought up or shut down. Likewise, they may be included in your backup scripts, so that they are shut down before backup is run, and restarted after backup is completed (unless you are using online backup).

The Progress source files for Jargon Writer host procedures are included in "zip" and "tar" files in the "progress\nt" and "progress\unix" subdirectories within your Jargon Writer working directory.

For unix systems, copy the "jsi.tar", "util.tar" and "demos.tar" files (using the "binary" option in FTP) to the application working directory, then use "tar -xvf <tar_file_name>"  to uncompress each one.

For NT systems, copy the "jsi.zip", "util.zip" and "demos.zip" files to the application working directory and use pkunzip or WinZip to unzip them.

Make sure that the "jsi", "a5", "demo32" and "util" subdirectories are installed in a directory that is in the PROPATH of the Progress agent. The easiest approach is to install them in the application's working directory, as described above.

However, if you have multiple application working directories, you may wish to set up one common parent directory that contains jsi and util as subdirectories. If you do so, make sure that every application's PROPATH contains this common parent directory, in addition to the application's working directory.

Check that all users will have the appropriate read permissions. (There is no need to allow write permissions to these directories. They can be "read-only").

If you are using AppServer with the Jargon Tunnel Broker, also use any text editor to find the line near the beginning of the "jsi/jsi.ini" host file that reads

  &GLOBAL-DEFINE HostType "WS"

and change the "WS" to "AS", so that the include files in the jsi directory will use AppServer interface logic instead of WebSpeed interface logic.

For Additional Assistance

If you have questions or problems not covered by this document, see the additional assistance section in the installation instructions index.