JADE 6.1: System File Default Location and Discontinuation o
Posted: Fri Aug 07, 2009 12:54 pm
by dcooper@jade.co.nz >> Mon, 3 Oct 2005 4:10:06 GMT
In current versions of JADE, the default location of system files (ie: _sys*.dat files) is the database path (commonly known as the "system" directory).
From JADE 6.1, the default location of system files will be changed to:
- The installation directory (commonly known as the "bin" directory) for Windows.
- $JADEHOME/runtime for Linux.
From JADE 6.1, the file extension of system files will be changed from ".dat" to ".bin".
Customers can always relocate the system files using the [PersistentDb] SystemFileDirectory parameter in the JADE INI file. This can be an absolute pathname or a relative pathname. A relative pathname is relative to the JADEHOME directory. On Windows, JADEHOME is the directory immediately above the installation directory. On Linux, it is the value of the $JADEHOME environment variable.
To continue using the default JADE 6.0 system file location, simply add the following in the [PersistentDb] section of the JADE INI file:
SystemFileDirectory=system
Customers not using the default JADE 6.0 location who want to continue using their current location simply need to set the SystemFileDirectory parameter to the absolute pathname of their system files.
This change provides several benefits:
1. It will make it easier for customers to ensure that versions of JADE system files do not diverge from dependent binary files. When JADE starts up, it will check that all system files are of the same version and that they match the correct binary file version.
2. Easier system management because dependent binary files and system files are co-located, enabling them to be backed up, restored and managed together.
3. Smaller database backups as system files will not be included. The system files need to be backed up only as frequently as the binary files.
4. Easier and more reliable installation of JADE updates. From JADE 6.1, JADE updates will be supplied as a new set of system files, rather than as a set of schema files that must then be loaded. While the set of system files will be larger than schema file updates, a compressed archive of the system files is only 18MB (approximately).
From JADE 6.1, there will be only one version of the system files. The current deployment-only version (with the JADE Development Environment removed) will be discontinued. Customers wanting to prevent the JADE Development Environment from being run against a system can do so by applying a license key with no Developer Licenses. To later enable the JADE Development Environment, simply apply a key with one or more Developer Licenses. Customers wanting to prevent the JADE Development Environment from being run even with Developer Licenses can do so by not supplying the _jadeapp.bin and _jadedef.bin files with their system.
Regards,
The JADE Team.
In current versions of JADE, the default location of system files (ie: _sys*.dat files) is the database path (commonly known as the "system" directory).
From JADE 6.1, the default location of system files will be changed to:
- The installation directory (commonly known as the "bin" directory) for Windows.
- $JADEHOME/runtime for Linux.
From JADE 6.1, the file extension of system files will be changed from ".dat" to ".bin".
Customers can always relocate the system files using the [PersistentDb] SystemFileDirectory parameter in the JADE INI file. This can be an absolute pathname or a relative pathname. A relative pathname is relative to the JADEHOME directory. On Windows, JADEHOME is the directory immediately above the installation directory. On Linux, it is the value of the $JADEHOME environment variable.
To continue using the default JADE 6.0 system file location, simply add the following in the [PersistentDb] section of the JADE INI file:
SystemFileDirectory=system
Customers not using the default JADE 6.0 location who want to continue using their current location simply need to set the SystemFileDirectory parameter to the absolute pathname of their system files.
This change provides several benefits:
1. It will make it easier for customers to ensure that versions of JADE system files do not diverge from dependent binary files. When JADE starts up, it will check that all system files are of the same version and that they match the correct binary file version.
2. Easier system management because dependent binary files and system files are co-located, enabling them to be backed up, restored and managed together.
3. Smaller database backups as system files will not be included. The system files need to be backed up only as frequently as the binary files.
4. Easier and more reliable installation of JADE updates. From JADE 6.1, JADE updates will be supplied as a new set of system files, rather than as a set of schema files that must then be loaded. While the set of system files will be larger than schema file updates, a compressed archive of the system files is only 18MB (approximately).
From JADE 6.1, there will be only one version of the system files. The current deployment-only version (with the JADE Development Environment removed) will be discontinued. Customers wanting to prevent the JADE Development Environment from being run against a system can do so by applying a license key with no Developer Licenses. To later enable the JADE Development Environment, simply apply a key with one or more Developer Licenses. Customers wanting to prevent the JADE Development Environment from being run even with Developer Licenses can do so by not supplying the _jadeapp.bin and _jadedef.bin files with their system.
Regards,
The JADE Team.