- Added in Builder 6.0
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 | MultiExcerpt named proxyport was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro |
proxyPath | Specifies the part of the overall URL that is mapped to the actual host name and port. If proxyPath is used, the modeler must ensure that this value is unique within the proxy. 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: |
proxyHost | Specifies the host for the proxy deployment. If localhost is used, the proxy will be created on the same host the service is deployed to. Use a dedicated host, if you want to run your proxy on a different host of the same Bridge domain. See also externalProxyHost. |
externalProxyHost | Specifies the host name as seen by the client.
|
proxyProtocol | Specifies the used proxy protocol. |
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