Overview
An HTTP URL alias is an alias that you create to replace a portion of the URL to a resource on Integration Server. The URL alias typically replaces the path portion of the URL which identifies the name and location of the resource. For example, when you create a URL alias for a service, the alias replaces the invoke directive and the name and location of the service on Integration Server. A client request for the service includes the alias instead of the invoke directive and the service information. When Integration Server receives the request, Integration Server invokes the service associated with the alias.
You can associate a URL alias with items such as services, HTML pages, dynamic server pages (DSP), an image file, or web services. In addition to associating a URL alias with a single resource, you can also identify a different resource for a URL alias based on the incoming port for the request. This makes it possible to define a single URL alias that resolves to different destinations based on the incoming port of the HTTP request. In addition, you can also define the "empty path" as an alias, allowing the definition of a default destination for any incoming port.
URL aliases have several benefits:
A URL alias may be easier to type than full URL path names.
If a resource has a URL alias, it can be easier to move resources on
Integration Server. An administrator updates the alias information to point to the new location; there is no need to notify users of the change.
A URL alias is more secure than URL path names because users do not see directory, service, or file names.
Note: | A URL alias can be used with HTTP or HTTPS ports only. |
You can create a URL alias from Designer or Integration Server Administrator.
Create an alias from Integration Server Administrator if you want to:
Assign an alias to a resource other than a Flow, Java, C, Adapter, or XSLT service. For example, from
Integration Server Administrator, you can associate an alias with a DSP, HTML, jpg, or web service.
Create a URL alias for a REST resource configured using the legacy approach.
Note: | For more information about the approaches for configuring REST resources, see REST Developer’s Guide. |
Associate more than one URL alias with a particular resource.
Create an alias for the “empty path”.
Specify a port-specific destination for a particular URL alias.
If you want to create a single URL alias for a service, consider using Designer. When you use Designer to create a URL alias, you do not need to specify the URL path. If Designer was used to create the URL alias, you can move a service from one folder to another without having to update the path name assigned to the alias. For more information about creating URL aliases for services in Designer, see webMethods Service Development Help.
