Show TOC

Background documentationMappings for Path Locate this document in the navigation structure

 

To describe how the system generates external URLs for Web services, we can assume that a URL has two main parts:

  • The first part contains the URI scheme, the host name, and the port used.

  • The second part contains the path to the resource and optional parameters.

Example Example

We have the following WSDL URL: http://service.example.com:50000/ExampleService/Example?wsdl

  • The first part is: http://service.example.com:50000

  • The second part is: /foo/bar/ExampleService/Example?wsdl

End of the example.

The system generates the second part of external endpoint and WSDL URL using the available path prefixes as described below.

Note Note

The path prefixes apply only to hosts for which you have set WS HTTP Mapping. For more information, see Configuring Reverse Proxy Settings.

End of the note.
Path Prefix Usage

Depending on the availability of path prefixes, the system generates external URL for Web services in one of the following ways:

  • If there is path prefix for endpoint and/or WSDL, then the second part of the generated endpoint/WSDL URL contains the corresponding value specified in the path prefix followed by the original path.

    Example Example

    There is my/folder prefix specified for WSDL. The system generates the second part of the URL as follows:

    • Internal URL: http://[host]:[port]/ExampleService/Example?wsdl

    • External URL: http://[vhost]:[vport]/my/folder/ExampleService/Example?wsdl

    End of the example.

  • If there is no path prefix specified, then the second part of the generated WSDL URL is the same as the second part of internal WSDL URL.