File transfer on same server

Mohammed,

You will need 2 threads one inbound to read the file another outbound to write the file.

You will need routing set up on the inbound thread to the outbound thread.

Personally I would use the Fileset/Local protocol for both threads (assuming both the inbound and outbound are referenceable by the Cloverleaf platform.

You can do this with one thread. I have a few threads myself that are only used to move a file (with only minor changes) from one directory to another.

Like Jim I use the Fileset/Local protocol because I am always moving all files from one directory to another. What you need to do is to route the messages back to the same thread. Have you forgotten that?

See the included screenprints. In my example I am even creating a copy of the original file, hence the 2 routes.

Well, it depends on how you want the transfer to work.

What you have configured right now is that all files from the inbound directory will be taken and their content will be appended to the file ‘test.txt’ in the outbound directory. I have tried this configuration myself and this works; see the included screenprints and test-files.

But if you want the separate files to be copied to the outbound directory, you will need to use a specific TCL-proc called ‘gc_getIBFilesetNameForOB’ (it should be in your installation) and put it in the Directory Parse of the Fileset/Local Properties and in the TPS Inbound Data. This proc will take the filename of this file (= message) and put it in the metadata of this message. The outbound filename that you have put in (test.txt) will then be ignored.

Some screenprints of this as well in the Word-document.

Hope this helps.

One of the reasons I use two threads is so that it is easier for others monitoring the integration to see what is happening with just a cursory glance.

Either way will obviously work.

I have nearly always needed to deploy some Tcl when doing file transfers (not that Ido that many) although the procs Iuse are generic so I only need to provide the appropriate arguments.

Only 3 attachments per post. This is the result-file.

Ah! I missed that one.

You get the id ‘_HCI_static_route_’ by pushing the button ‘Set static route’. You do this when you want to route ALL messages, regardless of the trx id that was setup (or not) on the Inbound tab (‘Trx id determination Format’).