Shared Jade Executables Folder

[ConvertFromOldNGs]

by Mike May >> Tue, 18 Oct 2005 10:56:24 GMT

I have umpteen Jade databases on a server, each running a DB server and an app server from its own DB-specific folder. This is, of course, consuming many bigabytes of memory. Before I start experimenting for myself, does anyone know for certain whether or not I can run the DB and app servers for several databases from a common shared set of Jade executables? ie, have jadrap.exe, jadapp.exe and jade.exe, plus all the DLL's, living in a single folder on my server?

[ConvertFromOldNGs]

by Brendan >> Tue, 18 Oct 2005 12:55:06 GMT

Hi Mike,
Yes you can.

You can also share the system database files as well (the ones which start _sys*.dat (and _jade*.dat if there is a dev environment included in the licence key)). See the SystemFileDirectory setting in the [PersistentDb] section. In 6.1 these _sys*.dat and _jade*.dat files will be moving to the bin directory to join the exe and dll files there.

The only thing you need to be careful about is when you do an upgrade of JADE (eg. 6.0.22 to 6.0.23 or (more tricky) 6.0 to 6.1). If you do the upgrade on only one of the environments, the others will have a mixture of levels of .dat files and the _control.dat file for these other environments will have the wrong timestamps for the readonly system .dat files. A reset timestamps may be enough to fix this but sometimes an upgrade may involve user .dat files being modified. This can happen in a major release upgrade which is why this may be more tricky.

I'm sure the whole process of upgrading when sharing exe and .dat files could be scripted. Perhaps someone has already had a crack at this?

Brendan