Hi Terry, we struggled with the same problem you are having and found a solution without modifying the source file name.
We have a legacy app on a mainframe that FTP’s us a file and they don’t alter the name, the specify a destination file name and a content type.
When FTPing a file to the Integration Server FTP port, the syntax of the put is:
put <sourcefile> <destinationfile>;<filecontentype>
In our example, the sourceFile name on the mainframe is called:
TFRGD.WMFO.SALESUS.GL.OUT.A
The destinationFile is:
TFRGD.WMFO.SALESUS.GL.OUT.A
The fileContentType is:
text:plain
The FTP put command they use (after doing a cd to our interface namespace folder) is:
put TFRGD.WMFO.SALESUS.GL.OUT.A TFRGD.WMFO.SALESUS.GL.OUT.A; text:plain
This tells webMethods that the content of the file is: text:plain (and it already has a mime type defined and knows how to handle it).
This works fine for us.
So I think all that is missing from the other suggestions in this thread is to specify a destination file name followed by the content type.
Anyway, give it a try.
Note: this solution is documented in the webMethods Flat File Schema Developer’s Guide (v6.0.1.)
Good luck!
Wayne
#webMethods#webmethods-Protocol-and-Transport#Integration-Server-and-ESB