Route an specific application through a proxy

Question

I'm trying to route all the conections from an specific application through a proxy (HTTP) with user authentication.
The application doesn't have an option for this.
I know I can do this in two ways. The first one is modify the network configuration in the System Preferences, however, this affects all the connections, which I don't want.
The second method is using a third-party software: Proxifier, but it is too expansive for what I think can be done naturally by the system.
Is there another method, preferably free, to do this? Something in Terminal or similar?
Thank you.

Answer 1

Yes, it can be done; Assuming all of the class files
you need are installed, and the servlet engine has
access to other resources you need (the correct files,
other devices, etc) you can do it;The class files will be installed. Does the servlet engine normally have access?
I am probably making a Windoze exe from the class files, since the target users are all using Windoze. Does this have any effect on the question?
I would avoid it on general principles.
There are a couple of things to consider:
Your use of the word application make it seem like you
are essentially starting a Java batch job and running
it in a servlet engine. If you are doing this for a
job, you might find that employer policies prohibit
the use of web server resources for batch processing.Not a batch job, the application is basically a server itself. It is going to have request coming in on a port and it is going to respond. I am not trying to do this without the knowledge of the server admin. They are willing to let me run the server app. The only thing is that I need not tell them every time I want to stop/start the server app since the web server is at a remote location from where I am. If I can start/stop the server remotely, it saves them the trouble.
I can also use this interface to monitor the error log, etc...
The security models in servlet engines are frequently
different than for batch, the especially the way they
are optimized is different.
You will not be able to wait to reveal final results
unless the application is very quick; Browsers
timeout rather quickly.Like I said above, I dont need to wait for results. I just need to be able to make a request to a servlet, and have it start/stop the application. hmmm... stopping might be a problem right, since the servlet wont have a reference to the app once it is running.... or can it hold the reference?? I am quite lost since I have never worked with servlets before.
Thanks again,
Dewang