Using the History Browser
About
the History Browser
Using
the History Browser
Viewing
Axway Servers for a given object revision
Viewing
BroadcastGroups for a given object revision
About the History Browser
Via the History Browser,
you can trace the object development history in Composer and view
the list of all revisions of an object. From the Browser, you can send
an object revision to
Server
for execution.
Composer adds objects to the History
Browser in two ways:
- Explicitly: when
you upgrade an object that is currently on a Server, Composer displays
in the Browser both the latest revision (status Checked)
and the previous revision (status Committed,
or Archived). The left
pane of the user interface only displays the most recent object revision.
- Implicitly: when
you send a new object revision to Server, it overwrites the previous revision
of the same object if the status is ToBeCommitted.
If the previous revision has the status Committed,
Composer overwrites it when you commit the new revision. The previous
object revision is not deleted: it is archived and is displayed in the
History Browser with the status
Archived.
Using the History Browser
How to display the History Browser
The History Browser is available
from both the Topography workbench and the Integration-Services workbench.
To display the History Browser,
right-click the object and select History
Browser from the contextual menu.
The Browser displays the list of revisions of the selected object. For
each revision, the Browser displays:
- The revision name
(by default, a number that increments for each new revision)
- The object status
- The modification
date and time
- The name of the
user who performed the modification
The following table describes the actions you can perform from the History Browser.
|
|
Display the properties window for the selected object revision.
|
|
|
Delete the selected object.
|
|
|
Display the object dependencies for the selected object
revision.
|
|
|
Remove the selected object from the run-time environment
and make it accessible for modification in Composer.
|
|
|
Send to Server the selected object and all
itschild objects, even
if the child objects are already on a Server in association with a different
parent object.
Use this command if you need to initialize your run-time
environment and ensure that all the required objects are sent to Server
on the Axway Server.
|
|
|
Send the selected object to Server. This action only sends
objects that are not already on a Server. That is, objects that have not
already been sent to Server in association with another parent object.
|
|
|
Transfer CFT only
Commit the selected object. This option is only available
for objects that have the status ToBeCommitted.
|
|
|
Refresh the display.
|
Viewing the Axway Servers where
the object revision is in execution
To display the list of Axway Servers where a given object revision
has been sent, select the object revision in the upper pane of the Browser.
The Axway Server tab in
the lower pane of the Browser displays the Axway Server(s) where the
selected object revision is Committed
(or ToBeCommitted). If
the status of the selected object is Checked
or ToBeChecked, the Axway Server tab remains empty.
Viewing the BroadcastGroup(s) for a given object
revision
A BroadcastGroup is the set of objects linked to a given object. When
you perform any broadcast operation on an object (Send to Server, Remove
from Server...), Composer performs the operation on all the linked objects
in the BroadcastGroup.
To display the BroadcastGroup(s) for a given object revision, select
the object revision in the upper pane of the Browser.
In the left pane of the BroadcastGroup(s)
tab, Composer displays the list of BroadcastGroups created for
the selected object revision. If you send an object revision to more than
one Server, the BroadcastGroup tab displays a BroadcastGroup for each
Axway Server to which you send the object.
Select a BroadcastGroup in the list. The right
pane displays:
- TheAxway Server associated with the selected BroadcastGroup.
- The list of objects
that belong to the BroadcastGroup.