Upgrading of Thin Clients

[ConvertFromOldNGs]

by Michael >> Tue, 1 Aug 2006 1:56:47 GMT

Hi,

Hoping someone can point me in the right direction iwth what is going on here.

[ConvertFromOldNGs]

by Michael >> Tue, 1 Aug 2006 2:10:14 GMT

Sorry will try that again. Don't know what happened there.

I'm trying to update the Thin Client with a new version of Jade which is working, but the problem is coming when I try to upgrade non-Jade files.

In my Thin Client ini file I have DownLoadDirectory/2 and PreDownLoadDirectory/2 are blank. So looking at the documentation I would expect the files to download from the server to something along the lines of \bin\download1. However they end up in the root directory.

********** Thin Client download install started: 14:06:41 01\08\2006
Jade Binary directory=E:/Finesse/bin/
DownLoadVersion=1.9.0
DownLoadDirectory=E:/Finesse/download/
Post Install exe=jade.exe
Backup file: E:/Finesse/backup/ACA Finesse System.chm to directory E:/Finesse/backup/
Backup failed. Reason: The system cannot find the file specified.
Backup file: E:/Finesse/backup/ACAFinance.cnt to directory E:/Finesse/backup/
Backup failed. Reason: The system cannot find the file specified.
Backup file: E:/Finesse/backup/ACAFinance.GID to directory E:/Finesse/backup/
Backup failed. Reason: The system cannot find the file specified.
Backup file: E:/Finesse/backup/ACAFinance.hlp to directory E:/Finesse/backup/
Backup failed. Reason: The system cannot find the file specified.
Backup file: E:/Finesse/backup/cnldap.dll to directory E:/Finesse/backup/ Backup failed. Reason: The system cannot find the file specified.
Backup file: E:/Finesse/backup/karma.dll to directory E:/Finesse/backup/ Backup failed. Reason: The system cannot find the file specified.
Backup file: E:/Finesse/backup/nsldapssl32v30.dll to directory E:/Finesse/backup/
Backup failed. Reason: The system cannot find the file specified.
Install file: ACA Finesse System.chm in directory E:/Finesse/
Install file: ACAFinance.cnt in directory E:/Finesse/
Install file: ACAFinance.GID in directory E:/Finesse/
Install file: ACAFinance.hlp in directory E:/Finesse/
Install file: cnldap.dll in directory E:/Finesse/
Install file: karma.dll in directory E:/Finesse/
Install file: nsldapssl32v30.dll in directory E:/Finesse/
jade.exe successfully initiated.
Download Install completed

Can anyone point me in the correct direction?

Cheers

Michael

[ConvertFromOldNGs]

by Michael J. >> Tue, 1 Aug 2006 5:41:20 GMT

Michael,

Thin client downloads are controlled by the application server ini file.

I think the download directory on the thin client ini is only used as temporary directory during the install.

What do your App server Ini settings look like? if you post that section in here im sure someone can help you.

in general;

In the app server section there should be an entry like;

DownLoadDirectory = r:/production/thinclient/c_bin/download

That directory must be app server relative. That will define where the files come from. By default all the directories and files from that directory should should be copied into the root directory on your client (but keeping the same directory structure).

If you have the Jade documentation page 207-209 in the Jade administration guide covers it indepth.


Michael J.

[ConvertFromOldNGs]

by Michael >> Tue, 1 Aug 2006 21:14:25 GMT

Hi,

Thin client looks like this:

[JadeThinClient]
FormCacheFile=default
UseCacheFile=true
UseCompression=true
RPCEncryptionEnabled=false
RPCEncryptionHookDLL=Internal
TcpBlockSize=65535
MouseMoveTime=200
Trace=none
CacheEntryTimeout=30
RemovePreDownLoadFiles=false
AttemptReconnect=true
TraceDirectory=logs
TraceAppServer=false
ReconnectTimeout=40
AutomaticDownLoad=true
AskToDownload=true
AskToPreDownload=false
DownLoadVersion=1.9.0
DownLoadDirectory=e:\finesse\bin\download
PreDownLoadDirectory=
DownLoadDirectory2=

App Server looks like this:

[JadeAppServer]
ConnectionTimeout=0
EnableAppRestrictions=false
AllowSchemaAndApp1=<schema, application>
PictureCacheFile=default
WindowPos=7,0,1027,194
RPCEncryptionEnabled=false
RPCEncryptionHookDLL=Internal
KeepAliveTime=10
NodeName=jadapp-60779
NodeNameDescription=Jade AppServer 60779 (E:\FinesseLocalDev\system2nd) CacheEntryTimeout=30
RunAsService=false
AttemptReconnect=true
AutomaticDownLoad=true
AskToDownload=true
DownLoadVersion=1.9.0
DownLoadDescription=Jade 6.1.07 Update
PreDownLoadVersion=
PreDownLoadDescription=
DownLoadMaximum=10
DownLoadDirectory=
DownLoadDirectory2=
PreDownLoadDirectory=
PreDownLoadDirectory2=

[i686-msoft-win32-ansi]
DownLoadDirectory=E:\FinesseLocalDev\bin
FullJadeInstallDirectory=
PostInstallExe=

Additional info: The files we are having problems updating on the client are the ones associated with Card Schema and some of our help files. Setup for running is we are running a RAP and App Server. It is transfering the files to the client but only installs them in the root directory not the bin. The setup is the same as I used about 6 months about (which worked). The only difference is that the i686 section if it doesn't exists gets added and looking at the logs it uses this to find the directory it should be downloading the files from.

Michael

[ConvertFromOldNGs]

by Michael J >> Wed, 2 Aug 2006 1:58:56 GMT

Does the PC running this thin client have an e: or is just a coincedence that both the server and client PC have an e: ?

[ConvertFromOldNGs]

by Michael >> Wed, 2 Aug 2006 5:20:45 GMT

Running on the same machine but using different directories for the bins. Have the same problem when run on another pc.

[ConvertFromOldNGs]

by allistar >> Tue, 1 Aug 2006 23:30:23 GMT

I hope this isn't an inappropriate posting for this forum:

Using the "Connection Manager for Jade" software your bin directory will be kept in sync, and you get to decide exactly what files to copy down from a GUI. Another benefit is that it will automatically load balance thin clients across available application servers, and all client settings (schema, app, ini file etc) are all driven from the same server GUI - the client doesn't decided these things, the server does (which is, IMO, how it should be). Rolling out configuration changes (like a new app to run, ini file changes, introducing a new application server etc.) is a change done in one simple server side GUI. New client connections will start using those settings immediately.

It's currently being used in over 600 Jade sites. Contact me if you need further details.

Regards,
Allistar.