File Transport Protocol (FTP) is a standard network protocol used for the transfer of computer files between a client and a server on a computer network.
Looking for some suggestion on what the community has been setting Confirm Complete to? The testing I did when this was set to size is way too slow at around 1 message for 2 seconds. Is it safe to set this value to None? Would I get half messages if the sending system didn't compete writing the message.
We use the %Net.FtpSession class to perform FTPS file transfers. This has worked fine with Implcit FTPS servers but crashes when trying to connect to an Explicit FTPS server. Explicit FTPS has a slightly diffferent negotiation in the intitial connection and different ports.
Has anyone gotten Explicit FTPS working with the Cache classes?
I have been using %Net.FtpSession and while it works, its handling of file/directory listings from an FTP server is less than ideal and, while this is due to the FTP protocol itself, the class could be written to handle this as would an FTP client such as FileZilla and command line/class FTP handlers for other languages. I was wondering if anyone knows how the Ensemble adaptor works with this in case it provides code that would help, though the source does not seem to be available. Below are the issues I see in FTP, some are based on past experience writing our own FTP handler in the past
I'm designing a workflow for PHR via FTP. What I've done is create a single FTP adapter to pick up files from multiple customers. A router then accesses a lookup table and determines if a particular customer is allowed to send a particular message type to the state. If not, the message doesn't go out. It seems like everyone is against this approach (other than my CEO, thankfully), including Intersystems:
i have a issue in getting the complete file path when using the FTP Adapter in service. EnsLib.FTP.PassthroughService / EnsLib.FTP.InboundAdapter
I need to know the folder name (including sub folder) where the new file is found by the service when looking up for new files. The normal file class is working good as expected
More details below,
In the below two examples you can notice folder name is fetched by normal File adapter, but in FTP only the file name is available.
TL;DR: If I set an Ensemble Production Service based on EnsLib.File.PassthroughService to a Binary charset encoding, it breaks the file handling. Any ideas?
A question to see if anyone out there is already doing this.
We have built a custom BS based off of the EnsLib.FTP.InboundAdapter. We have our processes wake up (using the Scheduler), grab the files in the directory, stay awake for a while, and then go back to sleep.
Each file goes through on its own message. So we can trace each individual file and we know if it made it successfully or not.
We have a custom FTP Service , and custom FTP adapter . Customization is just to find a duplicate file and for giving specific dynamic file spec pattern. While running and polling for files, we are getting this error. Could you please help ? What's the issue and how to resolve it ?
ERROR <Ens>ErrFTPListFailed: FTP: Failed List for <FileName> (msg='Cache error in 'readResponse': <READ>zreadResponse+4^%Net.FtpSession.1',code=426)
How do you used this Operation (EnsLib.HL7.Operation.FTPOperation) I have an FTP site. But, I was wondering if you could do this within the Ensemble Engine.
I would appreciate some advice please- hopefully there is plenty of experts out there.
We are setting up an sFTP share between hospital trusts here in the UK and I have set the outbound operation up using a custom extension of EnsLib.HL7.Operation.FTPOperation.
We are configuring a VPN tunnel to run between the sites also so there is a bit of firewall / network routing to take place to enable the connection but to add in a complication we are on a mirrored cluster and usually present on a Virtual IP address.
FTP (File Transfer Protocol) is a network protocol for transmitting files over TCP/IP connections in a network (including the Internet) configured to transfer files via this protocol. In an FTP transaction, a file sender is called a local host. A file receiver involved in FTP is a remote host, and it is usually a server. Although many file transfers can be conducted using Hypertext Transfer Protocol (HTTP), FTP is still commonly used to transfer files behind the scenes for other applications, such as banking services.
In 2020 we implemented HealthConnect as our HL7 interface engine. Having completed this, we are currently evaluating whether it would be beneficial to migrate our managed file transfers from our current MFT software, MOVEit to HealthConnect. I am interested in hearing from any InterSystems customers who have previously used MOVEit and currently using HealthConnect for file transfer managment. Any feedback would be appreciated.
By views
Open Exchange app
