Use the addPathAlias command to add an alias representing an alternative URL path that can be used to access the specified WSDL or endpoint. Specifying this alias can help prevent duplicate artifacts from being created during discovery.
Normally, path aliases are added automatically in one of two ways:
The register command detects an HTTP redirect and adds the original URL as an alias to the service descriptor created with the redirected URL.
The user uses the removeDuplicateEndpoint command to remove an unwanted duplicate created due to message traffic being observed at a non-canonical URL for an existing endpoint.
In the second case, adding the alias when the original endpoint is registered or discovered will prevent the duplicate from ever being created. So, you might add the addPathAlias command to a script used to recreate an environment that was observed in testing to have this problem.
Use the removePathAlias command to delete an alias you created with the addPathAlias command.
See also addNodeAlias for host name aliases and addBaseAddressAlias for other aliases in the authority part of the WSDL's URL.
See the section "Resolving Discovery Issues" for a discussion of the use of this command.
btmcli addPathAlias -s wsdlUrl | -e endpointUrl -alias pathAlias -s sphereUrl -l username:password
| Name | Long Name | Description |
|---|---|---|
| -w | -wsdlUrl | The full URL of the WSDL (service descriptor) for which you want to add an alias. |
| -e | -endpointUrl | The full URL of the endpoint(s) for which to add the alias. If multiple endpoints are matched, they will all be given the alias. |
| -alias | -- | The alternate path to map to the same descriptor or endpoint. This should be just the path portion of the URL, starting with "/". |
| -s | -sphereUrl | The URL of the sphere.
http://hostname:port/btmcentral/sphere/ This flag is not required if you have set the AP_SPHERE_URL environment variable for your sphere. |
| -l | -userLogin | The username and password associated with the sphere, in the format: username:password. This set of credentials must belong to a user in the btmadmin role.
See Security Options in Accessing CLI Commands for information on furnishing login credentials. You can encrypt passwords using the |
The following example shows the addPathAliascommand.
btmcli addPathAlias -e http://jbujes:7001/bookmart/credit/CreditService
-alias /bookmart/amex/CreditService
-s http://jbujes:8080/btmcetnral/sphere/ -l admin:abracadabra