8. Object life cycle

As you create, modify and execute objects in Axway Composer, they pass through a life cycle of statuses that determine what you can do with the object and the objects linked to it. This topic describes that cycle.

Object statuses

The life cycle is a series of phases that describe the development of an object, from initial creation to completion. Each phase in the life cycle is associated with a status setting. The statuses not only allow you to track the progress of an object, they also allow you to validate the definition of the object. In particular, the Check function performs sophisticated checking on objects. If information is missing or incorrect, the software itself can usually warn you of the problem before it becomes a problem.

	Status	Details
Modifiable	ToBeChecked	This is the initial status of all objects. The object definition is not yet complete. When you modify objects that were previously Checked, their status changes to ToBeChecked until you check them again.
Modifiable	Checked	The definition of the object is complete and its properties are valid. Any objects that this object uses are also checked at the same time.
Non-modifiable	ReadyToSend	The object definition is already Checked and is ready to send to Server. Objects with this status are non-modifiable, but are not yet on Server.
	BroadcastInProgress	An object has the status BroadcastInProgress when you have sent it to Server, but it is not yet available in the runtime environment. The Send to Server operation on the object is in progress.
	ToBeCommitted	Axway Transfer CFT only An object has the status ToBeCommitted when you have sent it to Server on at least one Axway Server, but have not yet committed the object.
	PartiallyCommitted	A Channel object has the status PartiallyCommitted when the Commit operation was successful on one or more Axway Servers, but not on all of them. Optionally, you can force the broadcast via the Broadcast Browser.
	Committed	When an object is in execution in at least one run-time environment, it takes the status Committed.
	Archived	An object is Archived when it was previously on Server, but has been overwritten by a new revision version of the same object. Use the History Browserto view previous versions of an object.

Object dependencies

When you define or import an object, it is stored in the metadata repository and is available for reuse by other objects. To maintain consistency and coherence in this interlinked network of objects, the objects are arranged in a specific hierarchy. Objects are said to use objects that are below them in the object hierarchy.

Because objects use other objects, their object statuses are also dependent on each other. For example, if you modify an Application, its status is reset to ToBeChecked. Any Channels that use this Application are no longer valid and their status is also reset to ToBeChecked.

To help you manage the interlinked network of objects, the software provides the Object Dependencies Browser that displays the object dependencies for a selected object.

When an object has the status Checked or ReadyToSend, you can send the configuration to one or more Axway Servers, as described in the next topic.