Redbex Reference Manual

Zoom Window Out
Larger Text | Smaller Text
Hide Page Header
Show Expanding Text
Printable Version
Save Permalink URL

Navigation: Application Server > Administration

Versioning

Over time the Application Server will be deployed in different versions, new features might be added, bugs removed etc. To distinguish between different versions of the Application Server each version has a unique version number. Version numbers consist of four components: major, minor, build, and revision. All components are integers greater than or equal to 0. The format of the version number is as follows:

The components are used by convention as follows:

•Major: Application Servers with different major versions are not interchangeable. A higher version number indicates a major rewrite of a product or great enhancements in functionality, where backward compatibility cannot be assumed. If the major version number changes a new license is necessary. A change in the major version number indicates a change in the Web Services API, therefore the client (e.g. the Smart Client) software has to be updated to be compatible with the new Application Server version.

•Minor: If the major version number on two Application Server versions are the same, but the minor version number is different, this indicates significant enhancements. A change in the minor version number indicates a change in the Web Services API, therefore the client (e.g. the Smart Client) software has to be updated to be compatible with the new Application Server version.

•Build: A difference in build number indicates a new version with no significant new features implemented, but a few small improvements and bug fixes. If the Application Server's build number changes clients (e.g. the Smart Client) do not have to be updated.

•Revision: A difference in revision number indicates a new version with small changes e.g. bug fixes. If the Application Server's revision number changes clients (e.g. the Smart Client) do not have to be updated.

Checking the Application Server Database version

When the Redbex Application Server starts up and connects to the Application Server Database it will read out the version of the Application Server Database and decide if the current Application Server supports that database version. This is done by comparing the major and minor component of the database version number to a compatibility version number that is hard coded within the Application Server. In other words all versions of the Application Server database that have a major and minor version number that equals the major and minor compatibility version number hard coded within the Application Server are compatible with that version of the Application Server.

Example: If the Database Version number is 3.4.5.2 and the hard coded compatibility version number in is 3.4.0.0 the Application Server can use that database. If the compatibility version number would be 3.5.0.0 or 2.1.0.0 the Application Server cannot use that database.

The database compatibility version number is logged on application server startup and is also reported by the server information service.