Resolution:
Description:
=========

When sending an outbound notify operation with EZComm in a FTP transport using the inputFile attribute of a SendRequestNotification activity, the file in the partner server is named, for example, "CuXhadfMoiid8UKFF_2DAo54-iiQ_2010-04-06_13-40-13-729.msg", rather than the 'inputFile' attribute of the JMS message.

Environment:
==========
BusinessConnect - all versions.


Resolution:
========

BusinessConnect (BC) uses the transaction id as part of the output filename, so the value of the field "transactionID" is what is present inside the SendRequestInput before the payload is routed to BC. Make sure that the "Generate Unique Transaction ID" box is unchecked in the Send Request task in BusinessWorks (BW).  If it is checked, the BW palette will generate and use its own transaction ID regardless of what you have set in the transactionID field.

If using a custom FTP script, the file can be passed in as a file reference via the inputFile reference in BusinessWorks to BusinessConnect. BusinessConnect will pass the file name in through the srcFileName job variable.  As stated in the BusinessConnect manual, the job.get("srcFileName") function will return a value in cases where the payload is in a referenced file.  The custom FTP script can then transfer data to the target system using the referenced file name "as is".

Keywords/Tags:
= = = = = = = = =

How to preserve the original file name while sending a request to an FTP server using the EZComm protocol with an FTP script