My first file transfer!

After installing your Transfer CFT, you can use the delivered configuration samples and default values to quickly and easily perform your first transfer.

For more information on starting your Transfer CFT, and basic operational commands, see the section Start, stop, and Transfer CFT administrative scripts.

This topic describes how to:

Perform a file transfer using the sample configuration

The sample file features two default partners, NEWYORK and PARIS. Each of these partners is pre-configured to communicate using the PeSIT protocol. Additionally, both of these partners listen on the localhost interface. You can begin with a simple transfer, and then check the catalog for transfer details.

To send a file from PARIS to NEWYORK, run the following command:

CFTUTIL send part=NEWYORK, idf=txt

To check in the Transfer CFT catalog to confirm that the transfer completed successfully, enter:

CFTUTIL listcat

You should see that the default file was sent from NEWYORK to PARIS. There are two entries are displayed, this is due to the fact that you performed a loop transfer using the localhost interface.

Partner  DTSAPP File     Transfer         Records       Diags        Appli.   Appstate.

                Id.      Id.       Transmit     Total   CFT Protocol Id.

-------- ------ -------- -------- ---------- ---------- --- -------- -------- ---------

NEWYORK  SFX XX TXT      J2220582        112        112   0 CP NONE

PARIS    RFX XX TXT      J2220582        112        112   0 CP NONE

To display exhaustive transfer details, enter the command:

CFTUTIL listcat content=debug

The purpose of the My first file transfer section is to help you feel comfortable with basic Transfer CFT file transfer commands. Once you understand core file transfer concepts, you can delve into the rich array of parameters that allow you to customize your application integrations and data flows. Additional commands and options are available to help you define the monitoring granularity  for your executed transfers.

What's next?

In the following sections, we'll take a look at additional Transfer CFT transfer modes, as well as some useful configuration parameters. With Transfer CFT, the transfer initiator can be either the sender of the file or the receiver, as indicated in the examples below. Additionally, in these examples we will use the convention that the requester is the client, so the transfer description may read Requester/Sender if the client is supplying the file.

Note For more information on a command and a list of available parameters, enter CFTUTIL help cmd=<name of command>.

Perform a standard mode transfer

Let's start by performing the same type of transfer as in the sample configuration above, but without using the samples. First, you need to create two partners, and then exchange a file.

In this example, the Requester Paris site sends file to the Server New York site

 

Requester/Sender Server/Receiver

Configuration

  1. Create a partner.
  2. Create an IDF.

Runtime

  1. Run the transfer.
  1. Check the catalog.

Configuration

  1. Create a partner.
  2. Create an IDF.

Runtime

  1. Retrieve the sent file.
  2. Check the catalog.

Use the explicit mode to get a file

In explicit mode, an application makes a specific file available for a defined partner. Then when that particular remote partner is ready, it can retrieve the specified file, which only needed to be made available once.

In this example, the Sender site Phoenix has a file available for the Requester Paris site

 

Server/Sender Requester/Receiver

Configuration

  1. Create a partner.
  2. Create an IDF.

Runtime

  1. Make your file available.

    The send command is set with the ‘state=HOLD’ parameter. The HOLD attribute puts the file in the Transfer CFT catalog, and indicates that it is available for the partner.

  2. Check the catalog.

Configuration

  1. Create a partner.
  2. Create an IDF.

 

 

Runtime

  1. Receive the available file.
  1. Check the catalog.

Receive multiple files from a partner

This transfer mode is the same as the previously described explicit mode but provides multiple files for a defined partner. So an application might create several files and set them to an available state, and the remote partner can then retrieve these when ready, for example at a scheduled time.

In this example, the Sender Phoenix site has multiple files availalbe for the Requester site

 

Server/Sender

Requester/Receiver

Configuration

  1. Create a partner.
  2. Create an IDF.

Runtime

  1. Make a file available SEND part=PARIS, idf=INVOICE, state=HOLD.
  2. Repeat with another file.
  3. Repeat again with a third file. This ‘HOLD’ attribute puts the files in the Transfer CFT catalog and makes them available for the partner.
  1. Check the catalog for 1 entry per transfer. A generic entry is set.

Configuration

  1. Create a partner.
  2. Create an IDF.

Runtime

  1. Receive all of the available files:
    RECV part=PHOENIX, idf=INVOICE, file=ALL.
  1. Check the catalog for 1 entry per transfer. A generic entry is set.

Use the implicit transfer mode

The implicit transfer mode is often used to make a file whose content is frequently changing available to partners. The file is always available and partners can retrieve it as many time as necessary.

In this example, the Sender Phoenix site has a file whose contents may be frequently updated availbe

 

Server/Sender Requester/Receiver

Conf

  1. Create a partner.
  2. Create an IDF where impl=yes.

Runtime

  1. The CFTSEND is set with ‘impl=yes’.
  2. Check the catalog.

Conf

  1. Create a partner.
  2. Create an IDF.

Runtime

  1. Receive the file.
  1. Check the catalog.

