Automatic Download Issues and Considerations

The UpgradeRuntimeTo64bit parameter in the [JadeAppServer] section of the JADE initialization file only on each application server, when set to true, causes a 32‑bit client running on a 64‑bit operating system to be upgraded to 64‑bit binaries.

The 32-bit version of presentation client binaries must be installed on the 64‑bit application server, in one of the following directory structures.

• <jade‑program‑data‑directory>/i686‑msoft‑win32‑ansi/download/

• <jade‑program‑data‑directory>/i686‑msoft‑win32‑unicode/download/

The 64-bit version of presentation client binaries must be installed on the 32‑bit application server, in one of the following directory structures.

• <jade‑program‑data‑directory>/x64‑msoft‑win64‑ansi/download/

• <jade‑program‑data‑directory>/x64‑msoft‑win64‑unicode/download/

The automatic download feature requires that the jade.exe and jaddinst executable program binaries and all libraries required by the jade.exe program running in thin client mode must be present in the binary directory on the application server.

The binary directory on the application server must have read access. The binary directory on each presentation client must allow read and write access to create the interlock files, create and update the values of the DownLoadVersion and PreDownLoadVersion parameters in the [JadeThinClient] section of the JADE initialization file on the presentation client, copy the older versions of the files from this directory, and allow the jaddinst program to copy files into the directory and overwrite the existing files.

Do not use the same binary directory to communicate with multiple application servers, as each application server may attempt to alternately upgrade the files in turn.

If the JADE initialization file on the presentation client is read-only, the download version cannot be updated. As a result, each time the presentation client initiates the application and the application server and presentation client download versions are different, they go through a file comparison phase that is not necessary, consuming more resources, and causing a longer initiation time.

When the JADE thin client downloads any files with an .ocx name type, an attempt is made to register these files to the Windows operating system. This registration process can be performed only under administration mode. The JADE thin client installer detects that an OCX file has to be installed and attempts to re‑run itself in administration mode so that the OCX file can be registered with the Windows operating system.

If the installer can be run in administration mode, the files downloaded are installed as normal and any OCX files are registered. If the client environment does not permit the operation of administration mode, the attempted re‑initiation fails and the download installation continues in non‑administration mode. This results in the OCX registration process failing and being reported to the user. This is a non‑fatal error, and use of the OCX will require manual intervention from an administrative user.