Configuring Reverse Proxies

Reverse proxies are used to map internal proxies to external proxies.

A reverse proxy is located between a service consumer and a provider back-end system, from where it routes consumer messages to a service endpoint.

You can configure a back-end system to support the deployment of a reverse proxy. You can set substitution rules for the host name, the http port, and the https port, as well as the path prefix for the following:

WSDLs that are exposed directly from the back-end system
WSDLs that are published to the UDDI registry
WSILs that are exposed at the back-end system

Reverse proxy settings are client-specific. You can make different proxy settings for each client.

Reverse proxy settings can be assigned to the UDDI part of the Services Registry that can be configured in the back-end system.

Procedure

To display or change the reverse proxy settings:

Go to the Technical Configuration tab.
Choose System Global Settings.

Go to the Reverse Proxy Settings tab.

An overview of the reverse proxies and the following settings is displayed:

Reverse proxy name	A unique name in the client that can be referenced by a UDDI registry setting.
Incoming http header host name	This attribute references the HTTP header field host. Here, you specify the Internet host and port number of the resource that is being requested. Messages that are sent can have the HTTP header set or not set.
Incoming ICM port	Specifies the port at which the message is received in an SAP instance. If the sender specifies the target port in the HTTP header, this is interpreted as the incoming ICM port.
Substitute host name	Specifies the host name that is used to replace the host names in the endpoint URLs in the WSDLs and WSILs. Additionally, the metadata URLs - WSDL URLs for service, binding, and port type – will also be substituted.
Substitute http port	The port number of the HTTP service is used to substitute the HTTP ports in the endpoints and metadata URLs.
Substitute https port	The port number of the `http` service that will be used to substitute the `https` ports in the endpoints and metadata URLs.
Additional path prefix	The path prefix for the paths of the endpoints and metadata URLs. The default path of an ABAP service is: `http(s)://<host>:<port>/sap/bc/srt/xip/sap/<service definition (name of the ABAP object)>/<client>/<service name>/<binding name>` This can be aliased by any name: `http(s)://<host>:<port>/<any name>` With an additional path `<prefix>`, the URLs of endpoints and metadata would look as follows: `http(s)://<host>:<port>/<prefix>/sap/bc/srt/xip/sap/<service definition (name of the ABAP object)>/<client>/<service name>/<binding name>` The same is true for aliases: `http(s)://<host>:<port>/<prefix>/<any name>` Note When a message is forwarded to the actual endpoint, the reverse proxy has to remove the prefix. End of the note.
Metadata protocol substitution	You can configure the protocol of the WSDL URLs for UDDI publication. Possible values are `http`, `https`, or `incoming`: `HTTP / HTTPS`: The configured protocol (`HTTP/HTTPS`) is used for UDDI publication. Import statements for other WSDL fragments also use the configured protocol. `Incoming` `HTTP` is used for UDDI publication. Import statements for other WSDL fragments use the same protocol as is used by the WSDL request.
Endpoint protocol substitution	Possible values are `config`, `http`, `https`, and `incoming`. If a request for a WSDL is sent through a particular protocol, the Endpoint protocol substitution setting defines the protocol substitutions for the endpoint URL. `HTTP / HTTPS` Substitution regardless of the incoming WSDL request and configuration `Config` Substitution as defined in the service configuration. `Incoming` Depending on the incoming WSDL request. the substitution uses the same protocol as is used in the WSDL request.

Note Note

The Reverse proxy name, the Incoming http header host name, and the Incoming ICM port are used to identify the reverse proxy. The other settings here determine what action is taken for an inbound http WSDL request.

End of the note.