User`s guide

It is "tied in" to the IID environment and is manageable from within IID. One of the key features
that it provides is the notion of proxying requests. When a browser application runs, it is
constrained to communicate via REST back to the server which supplied the HTML in the first
place. This is known as the Same Origin Policy (SOP). When developing, this can be a problem as
we often wish to make REST requests to our IBM BPM server which … is not the same server as
the Web Preview Server run-time. SOP requires that the target of a REST request be the same host
and port number.
One solution to this development problem is the notion of a proxy. Here, the REST request is sent
to the Web Preview Server run-time and it is the Web Preview Server run-time that sends the
request to the target REST provider. A response from the REST provider is routed back through
the Web Preview Server and finally to the browser application. This circumvents the SOP as from
the browser's perspective, the REST request was sent to the same server that served up the HTML
in the first place (i.e. the Web Preview Server).
When we open the properties of the Web Preview Server definition, we are show the following:
Page 223