Logical order for creating objects
Creating objects from the contextual menu
When you create new objects, you can either complete all the property definitions for the object immediately, or you can give the object a name, store it in the metadata repository and define its properties at a later stage. The object status remains ToBeChecked until you have defined all the mandatory object properties and checked the object.
When you create new objects, you can either start with the lowest object in the hierarchy and build your configuration from the bottom up, fully defining and checking each object before you use it in another object. This is known as a bottom-up approach. If you take this approach, there is a logical order for defining objects, as described below.
Alternatively, you can adopt a top-down approach. In a top-down approach, you use the top-level object, the Integration-Services-Diagram, as your starting point and schematically define how you want a set of applications to communicate.
You may for example know that you require a Host object in a given location. On that Host, you require a Axway Server and an external application (Application object). The Application must communicate with a B2B partner whose Host is not known - a Partner object. In this scenario, you can set out the required, but undefined objects on the Diagram and complete their definition subsequently.
When you create objects from the bottom up, keep in mind that there is a logical order for creating objects. For example, you cannot complete the definition of a Axway Server if no CommNetwork is available. Similarly, the purpose of a Channel is to connect two software applications. This means that it is more logical to define Channel properties after you define the Axway Server, Application or Partner objects that it connects.
It is recommended that you define the common objects in this order:
- CommNetwork
- Host (and optionally CommAdapterTemplate and ServerTemplate)
- Axway Server
- TopographyDiagram (and optionally ServerList)
- Partner and Application
- Channel
- Integration-Services-Diagram (and optionally ChannelList)
For more information on how objects relate to one another, refer to Object dependencies.
For more information on defining objects via the Integration-Services-Diagram, refer to Integration-Services-Diagram: Start here.
To create new objects, follow the same basic procedure. In the Integration-Services workbench, you always create objects in a WorkFolder. The object name must be unique in that WorkFolder. See Conventions for names and descriptions for details.
- Define the object properties immediately, in which case you must complete all mandatory fields. For information on how to complete these fields, refer to the relevant topic for each object.
- Create the object without defining all the property definitions immediately, in which case you need only complete the Name field on the General tab.
- Define the object properties immediately, in which case you must complete all mandatory fields. For information on how to complete these fields, refer to the relevant topic for each object.
- Create the object without defining all the property definitions immediately, in which case you need only complete the Name field on the General tab.
The contextual menu adjusts depending on which object is selected in the left pane. To create a new object via the contextual menu, you must right-click the object above it in the hierarchy. For example, to create a new Application, right-click a Host object in the left pane. To create a new Partner, right-click a HostGroup.