Typically, you would use this command when the system discovers two endpoints with the same path but different host names due to a DNS alias that was not known to the system. Executing this command also adds the missing alias to make sure that future discoveries do not result in recreating the duplicate endpoint.
If duplicates differ only in their base address, it is assumed that other endpoints found under both base addresses are also duplicates. In addition, the service descriptors (WSDLs) for the duplicate endpoints are also deleted from the model. WSDLs and endpoints under the duplicate entry point that are not actually duplicates are not removed; they are moved under the remaining entry point.
If the specified endpoint URL refers to a dependency-discovered endpoint and the duplicate URL refers to a discovered or manually-registered endpoint, the command is reversed: the duplicate endpoint is preserved and the base address of the endpoint URL is treated as an alias.
You can preview the results of this command before committing to the changes it defines. After previewing, you must run the command again without the -P option to actually make the changes.
See Resolving Discovery Issues, for a discussion of the use of this command in resolving discovery issues.
btmcli removeDuplicateEndpoint -e endpointUrl -d duplicateUrl [-P] -s sphereUrl -l username:password
|-e||-endpointUrl||The URL of the endpoint to preserve.|
|-d||-duplicateUrl||The URL of the endpoint to remove as a duplicate.|
|-P||-preview||Preview the results of the move without actually moving endpoints.|
|-s||-sphereUrl||The URL of the 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
In the following situations, the
removeDuplicateEndpoint command will refuse to make the specified changes to avoid compromising the integrity of the model or destroying information that is not actually duplicated.
The endpoints belong to different services or different versions of the same service.
The endpoints implement different interfaces.
The endpoints live in different deployments.
The WSDL for the duplicate endpoint refers to services or endpoints that are not referenced by the WSDL for the remaining endpoint; that is, the WSDLs cannot be considered duplicates.
In these cases, you might need to do the following:
unregister command to unregister the service endpoints that cannot be removed with the removeDuplicateEndpoint command.
addBaseAddressAlias commands to add aliases that help the system recognize endpoint duplication.
The following example shows the
btmcli removeDuplicateEndpoint -e http://jbujes.edge.com:7001/bookmart/credit/CreditService -d http://jbujes.delphi.com:7001/bookmart/credit/CreditService -P -s http://localhost:8080/btmcentral/sphere/ -l admin:password