Yes - OTM works with several reverse-proxy (RP) servers, though it was designed to work behind Apache-based RP servers. I've configured it in the past to work with Netegrity, Aventail, Apache and Microsoft ISA. Unfortunately, I haven't seen it work with WebSphere Edge
You are correct to configure the glog.webserver.URL to point towards your reverse-proxy:
Code:
glog.webserver.URL=https://reverse-proxy.nexweb.org:443
The problem you're experiencing is that OTM uses very complex javascript and the WebSphere Edge Server is trying to manipulate it in order to make it work. I've seen the same issue with Aventail and it just doesn't work. You'll need to do the following:
- Disable all html, jsp, javascript and URL parsing in the reverse-proxy server.
- Utilize a URL prefix (such as /otmprod) and allow the reverse-proxy server. This ensures that OTM will automatically prepend the URL prefix to all outbound URLs, including javascript.
- Ensure that the reverse-proxy server strips the URL prefix off before passing requests back to OTM.
So your data transmission looks like this:
- Request from browser to RPL:
- http://otmserver.mavenwire.com/otmprod/GC3/glog.webserver.servlet.umt.Login
- Request from RP to OTM web:
- http://otmserver.mavenwire.com/GC3/glog.webserver.servlet.umt.Login
- Response from OTM web to RP:
- http://otmserver.mavenwire.com/otmprod/GC3/glog.webserver.util.FrameGC3Servlet
- Response from RP web to browser:
- http://otmserver.mavenwire.com/otmprod/GC3/glog.webserver.util.FrameGC3Servlet
- Request from browser to RPL:
- http://otmserver.mavenwire.com/otmprod/GC3/glog.webserver.util.FrameGC3Servlet
- Request from RP to OTM web:
- http://otmserver.mavenwire.com/GC3/glog.webserver.util.FrameGC3Servlet
- ... and so on.
This requires the proper configuration of your RP server and setting the following property in OTM:
Code:
glog.webserver.urlprefix=/otmprod
If that doesn't work, then the only option is to utilize one of the known-good reverse-proxy servers noted above.
Thanks,
--Chris