Committing a new object revision
When you commit an object, it is taken into account in the specified run-time environment.
You can track the process of a commit operation in the Broadcast Browser. For details, see Using the Broadcast Browser.
Note: This operation is only available for Axway Transfer CFT.
You can only commit objects that have the status ToBeCommitted. If the object does not have this status, you must first use the command Send to Server.
To commit an object:
- The object
- All objects that the object uses
When an object is on a Server or Archived, you can create a new revision of the object in order to modify the object definition without interrupting execution. When you send the new revision back to Server and commit it, the new object revision overwrites the previous revision on the Axway Server and execution continues uninterrupted.
Note: You can only commit the most recent revision of an object.
For details, see Creating a new object revision and Using the History Browser.
If you are using the Transfer CFT product, a Channel always connects two Transfer CFT servers. The Channel must have the status ToBeCommitted on both servers before you can commit it.
Both Channel endpoints must be ToBeCommitted before you can commit the Channel. When you commit the Channel, its status passes to Committed.
However, if the commit operation is only successful on one end of the Channel and not the other, Composer:
If a Channel has the status PartiallyCommitted, the configuration of the two Transfer CFT servers is incompatible and communication over the Channel is not possible. Check the configuration of the Transfer CFT where the operation failed and make sure there are no network problems. You must then re-commit the Channel on the relevant Transfer CFT.