...
Release is updated with each build of PortalProtect. Release is updated automatically to ensure that all builds are unique.
Generally, all components must have the same version in order to be 100% sure of compatibility but Ceptor PortalProtect is in most cases backward compatible, in such a way that new components can communicate with older components. There will simply be functionality which is not available if the version numbers are mixed.
Ceptor is designed to run 24/7 meaning you can upgrade servers in a cluster one at a time, and you can use older Agent versions and mix them with newer, although these agents might possibly have limited functionality.
Example of a .version file.
# version file copyright=(c) 2017, Asseco Denmark A/S |
This file is found in the root of the Ceptor PortalProtect JAR files in the lib folder in the distribution.
...