This topic describes an aspect of deployment: object revision management. The object revision functionality is only available for the Transfer CFT and Messaging Enablers.
You may find that you need to modify an Integration-Services object that is currently on a Server. If major modifications are required, remove the object from the Server. If, on the other hand, the required modifications are minor, you can upgrade the object.
For example, you may need to add a CommPoint, or service access point, to an Application. Rather than removing the object (and all objects that use it) from the run-time environment and interrupting processing, you can upgrade the object, modify the new revision version and then return it to the Server.
The new object revision replaces the previous object without interrupting execution.
In addition, the previous object revision is archived and is available via the History Browser. The History Browser maintains a trace of all previous object revisions, each with a unique revision name.
Via the Browser, you can:
For example, you may find that an object that is currently on a Server is in some way defective. From the History Browser, you can select a previous revision of the same object and send it back to Server: it overwrites the current object in the run-time environment and the current (defective) object is archived in the History Browser.
As well as the History Browser, Axway Composer provides a set of tools that accelerate and facilitate your work, as described in the next topic.