I think it is important to understand the term "does not support Proxy". Is the application speaking HTTP but does not allow to configure a proxy? In this case MWG could be deployed in a transparent mode. The application thinks it is talking to the internet directly, but MWG will intercept the traffic and filter it (if possible).
If the application is not speaking HTTP then MWG won't be able to filter it, since MWG is naturally a HTTP proxy. It ships with a SOCKS proxy which basically accepts connections on a port and allows to redirect the traffic to a destination. You can add some simple source/destination rules, but authentication is (at the moment) not possible, at least without further manual tweaking. Also the SOCKS proxy will in no way call the rule engine to apply any of the filters set there.
Additionally the application must support SOCKS.
Probably you rather need a plain TCP proxy that picks up traffic to a specific destination from the network and applies some rules on it. I believe this is probably a job for a firewall.
Maybe you could share some more information about the applications you are refering to and their issues talking through MWG. This could help.
The application does not support the configuration of a proxy. I was more looking for something that would intercept HTTP request (or another TCP port) and relay it across WW. WW in Transparent mode is not an option at this point.
If the application is trying to connect to a specific port, you can use the Mcafee client proxy to redirect the traffic you.
Is it in production or still in beta? Is it included with WW licence or we have to pay for it?
is in production. https://contentsecurity.mcafee.com/ can download it from your account. is included in the package Webgateway.
then you're inside, you go to tools. if you have not used it is recommended to download the manual.
If nothing else work, read the manual... )