Managed File Transfer

If the same file is transferred twice from Source (on-prem), it should generate an error stating the file already exists at the destination location (cloud).

There shouldn't be any duplicate entries at the target location (Cloud).

In the event that a file is already present in the destination and a file by the same name is placed at the source, what should be the behavior?

Does it will throw an error at the destination ? or it will overwrite the file at the destination?

Please let us know.

This is up to you and your Connect:Direct Process. You define the behavior by specifying the appropriate Disposition (disp) parameter on the Copy step. See Connect:Direct for UNIX Copy Statement. The three options are:

disp = [(] new | mod | rpl [)]

• disp=new indicates the file must not already exist. Otherwise the copy will fail.
• disp=mod indicates that if the file already exists, data will be appended to the end of the file. If the file does not exist, then mod behaves as if new is specified.
• disp=rpl indicates that copy to will act as if disp=new was specified if the file does not already exist. If the file exists, then it will be overwritten. The default is rpl.

If the same file is transferred twice from Source (on-prem), it should generate an error stating the file already exists at the destination location (cloud).

There shouldn't be any duplicate entries at the target location (Cloud).

In the event that a file is already present in the destination and a file by the same name is placed at the source, what should be the behavior?

Does it will throw an error at the destination ? or it will overwrite the file at the destination?

Please let us know.