The alias must be defined locally for this entry point only. Aliases defined at the network node level must be removed using the
removeBaseAddressAlias command allows you to remove incorrect or outdated aliases from the system. Although it does not undo the removal of duplicate artifacts caused by the complementary
addBaseAddressAlias command, any new discoveries for the base address and the ex-alias will again be treated as separate entities.
See Resolving Discovery Issues, for a discussion of the use of this command in resolving discovery issues.
btmcli removeBaseAddressAlias -baseAddress address -alias address -s sphereUrl -l username:password
|--||-baseAddress||The base address of an existing entry point in the sphere. Use the format scheme://host:port/|
|-alias||--||The base address to remove as an alias for the above entry point.|
|-s||-sphereUrl||The URL of the sphere.
This flag is not required if you have set the AP_SPHERE_URL environment 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
btmcli -removeBaseAddressAlias http://jbujes:8080 -alias http://220.127.116.11:8080 -s http://localhost:8080/btmcentral/sphere/ -l admin:abracadabra