Overview

The following files must be installed on your host so that they can be "served" from the host when Jargon Reader is started from a PalmOS-based handheld device or PocketPC handheld device.

1. text "ini" files that specify the startup parameters for each application procedure
   
2. your "xml" procedure files
3. compressed versions of your "xml" procedure files in ".gz" format (yourfile.xml.gz) (Palm only)
4. any image files used by your application
5. any online documentation files used by your application

Install these files in subdirectories under the document root directory for your specific Web server (this will vary). On some unix Web servers, the document root directory may be the "/html" directory. On Windows NT/2000 systems, it is usually "C:\inetpub\wwwroot".

For convenience, you may find it simplest to create a subdirectory structure similar to that used for client directories. For example, if the document root directory is "C:\inetpub\wwwroot" (on a WinNT/2000 server), you might install an Order Entry system using a structure like this:

C:\Inetpub\wwwroot\xml\oe\*.ini
C:\Inetpub\wwwroot\xml\oe\*.xml.gz
C:\Inetpub\wwwroot\images\oe\*.gif
C:\Inetpub\wwwroot\doc\*.htm

Configuring INI files

Modify the parameter values in your startup "ini" files to correctly point to the locations you have selected above. Remember that the document root directory portion (such as "inetpub/wwwroot") is omitted).

There are four (4) required parameters in a startup "ini" file and one optional parameter used by Jargon Reader. In addition, you may add other parameters for your application-specific needs.
 

AppRootDir	The search path for xml files. Separate multiple entries with semicolons.
AppName	The startup xml filename
HostURL	The host URL (symbolic name or numeric IP address) of the web server
Script	The middleware script name and parameter(s)
BoldLabels	An optional parameter that instructs Jargon Reader to display all labels and checkbox captions in boldface if the value is "true". If the parameter is missing or "false", a regular font is used (non-bold).


For example, if your server domain name is "www.abc.com", and you are using WebSpeed with the default service name of "wsbroker1" on a WinNT system, then the "login.ini"  file for the above example would look something like this:

AppRootDir=http://www.abc.com/xml/oe
AppName=login
HostURL=http://www.abc.com
Script=scripts/wsisa.dll/WService=wsbroker1
BoldLabels=true

Compressing XML Files

To create the compressed version of the xml file, run the "jsicomp.exe" procedure that is included with the Jargon Reader installation file, using the xml filename as a parameter. Run it from a command line prompt in the directory that contains the xml file. For example, from a command prompt, type:

jsicomp login.xml

to create the "login.xml.gz" file for the above login example. Then copy this file to the web server directory as shown above.

This step is required when using Jargon Reader for Palm OS, and is optional for other Jargon Reader versions.

These files are modified one-way compressed gzip files that provide faster downloads and also a degree of security by not disclosing source code in cleartext mode.

Online Documentation

Similarly, you may wish to install all online documentation for your application as HTML files and (perhaps) image files that are accessed via your Web server, rather than deploying the document files to each client system. This reduces ongoing maintenance costs and makes updated documentation instantly available to all users.

/html/doc/oe/*.html
/html/doc/oe/*.gif
/html/doc/oe/*.jpg

Troubleshooting

Problem: Can't download "ini" files from server

Solutions:

1. For IIS4/5 on Windows NT/2000, the problem may be due to a Windows feature called "URLScan." This is an optional Microsoft tool (part of the "IIS Lockdown" downloadable tool), that enables IIS to allow or deny access to various file types. If you have URLScan installed, edit this file:
   c:\winnt\system32\inetsrv\urlscan\urlscan.ini
   and if access is denied for ".ini" files, comment out the line, save and reboot.
    
2. For Windows 2003 server, which installs with many options shut off by default (for security purposes), you may also have to do these steps, using the IIS Manager.
   • Select the web server node
   • Click "Properties"
   • Select "Mime Types"
   • Add a new MIME type to serve files with the extension ".ini" (for V3 apps).
   • Extension: ".ini"
   • MIME Type: "text/plain"

For Additional Assistance