Revision management and the object life cycle
The object revision functionality is only available for the Transfer CFT and Messaging Enablers.
The purpose of the object revision function is to enable you to upgrade an object or a group of objects without interrupting execution of the objects on the Axway Server.
You may need to correct a minor problem in an object definition, or add certain parameters in order to take new requirements into account.
Rather than interrupting execution by removing the object (and all the objects that use it) from the Server, you can:
The new revision overwrites the previous version.
If the current instance of the object on the Server is in some way defective, you can replace it with a previous revision of the object, without interrupting execution.
Note: Revision management in Axway Composer is not the same as version management in the AccountingIntegrator product. Revision management does not include validity periods that determine when execution starts and stops.
When you send an object to Server, its status changes to Committed (or ToBeCommitted in the case of Transfer CFT). The object is no longer modifiable.
To modify the object, you must do one of the following:
For details, see Revision management and object dependencies.
Use the following tools to check each step of the object revision mechanism:
The current version of Axway Composer does not manage parallel versions of an object revision.
This means that you can only:
For details, see Revision management rules.
Because you cannot maintain parallel versions of an object, it is recommended that you duplicate objects if you want to create an entire new version of your configuration for a future date, for example next month or next year.
The revision mechanism is intended to be used for correcting minor problems or for making minor modifications to objects currently in runtime. To make major updates to an object, it is recommended that you make a copy of the object and then modify the copy.
Take the example of a Axway Integrator Integration-Task. After you test and check the objects used by the Integration-Task, you send them to Server. Each time you need to correct a given problem or make a minor modification to an object, you can create a new revision, modify the new revision and then send it back to Server.
However, to create a new Integration-Task that manages new Applications, it is better to copy the Integration-Task, its Map-Brokers and its Business-Documents into a different Folder. You only need to copy objects to which you intend to make major modifications. If it is only the Integration-Task that will change, then this is the only object that you copy.
Typically if you want to add a new CommAdapter or CommPoint to a Axway Server, you create a new revision of the Axway Server.