Enabling Partial Matching of URL Aliases

In some cases, URL requests include identifiers for a particular API. Because these identifiers vary for each instance of an API, URL requests might not exactly match any of the defined URL aliases for a particular API. To enable you to define URL aliases for such APIs, webMethods API Gateway can use partial matching to process URL requests. A partial match occurs when a request URL matches or begins with only part of a URL alias.

When partial matching is enabled and webMethods API Gateway receives a request URL, an alias is considered a match if the entire alias matches all or the beginning of the request URL, starting with the first character of the request URL's path.

For example, if URL alias calc has a URL path of gateway/RESTCalcService/1.0 and webMethods API Gateway receives the following request URL:

https://MyHost:9072/calc/deleteCalc

The request URL matches the calc alias and resolves to the path: https://MyHost:9072/gateway/RESTCalcService/1.0/deleteCalc.

webMethods API Gateway retains the trailing characters of the request URL. In this case, webMethods API Gateway retains the /deleteCalc.

To enable webMethods API Gateway to use partial matching of URL requests, you must set the value of the parameter watt.server.url.alias.partialMatching to true in Integration Server (in the Integration Server Administrator, go to Settings > Extended link). The default is false. For more information on configuring partial matching of URL aliases using Integration Server, see IBM webMethods Integration Server Administrator’s Guide.