In some cases, URL requests include identifiers for a particular resource. Because these identifiers vary for each instance of a resource, URL requests might not exactly match any of the defined URL aliases for a particular resource. To enable you to define URL aliases for such resources, Integration Server 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 Integration Server 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 a2 has a URL path of rest/purchasing/invoice and Integration Server receives the following request URL:

http://MyHost:5555/a2/75909

The request URL matches the a2 alias and resolves to the path: http://MyHost:5555/rest/purchasing/invoice/75909.

Integration Server retains the trailing characters of the request URL. In this case, Integration Server retains the /75909.

If you enable partial matching of URL aliases, do not define an alias that begins with another alias. For example, do not define an alias named a22 if an alias named a2 already exists. Integration Server evaluates a request URL in ascending alphabetical order. When a URL alias starts with the same characters as another alias, Integration Server will not match the longer alias. If you define a2 and a22 as URL aliases, Integration Server will never match a22 because Integration Server matches any request URL that includes the a22 alias to the a2 alias instead.