An Application object is an instance of a software application whose internal structure is not visible or configurable from insideAxway Composer. For example, an Application could be an Oracle application or legacy payroll software. The Application object is always located on a specific Host.
You can perform all basic operations on Application objects.
This object does not follow the standard object life cycle. You cannot send this object to Server. You can use the object in an Integration-Services-Diagram.
It is recommended that you create and store all Applications in a parent Folder that is accessible to all users. This is because if you define a Channel between Applications located in sibling Folders (at the same level in the Folder hierarchy), the Channel is only visible in the Folder where you created it. A user who connects to the WorkFolder where the other Application is defined cannot see the Channel.
For each Application, you must define the communication parameters required depending on whether or not your Application communicates via the services of a Axway Server located on the same Host. You can use either of the following methods:
Typically, in the case of the Axway Integrator product, the Application is not based on a Axway Server and you must define a CommNetwork, a CommAdapter and a CommPoint for the Application.
On the other hand, for Axway Transfer CFT or Messaging Servers, you typically need only define parameters for a CommPoint based on an External CommAdapter.