Diagram
The branch element for reusable transfer configuration. Subsequent fragments are used e.g. for file transfer specifications, notifications, mail server settings, that can be used in a number of file transfer Profiles. A fragment specifies how a file transfer is carried out whereas a Profile specifies what should be transferred. Therefore multiple profiles can use the same fragments, e.g. to transfer different files from the same source or to reuse the same transfer specification as the source and the target in different transfer operations. Fragments are a means to organize file transfer settings in a reusable way: Any number of fragments can be configured. They are distinguished by their name attribute. References to a fragment use the value of the name attribute to identify the respective fragment. Notification fragments are used to specifiy how notifications will be sent to recipients in case of file transfers. Fragments for credential stores are a means to organize secure settings in a reusable way: Any number of fragments can be configured. They are distinguished by their name attribute. References to a fragment use the value of the name attribute to identify the respective fragment. Mail server fragments are used to specifiy by what mail server notifications will be sent to recipients in case of file transfers.
Fragments
Element
Type
Required
Description
ProtocolFragments
Required
Notes
NotificationFragments
Optional
CredentialStoreFragments
Optional
MailServerFragments
Optional
Notes
ProtocolFragment:
- The ProtocolFragment describes how the file transfer is to be carried out – i.e. per FTP proxy.
MailFragment:
- The MailFragment describes how notifications about the transfer are to be transmitted.