Interwoven Proxy Server

Ottawa_IWOV

Does anyone know how exactly the Interwoven Proxy server is implemented? I understand what it does. But need to know more about the actual technology it uses etc.

Thanks,

Lucas.

Lucas Cochrane
lcochrane@dc.com

abackenr

not quite sure what kind of information you're looking for. i'll note down the highlights, and you can respond with specific questions:

o iwproxy has not changed significantly between 5.0, 5.5, and 6.0 so the following is valid for these versions of TS. There are significant improvements planned for an upcoming release.

o iwproxy is a bare bones http server that has specific knowledge of TeamSite it uses in order to virtualize content.

o it is implemented in C++

o iwproxy is an http daemon that sits behind iwwebd (the interwoven web daemon) and typically runs on port 1080.

o it uses a set of rewrite rules (regular expressions) specified in the backing store to translate http requests from the client into requests to the customer web server and into vpaths within teamsite.

o an incoming request to proxy, results in a request to the customer web server to fetch the document. depending on your SCE/VisualPreview configuration, it will optionally inject javascript code (which it recieves from a request to servletd) into the response before returning the request to the client.

o the current implementation of iwproxy is not tied to any other webserver implementation.

o iwproxy must run on the same machine as TeamSite since it does make calls into the TeamSite server, in particular calls to ensure that the user has read access to the requested document.

o the user must be authenticated in order to get information from iwproxy. if the user is not authenticated, they will be redirected to a login screen

hope this helps.

ariel