Windows Installation Checklist

Installation Checklist
For Windows NT/2000/2003

For Installation of:

Progress AppServer
Jargon Tunnel Broker

A. CONFIGURATION INFORMATION

1. Fill out the Installation Worksheet.

B: INSTALLATION STEPS

1. INSTALL PROGRESS PRODUCTS

Install the AppServer, NameServer, AdminServer and Java JRE.

Specify [AdminWorkDir] during install.

2. CREATE DIRECTORIES

Create the following directories:
[BrkrWorkDir]

[TunnelDir]

[JavaDir]

[WebRootDir]\temp (for RDU browser viewing)

[WebRootDir]\xml (for xml files)

3. INSTALL JAVA RUNTIME ENVIRONMENT (JRE)

If you do not already have it, download jre1.3 (or jre1.2) from the Sun's Java web site.

Run the jre installation program. Extract files into [JavaDir].

4. INSTALL JARGON TUNNEL BROKER.

Unzip tunnel.zip into [TunnelDir].

Refer to the Overview and Installation Instructions as necessary

Copy [TunnelDir]\tunnel\win32\scripts\jsihttp.dll to [WebScriptDir]

Copy [TunnelDir]\tunnel\win32\system32\jsihttp.ini to:

Edit jsihttp.ini (see Configuring the Jsihttp Script for Windows NT/2000/2003.)

Edit [TunnelDir]\tunnel\system\tunnel.ini (if necessary)

NOTE: be sure to set MaxAgents to a value no larger than the max AppServer users

For Windows 2003 servers, be sure you have configured IIS as discussed in the Installation Of The Cgi Or Isapi Script section of the Overview and Installation Instructions.

5. INSTALL JARGON HOST PROGRAMS

Unzip all zip files found in [WriterDir]\Progress\nt into [BrkrWorkDir] Modify HostType value in [BrkrWorkDir]\jsi\jsi.ini to "AS".

Copy "statusas.p" and "statusas.i" from tunnel\test to [BrkrWorkDir].

6. CONFIGURE DATABASES AND APPSERVER

Use Progress Explorer to configure the database server(s), if this has not yet been done.

Make sure databases start in multi-user mode (at least 1 server), with network startup params ("-S [SvcName] -N tcp").

The page writer processes (APW, AIW, BIW) are optional but are normally desirable for better performance in real installations.

Make sure the [SvcName] is defined in the services file:

The entry will look like:
"sports_svc 4001/tcp #port for Progress DB service sports_svc" Use Progress Explorer to connect admin server on localhost by right clicking localhost in tree, then click "Connect". Add a new AppServer broker by right-clicking AppServer in tree, then click "New". Configure the new AppServer broker by right-clicking it in the tree and click "Properties". Broker properties:

leave name as "asbroker1" for first broker, otherwise assign a new broker name

set Working Directory to [BrkrWorkDir]

set max agents to number of licensed AppServer users

set initial agents value to be <= max agents value

set mode to "StateReset"

Server properties:

add DB connection params to Server Startup Params with a "-pf <pf_filename>" option
create a ".pf" file with the DB connection parameters:
"-db [dbname] -H [HostName] -S [SvcName] -N tcp"
ex: create mydb.pf containing entry: "-db sports -H localhost -S sports_svc -N tcp"

IMPORTANT:
After completing all configuration changes, disconnect the Progress Explorer admin broker, then close Progress Explorer and restart it to make sure the changes take effect properly.

7. INSTALL JARGON READER FILES AND APPLICATIONS

Consult the installation instructions provided with your Jargon Reader install file.

8. START BROKERS AND SERVERS

Start web server (IIS or PWS) if it is not running.

Use Progress Explorer to start database(s), then check status.

Use Progress Explorer to start NameServer, then check status.

Use Progress Explorer to start AppServer broker, then check status.

Note: All of these could be set to autostart at boot time.

From Windows Explorer or from a DOS command prompt window:

9. TESTING

Check Status from Test Script.
Try the test.bat script (may have to modify for your application program/database). The output will appear in one long (messy-looking) line, because it is formatted for use with Jargon Reader. However, if you get back a long response that includes Propath directory entries, etc then it is working.
Check Status from Web Browser.
Try running statusas.p from a web browser. From a client PC with access to the Web Server host, open Internet Explorer or Netscape Navigator and enter a URL like:
http://999.999.999.999/scripts/jsihttp.dll/Broker=XXX/statusas.p?ProcName=GetStatus
Substitute the IP address of the machine that the web server is running on for the "999.999.999.999" and substitute the desired tunnel broker name for "XXX". You can use either a symbolic or numeric IP address, as long as the symbolic name is getting converted to an IP address correctly by DNS or other means. You can test this by trying to "ping" the symbolic address. The tunnel broker name must be one of those specified in your "jsihttp.ini" file.
Test Your Application.
From a client device, enter the URL of an application's startup file
Examples:
"http://www.abc.com/login.html" for a V2 desktop app
"http://www.abc.com/login.ini" for a V3 WPDA app
If it works, you’re done. Go celebrate.
Otherwise find out what is wrong and fix it.

10. DEBUGGING:

See the "Debugging Guide" for tips and techniques on testing and debugging any problems..