Send using open mode

This mode is similar to the FTP put command. It allows you to define the file name in the remote partner. The receiver must accept the open mode. Then, using a simple SEND command allows you to send a file to a partner in a dedicated directory with a dedicated file name.

In this example, the Sender New York site is sending a file to a partner that receives in open mode

 

Requester/Sender Server/Receiver

Conf

  1. Create a partner.
  2. Create a CFTSEND with fname=<FILE_TO_SEND>, nfname=cft/filpub/fic.txt …

Runtime

  1. Run the transfer.
  1. Check the catalog.

Conf

  1. Create a partner.
  2. Create an CFTRECV fname=&nfname…

    The syntax ‘fname=&nfname’ means that the receiver allows the open mode.

Runtime

  1. The file has been stored in the path defined by the client/sender, in this example: cft/filpub/fic.txt.
  2. Check the catalog.

Receive using open mode

This mode is similar to FTP get command. It allows the receiver to get a file from the sender in a dedicated location.  The receiver must accept the open mode. Then, a simple RECV command allows to get a file from a partner from a dedicated directory with a dedicated file name.

In this example, the Receiver site gets a file from the Sender

 

Requester/Receiver

Server/Sender

Configuration

  1. Create a partner.
  2. Create an CFTRECV that defines the fname.

Runtime

  1. Request the file stored on the remote server. Run the command: CFTUTIL RECV… nfname=<remote_requested_file>.
  1. The file retrieved is stored in the fname location.
  2. Check the catalog.

Configuration

  1. Create a partner.
  2. Create an CFTSEND where impl=yes, fname=&nfname.

    The syntax ‘fname=&nfname’ means that the server/sender allows the open mode.

Runtime

  1. The file stored locally in <remote_requested_file> is sent to the client.
  1. Verify the catalog

Perform broadcast and collect operations

Broadcast and collect modes allow you to send files to multiple partners and receiving files from multiple partners using a single command request for each.

Broadcasting

You can use broadcasting to send a file to an entire group of partners in one command, avoiding the task of sending the selected file individually to each of the partners in a flow.

The name of the broadcast list is itself a virtual partner, which contains a list of partners in your flow. This list of partners can be explicit, or it can reference a file that contains the list of partners.

Additionally, you can define what occurs if a partner is unknown, how the scripts are applied to the broadcast list, and so on.

More information...

In this example, the Sender Paris site sends a file to an entire group of partners in one command

 

Requester/Sender Server/Receiver – PHOENIX Server/Receiver – NEWYORK

Configuration

  1. Create a first partner NEWYORK.
  2. Create a second partner PHOENIX.
  3. Create a broadcast list that contains both part1 and part2.
  4. Create a CFTSEND.

Runtime

  1. Using one command, send a file to the broadcast list.
  2. The file is sent to both partners at the same time.
  1. Check the catalog. You should have 3 entries in the catalog, one generic entry and one entry per partner.

Configuration

  1. Create a first partner.
  2. Create an CFTRECV.

Runtime

  1. The first partner receives the file.
  1. Check the catalog, there should be get one entry for this partner.

Configuration

  1. Create a second partner.
  2. Create an CFTRECV.

Runtime

  1. The second partner receives the file.
  1. Check the catalog, there should be get one entry for this partner.

 

 

Collecting

Collecting files is the inverse of using a broadcast list. In the collect transfer mode you can receive a dedicated file from multiple partners (P n). This allows the receiver, or flow initiator, to receive a file from all defined partners using a single request command.

More information...

In this example, the Receiver Paris site collects or receives  a dedicated file from multiple partners

Client/Receiver

Server/Sender

PHOENIX

Server/Sender

NEW YORK

Configuration

  1. Create a first partner.
  2. Create a second partner.
  3. Create a collect list containing both NEW YORK and PHOENIX.
  4. Create a CFTRECV.

Runtime

  1. Using a single command, receive a file from both (all) partners using the defined collect list.
  1. Both files are received from both partners at the same time
  1. Check the catalog. You should have 3 entries in the catalog, one generic entry and one entry per partner.

Configuration

  1. Create this partner.
  2. Create an CFTSEND.

Runtime

  1. This partner makes a file available for the client SEND state=HOLD.
  1. The first partner sends the file.
  1. Check the catalog, there should be one entry.

Configuration

  1. Create a this partner.
  2. Create an CFTSEND.

Runtime

  1. This partner makes a file available for the client SEND state=HOLD.
  1. The second partner sends the file.
  2. Check the catalog, there should be one entry.
Note In these examples we created partners using the default MODE value, which is REPLACE. You can also use the MODE=CREATE, to create a new Transfer CFT partner.

Additional information

Once you understand the basic modes and concepts described in this topic, you can then add processing, symbolic variables, scripts and more to your transfers using other Transfer CFT options and features. See the dedicated sections in this document for details on customizing your transfer flows. A good place to start is Transfer Concepts, which presents high-level transfer processing concepts, transfer mode details, and procedural topics.

Related Links