On Tue, Nov 30, 2010 at 6:54 PM, <[email protected]> wrote: > I even managed to control/close all of the data and database connections to > IFS and the Database (which are on the same server, but separate from the > server used for Apache FTP Server), so that the number of established > sockets remains the same after several logins/downloads/disconnects. I can > provide this code if anyone else is interested.
Is this using JTOpen? > What I need to do next is set up the production environment that this FTP > server will operate in. There is an outward facing server in the DMZ which > users will connect to, but the database access and processing needs to be > done on the application server, behind the firewall. Only the application > server can connect to the database and IFS. > > Does anyone have any ideas on how to set this up with Apache FTP server? > Some type of FTP front-end to handle the connections, and then pass all the > commands to the application server, and receive all the responses and > filestreams, etc. FTP is somewhat hard to proxy due to the complexity with the data connections. There are dedicated FTP proxy products but I do not have any experience myself. I know that there has been some discussions here on similar topics, so there might be others with more experience. As for FtpServer, we support configuring a external IP for passive data connections which should help. /niklas
