General Checklist for Installation
on Windows NT/2000/2003

Overview
This document provides a quick checklist for installing Progress Software's Webspeed or AppServer middleware products with Jargon Software products on a Windows NT, Windows 2000 or Windows 2003 host.

This checklist uses the following names in examples. Substitute your own specific host, service and database names where applicable.

"nthost"  - host name for the Windows NT system
"host2"   - host name for server that has the Progress database(s). (Could be same as nthost)
"mydb"   - database name on host2
"mysvc"  - service name (mapped to a port number) for mydb access

1. Install the Webspeed or AppServer CD on nthost in the default directory (usually under C:\Program Files).

• standard install
• allow "ALL" users to access
• "Yes" to virtual directories
• set default working directory to C:\Webspeed\Wrk or C:\Progress\Wrk (for log files)
• set specific working directories for each Webspeed or Appserver broker (for your application)

2. Use Progress Explorer to add and configure Webspeed or AppServer.

Note: You can also use a text editor to directly edit the "ubroker.properties" file, if necessary. The AppServer and NameServer properties file (ubroker.properties) stores all component configurations managed by the PROGRESS Explorer administration framework.

For AppServer configurations, these components include the AppServer and the NameServer. There is one copy of this file for each PROGRESS installation. So, if you install the NameServer on a separate machine, it has its own copy of the ubroker.properties file.

The AdminServer reads and updates this file according to your instructions using the PROGRESS Explorer and management utilities. In order for the AdminServer to access it, this file must reside in the properties subdirectory of the PROGRESS installation directory. For general information on the content of the ubroker.properties and how to manage it, see the PROGRESS System Administration Guide.

unique broker name

set as default service

starting, threshold and maximum number of WebSpeed agents or AppServer servers, etc.

host & agent port numbers (check services file for unused ones)

ensure that "-weblogerror" is in the AgentParams for WebSpeed

add "-pf mydb.pf" to AgentParams for database connection parameters (see step 3)

log file names/directory locations

To set up a connection to mydb on host2:

• create mydb.pf on nthost in your working directory with contents like:
"-db mydb -H host2 -S mysvc -N tcp"
• on nthost, in the C:\Winnt\system32\drivers\etc directory:

add "host2" entry to HOSTS file

add "mysvc" entry to SERVICES file (use a unique port#)

• on host2, add the same entries to the hosts and services files on that system (unix: /etc/hosts and /etc/services)

3. If using AppServer, install the Jargon Tunnel Broker on nthost.

• See the Jargon Tunnel Broker Installation Instructions.

4. Install the "jsi/", "jrep/", "util/" and <application dir> host programs on nthost under your working directory:

• edit jsi\jsi.ini and set HostType to "WS" (Webspeed) or "AS" (Appserver)
• also in jsi.ini, set the UseBldBlks (Building Blocks) option to TRUE or FALSE as appropriate
• test compile all programs (see the Compiling Strategies document)

5. Install Jargon ReaderX (or Jargon Reader) and any online docs on server:

    5.1  Jargon ReaderX files (most common deployment option)

• Install the Jargon ReaderX "cab" and "jar" files on nthost in C:\InetPub\wwwroot\jrx (file names will look like: "readerx-1-0-0-56.cab" and "readerx-1-0-0-56.jar")

• Install jsi.jar on nthost in C:\InetPub\wwwroot\lib
• Install init.dtd, jargonapp.dtd and readerinit.xml on nthost in C:\InetPub\wwwroot\system

• Install apps (*.xml) in C:\InetPub\wwwroot\xml
• Install image files in C:\InetPub\wwwroot\images

• Install html files & online docs in C:\InetPub\wwwroot\doc

6. OPTIONAL: Only if deploying with Jargon Reader and installing the entire application on client PC's (not typical).

Install the Java JRE and the standard Jargon Reader directories and files and your own application files on ONE client PC under C:\Jargonsoft. If you wish, you can put your xml and image files on a network drive that can be accessed from all clients, or you can serve the xml and image files from the nt host by putting them under C:\InetPub\wwwroot as in step 5 above, and changing the "ini" to use "remote" instead of "local" access.

• xml/ - your app files (*.xml)
• images/ - your image files and standard image files
• lib/ - standard jar files
• system/ - standard dtd/xml files and *.ini files for your app startups

7. Check for the correct parameters in all startup HTML pages and config files:

• HTML files for Jargon ReaderX apps or for Jargon Reader served applets
• system/*.ini files on clients (Jargon Reader client deployment only)

8. Test your app thoroughly on one client PC, fix any problems
 

9. OPTIONAL: Only if deploying with Jargon Reader and installing the entire application on client PC's (not typical).
 

• Create a zip file of C:\Jargonsoft contents, using pathnames, and copy to a server so you can download/unzip it on each client PC.

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