gJax 3.1.1
Functional Web Applications

 

Installation
Please review the whole of this document before proceeding.

If your software is supplied on CD, copy the files to a directory on the server where you plan to install gJax.   If it is supplied as a zip file, copy the zip file to the directory.

  1. The following directories are recommended or suggested for installation:

    Operating System

    Directory

    Windows

    C:\Program Files\George James Software\gjax (recommended)
      

    UNIX /Linux

    /usr/gjax (suggested)
      

    OpenVMS

    disk:[GJAX] (suggested)
     

     

  2. If the software was supplied as a zip file unzip it using the appropriate method for your operating system.  

    Operating System

    Unzip method

    Windows

    Use WinZip, 7-Zip, pkunzip or similar software
       

    UNIX /Linux

    $ unzip -a gjax_n.n.n.zip
       

    OpenVMS

    $ UNZIP GJAX_n.n.n.ZIP /BINARY=AUTO /TEXT=AUTO
    (The Info-Zip version of UNZIP.EXE is available from
    ftp://ftp.info-zip.org/pub/infozip/VMS/)
       

     

  3. Continue the configuration process by following the instructions in the gJax Installation Procedure.  The installation procedure is called gjaxInstallationProcedure.pdf and is in the Documentation sub-directory where you have installed the gJax software. You may be able to click here to open it.

Below are notes concerning known bugs, limitations and issues related to the use of gJax on various platforms.


Internet Explorer
gJax's web-based client interface is designed to operate with Microsoft's Internet Explorer Version 5.0 and later.  It will not work with Netscape Navigator, Mozilla, Opera or any other browser. 

We have observed a problem that results in an Access Violation when gJax is used with some early versions of IE 5.0 (notably version 5.00.2314.1003).  We recommend that you use IE 5.01 SP1 or later.


MSXML
gJax requires that Internet Explorer must have version 3 of Microsoft's XML Parser (MSXML) installed in Replace Mode.  Earlier versions of IE 5 shipped with MSXML Version 2 which contained a non-standard implementation of XSLT.  Furthermore version 3.0 can be installed either in alongside mode or replace mode. 

You can find out what version of MSXML you have installed and in what mode using Chris Bayes MSXML sniffer, which can be found here: http://www.bayes.co.uk/xml/index.xml?/xml/utils/msxml_sniffer.htm

You can download and install Microsoft XML Parser 3.0 SP4 here: http://msdn.microsoft.com/XML/XMLDownloads/default.aspx.  We have not yet tested with Microsoft XML Core Services (MSXML) 4.0  and so do not recommend that you use this version at this time.


CSP or WebLink or serverLink
gJax can be used either with Caché CSP or WebLink or serverLink to provide web server connectivity.  On Caché systems we recommend the use of CSP or WebLink.  WebLink is an optional component of Caché and is not installed automatically.

Notes:

  1. Using the WebLink System management pages , the WebLink Maximum_String_Length parameter should be set to 32000 for the server used by gJax (normally named gjax).
  2. If are using IIS as your web server and you don't wish to place a copy of mgwms32.dll in the gjax directory, then the IIS application for your gjax virtual root can be configured to script map .dll requests to mgwms32.dll in your preferred location (eg c:\cache\weblink\i386\mgwms32.dll).

Security
If you are using IIS and your gJax clients are running on a private network, then it is recommended that you enable integrated authentication and disable anonymous access within IIS for the gjax virtual directory.  gJax will automatically detect that the user is authenticated and will not take the user through gJax's own connection procedure. 

If the user is not known to gJax they will not be permitted to connect to the server.

In the event that a system manager need to connect as another gJax user then a Connect As function is provided to enabled a suitably privileged and authenticated user to connect as a different user.  Use of this capability is logged in the gJax session log and if required this functionality can be disabled for all users.


GT.M Installation
The gJax installation procedure expects the GTMROUTINES environment variable to have the current working directory (usually expressed as a period) as the first item in its search list (eg GTMROUTINES=". /usr/local/gtm").  It also assumes that the gjax directory will be the current working directory when gJax^%vcins is run.

If this is not the case for your environment we reccommend that you set the GTMROUTINES environment variable to include the current working directory temporarily, and make the gjax directory the current working directory before running gJax^%vcins.  For example:

# GTMROUTINES= ". $gtm_dist"; export GTMROUTINES

# cd /usr/gjax

# $gtm

gtm>d gJax^%vcins


Copyright 1999,2006 George James Software
http://www.georgejames.com