and forward mode relay
Transfer CFT Local Administrator store and forward mode enables you to route files from one computer
to another via one or more intermediate relays (computers or communication sites).
For example, when sending a file from computer A to computer C, where A and C are
either not directly connected or have a connection problem, the file is routed via
In the same way, a file to be sent to clients that are dependent on
the final receiver may transmit via intermediate systems and be sent on. This transfer
is accomplished using the same protocol from one end to
||This document describes the relay process as it relates to Transfer CFT. You can perform
relay transfers using other Axway products as the intermediary site.
The following illustration features 3 Transfer CFTs, where the protocol may be the
same or different between relay points:
- Source [Initial Sender A]
- Relay [Store and Forward B]
- Target [Final Receiver C]
Routing a transfer via a relay
Implementing the relay
To implement a relay in conjunction with
- Create the flow as described in the
Central Governance User Guide.
- In the SEND command include at a minimum:
- The name of the final receiver, for example TARGET_APPLICATION.
- The name of the flow, for example TEST_RELAY.
- The file to be transferred, for example
|cftutil send part=target_application, idf=test_relay, fname=report
- Optionally you can configure target post-processing to automatically send a reply.
cftutil send type=reply, part=&part, idm=idmr, idt=&idt, msg="Received file successfully."
cftutil end part=&part,idt=&idt
||You can use the script delivered with
Transfer CFT Local Administrator in the
runtime/exec directory/BIN_re.cmd as a basis for your ACK reply from the target application.
||When viewing the final transfer in the CG View Cycle Graph, you will see the number
of Transfer CFTs involved minus 1 entries and that these entries are linked. In the
example above, there would be two entries for the single "report" transfer.
- You cannot use a distribution list on the relay site, that is, when this site is being
used as part of a store and forward flow.
Transfer CFT Local Administrator store and forward mode is only possible from a requester/sender (write transfers
only, not read).
The following routing transfer concepts are described in this section:
- The protocol used
to implement the store and forward
- The types of store
and forward managed by the Transfer CFT
The processing possibilities using the store and forward site are detailed
in the next topic,
and forward processing
Protocols to implement store and forward mode
In order to route a file transfer, you must identify the partners involved
in the transfer: the initial sender and final receiver of the transfer.
Transfer CFT Local Administrator supports the following protocols for store and forward operations:
- PeSIT E
- PeSIT D CFT profile
For these protocol, the objects transferred can be files or messages,
in write mode only, the sender requester mode.
These three protocols manage the acknowledgement messages following
the reception of a file. See the SEND TYPE = REPLY command. The PeSIT
profile protocol also manages the sending of messages.
See the SEND TYPE =
Store and forward types
Three types of store and forward operations are possible on the initial
Backup store and
After unsuccessfully attempting to connect to a final
file receiver (the call retry attempts have expired), Transfer
CFT forwards the file to an intermediary site as a backup.
: For a given final receiver, the Transfer CFT immediately stores
and forwards the file.
store and forward
: For a given final receiver, Transfer CFT routes
a file from the sender to the first intermediary partner. Each site only knows the
next (intermediary) partner. When using this mode, the final destination does not
actually have to be configured in the source Transfer CFT configuration.
For the corresponding parameter settings see
and forward processing