Where to find objects in relation to Composer workbenches
Possible operations on objects
Tools for working faster with objects
Each Composer object describes a set of parameters and represents a step, or element, in the processing chain. Each "step" in the chain depends on and is linked to the step before and the step after. However, each step can also be defined and processed separately. Each separate element is represented in Composer using a metadata object.
For example, when you define a file exchange process between a source site and a target site, the host machine for the source software constitutes an object (a Host). The network used to communicate is another object (a CommNetwork). The software and the protocol used for the transfer constitute another object (a Axway Server and its sub-object, a CommAdapter), and so on.
In the life cycle of an object, Composer assigns a sequence of statuses to the object. These statuses allow you to monitor the progress of objects from creation to completion.
The set of objects that you can define and work with depends on:
The Administration workbench comprises a set of objects used to define user rights and access to WorkFolders. The Administration workbench comprises the following objects:
The objects that you define in the Topography workbench are static objects that correspond to the network infrastructure layer of the software. The Topography objects define the run-time environment where you execute your configuration. That is, the configuration of the Axway Server (AccountingIntegrator, Transfer CFT, Integrator, and so on), the machine on which the product runs, and the network used to communicate.
Typically, after you define and check these objects, you do not often modify them. Topography objects are not contained in Folders. After you define Topography objects, they are available for use in the Integration-Services workbench in read only mode.
Topography objects comprise the following:
The objects that you define in the Integration-Services workbench correspond to the software infrastructure layer. Typically, after you define these objects, you will modify them often. Integration-Services objects are stored in WorkFolders. You only have access to objects stored in authorized Workfolders.
Integration-Services objects comprise the following:
When an object is defined and stored in the repository, any Composer user with the required user rights can:
For details on object life cycle operations, refer to Object life cycle and statuses.
Composer provides a set of tools for defining and working with objects: