Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

The terms update and upgrade, in relation to client XTM servers, have different meanings in the XTM software environment, and their proper distinction allows for averting any unnecessary misunderstandings. Therefore, it is vital that you know what they refer to specifically.


Update

The update of the server consists in moving up a server to the most recent XTM package version within the same XTM version a your server is currently in.

The update is usually performed for the purpose of obtaining desirable fixes/improvements which were deployed onto that particular XTM version, but your server does not have them yet because the package version on their server is older than the package version in which a certain fix/improvement was implemented; hence the need for an update of the server.

For example, your server has XTM v.12.9 and the package from 21 February 2022:

But the fix was prepared and deployed on the newer version of this package; for example, the one coming from 1 April 2022:

In such a case, the update pattern looks as follows:

v.12.9 (old package) -> v.12.9 (new package)

The overall time reserved for the update process amounts to 2 hours.


Upgrade

The upgrade of the server consists in moving up a server to a completely new XTM version. The upgrade is usually to the newest XTM package version of that XTM version.

The upgrade is usually performed for the purpose of obtaining desirable fixes/improvements which were deployed onto that particular XTM version (and for some reason they were not retrofitted to the XTM version your server currently has) and also acquiring brand-new features that were devised and deployed specifically onto that version (new XTM features are not retrofitted to lower XTM versions by default).

For example, your server has XTM v.12.9:

But a given fix/improvement/feature was deployed onto a new XTM version - 13.0:

In such a case, the upgrade pattern looks as follows:

v.12.9 -> v.13.0

The overall time reserved for the upgrade process may vary depending on the version range between the current XTM version of the server and the XTM version the said server is to be upgraded to. The minimum time amounts to 3 hours.


Good to know!

Apart from providing the most recent packages, the XTM support team also performs a standard check-up of the most prominent XTM functionalities to ensure a given server’s overall operability. Furthermore, as long as it is possible, what is updated/upgraded in the first place is the TEST/UAT server (if you have one), so that you can verify if the delivered product meets your requirements/expectations in terms of usability and/or efficiency.

  • No labels