Revision management and object dependencies

About revision management and object dependencies

Creating a revision of an object that uses other objects

Creating a revision of an object that is used by another object

Creating a revision of an object that is used by more than one object

About revision management and object dependencies

Axway Composer objects typically reuse other objects and exist in a hierarchy of object dependencies.

Because Composer objects are inter-dependent, the result of the Upgrade operation depends on where the object is positioned in the hierarchy.

For example, object A is an object that you can send to Server on an Axway Server. Object A uses object B, for example a Map-Broker that uses a Business-Document.

When you send object A to Server, object B is also automatically sent to Server on the same Axway Server. The status of both objects passes to Committed.

However, if you detect a problem in one of the objects, you create a new revision of that object.

Creating a new revision of an object that uses another object

Object A uses object B in the object hierarchy, but is not used by any other object.

If you create a new revision of object A, Composer:

• Only creates a new revision of object A
• Recreates the dependency link to object B[1] but does not create a new revision of object B
• Increments the revision tag of object A to [2]
• Sets the status of A[2] to Checked

The status of revision [1] of objects A and B is still Committed, as illustrated in the following diagram.

If you then send object A[2] to Server:

• It replaces the previous revision on the Server and its status is set to Committed
• Object A[1] is Archived
• Object A[2] uses object B[1]
• Object B [2] is still Committed

Creating a new revision of an object used by another object

Object B is used by object A in the hierarchy. When you send object A to Server, Composer also automatically sends object B to Server. Both objects have the status Committed.

If you detect a problem to be corrected in object B, create a new revision of object B. Composer:

• Creates a new revision: object B[2]
• Sets the status of B[2] to Checked
• Verifies the status of the parent object(s) of B. If the status of the parent object is:
• Committed, Composer creates a new revision of the parent object, for example A[2]
• Checked or ToBeChecked, Composer destroys the dependency link to B[1] and recreates the link to B[2]
• creates a BroadcastGroup, with the status Under Definition,for the objects B[2] and A[2]

If you start the BroadcastGroup that contains object A[2]:

• It replaces object A[1] on the Axway Server
• Object B[2] is automatically sent to Server and replaces object B[1] on the Axway Server
• Objects A[2] and B[2] are Committed
• Objects A[1] and B[1] are Archived

Example

In the following example, object A uses object B.

• A[2] and B[1] are on Axway Server 1
• A[3] and B[2] are on Axway Server 2
• A[1] and A[4] are no longer on a Server (status Archived)
• A[5] is modifiable (status Checked)

The following operations were performed to create this situation:

1. New revision of A[1] to create A[2].
2. A[2] replaces A[1] on the Server and A[1] is archived. Composer recreates the link between A[2] and B[1].
3. New revision of B[1] to create B[2].
4. A[2] uses B[1], so Composer automatically creates new revision of A[2]. New revision tag is A[3].
5. B[2] and A[3] sent to Axway Server 2.
6. New revision of A[3] to create A[4]. Composer recreates link from B[2] to A[4].
7. A[4] sent to Axway Server 2 and A[3] is archived.
8. New revision of A[4] to create A[5]. A[4] is still on the Server and A[5] is modifiable (Checked status).
9. Composer recreates new dependency link from A[5] to B[2].

Creating a new revision of an object used by many other objects

When you create a new revision of an object, Composer creates:

• A new revision of allCommitted objects that use this object
• A new link between the new revision and all Checked (or ToBeChecked)objects
• A BroadcastGroup for each Axway Server where the object was sent

In the following example, object A, D and C all use object B.

The following diagram illustrates what happens when you create a new revision of object B.

When you create a new revision of B[1], Composer:

• Also creates new revisions of the Committed objects - A and D
• Creates a new link between B[2] and the Checked object C[1]
• Deletes the link between C[1] and B[1]
• Creates a new link between A[2] and B[2]
• Creates a new link between D[2] and B[2]
• Creates a historical link between each new revision and the previous revision

Note: If A[1] and D[1] are on the same Axway Server, Composer also creates a BroadcastGroup for the objects B[2], C[1], A[2], D[2].

In such a scenario, the network of object dependencies can become increasingly complex. Because Composer must maintain the coherence of the inter-dependencies, it may be impossible to delete an object revision or send an object to Server. The BroadcastGroup helps maintain integrity of inter-dependent objects and avoid situations where the configuration is no longer coherent.

For details, see Revision management rules.