Hello! We want an Integration that should be moving files from a FTP server in a DMZ zone into another FTP server on our local network. I tried using EnsLib.FTP.PassthroughService(EnsLib.FTP.InboundAdapter, EnsLib.FTP.OutboundAdapter) Using this approach ensamble write data to the database, causing the CACHE.DAT to grow for every file that is moved. Looks like the entire file is written to the database, is this the case? We are not really interested in storing any file content information in ensamble in this particular case.
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.
I have a case where I am creating a PDF file from an Encoded String, and I need to transfer this file over to another server. I was wondering since this is PDF file if I could just invoke the FTP.OutboundAdapter within my Object script that is creating the PDF from the encoded string. Is this possible? Does anyone have an examples of using EnsLib.FTP.OutboundAdpater within their Object Script?
I am having a problem getting pair key authentication to work on my local PC. I am using freeSShd as the SFTP server. I generated private and public keys using putty gen . I used these keys to successfully log into the root directory using both Winscp and Putty. But this is not working with an FTP Operation. Below is the error that results. freeSSHd server log shows that I log in but immediately disconnect.
The minimum interval between invocations of the adapter by the Ensemble framework. For adapters that poll for external events, this is the polling interval. However, most polling adapters will process all inputs immediately if several are detected at one time.
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: