Each E2E Bridge provides an Apache reverse proxy as described in Bridge Architecture. This proxy can be automatically configured by defining proxy components for SOAP and HTTP services in the component diagram. Please refer to Managing Proxy Services for more information about how to manage these proxies after deployment.

Putting a proxy component in front of a given SOAP or HTTP service is usually done by using the component wizard as described in the Creating a Component Diagram.

Figure: Component Diagram of the HTTPS Proxy Dedicated Example

The proxy definitions are specified via tagged values on the E2E SOAP Service.

Tagged Value	Description
proxyPort
proxyPath	The path used to dispatch the request to the SOAP/HTTP service. By default, the path consists of a string unique within the proxy context having the following syntax: /<target host name>/<composite name>/<service name>. For example, assuming the xUML service shown in the component diagram above is running on myBridge.e2e.ch, the default path would look like /myBridge.e2e.ch/HttpsProxyDedicatedExample/HttpsProxyDedicatedService. A request URI starting with this path is then automatically redirected to http://myBridge.e2e.ch:12203 .
proxyHost
externalProxyHost
proxyProtocol

The following examples show how to:

• implement a proxy server in front of the E2E Bridge services using the http protocol
• implement a proxy server in front of the E2E Bridge services using the https protocol and certificates
• implement a proxy server in front of the E2E Bridge services using dedicated machines