ftp a file in it’s entirety

Leisa,

You should be able to accomplish this using the fileset-ftp protocol on your threads and simply treating each file as a single message (set the Style to single) and a raw route.

Hope that helps.

Jim Cobane

Henry Ford Health

Are you doing hci_static raw routing (shouldn’t give you trxid error if set up properly)?

It might be if you have a large file it might seem to be a big delay or ,depending on you platform, run into some resource constraint when treating the file as a single message. I am not sure about that though.

What Jim says: if you just want to send all messages from inbound thread A to outbound thread B (regardless of the content/sort of message), then use static routing.

Easy to do: create a route from thread A to thread B and hit the ‘Set as Static Route’ when inside the route; this will give you the route ‘_HCI_static_route_’. This now tells the engine to ignore TrxIds and just send all messages towards B.

OK so you now have the FTP working (using the static route) but the stored procedure is not working?

If you have the Data Integrator product, then you can execute a stored procedure at almost any part of the FTP interface, in a tcl proc. So using this method, the stored procedure can be called from within the start to finish of the FTP transaction, making it part of the transaction.

If not, and you are using the database_outbound protocol to invoke a stored procedure, then:

1) the stored procedure portion of the interface would be a second, separate outbound activity (additional route detail). Meaning – that there would be one input thread (FTP) and two output threads (FTP, DB). The implication is that the FTP portion could fail but the stored procedure could succeed or vice versa. This is something to consider.

2) you do need to be sending something to that database outbound thread, just to get it to trigger the database call.

The database_outbound protocol requires you to configure it by selecting the database and table (or view) that will be the target, even if you are executing a stored procedure that has no arguments, even if you don’t need to send any data at all to the database.

So there are different approaches to this situation – here is one suggestion:

– have the database admin create a view that holds the minimum columns necessary

– use the Cloverleaf Database Schema Configurator to read that view (and build a VRL for that view)

– build a simple translator that ignores the input data (file) and just copies literal strings to the output (select your VRL for the output format), just enough to meet the requirements of the stored procedure

– configure your outbound thread to reference that view, and then build the stored procedure call. You can use the data items from your translator (by referring to them with the syntax) or by hardcoding literal string values in the stored procedure call.

ok no problem!