Generic FTP & Encrypted Password Challenge
- This topic has 0 replies, 1 voice, and was last updated 16 years, 2 months ago by
.
-
Topic
-
I’ve been pondering the way our ftp jobs are set up. They all basically do the same thing — - * At a scheduled time, once a day, the ftp process connects to the vendor server, reads from one or more files, translates the financial HL7 messages in the files, and writes them to another file on the local server.
* Each ftp process has it’s own unique ip address, user name, password, inbound directory, scheduled trigger time, inbound file name pattern, and outbound file name (in the second thread).
* They all use the same basic tps inbound parse for collecting the inbound files. — I have written a tclproc which they can all use that accepts the file name pattern as an argument.
As a programmer who likes to make things as reusable and as consolidated as possible, I can’t help but think that all of these ftp processes should be able to run within the same process somehow. There should be a way to pass to the thread with the fileset-ftp protocol the ip address, user name, an encrypted password (which we need to decrypt before using — thus, part II of my challenge), inbound directory, inbound file name pattern, and outbound file name as arguments, possibly based on the scheduled time, perhaps via a cronjob.
Perhaps all the ftp thread/process does is collect the correct files from the servers and dump them into a local folder/directory for processing/translation. That’s still quite a feat. Then the next step in the process just needs to determine the file name to translate and route the messages in the files to the correct “outbound” file.
If it could be done, it would be a lot less threads and processes. I’m just not sure how to pass all of that information to a thread and have it be different every time. Nor am I quite familiar with using tcl to encrypt just one field and decrypt it and have it always come out correctly every time.
😉 So, I thought I’d ask the big brains here if you have any ideas.
- * At a scheduled time, once a day, the ftp process connects to the vendor server, reads from one or more files, translates the financial HL7 messages in the files, and writes them to another file on the local server.
- The forum ‘Cloverleaf’ is closed to new topics and replies.
