You can only move the entire set of endpoints defined for a service in a given WSDL as a unit, regardless of how you identify the endpoints.
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.
moveEndpoints command does not move any measurements. The measurements for the endpoint remain associated with the endpoint and nothing happens to these when the endpoint is moved to a new service. The measurements for the old service version continue to include data previously aggregated from the moved endpoint. The historical measurements for the target service version are unchanged; new measurements for the endpoint are included in the target version of the service.
You can use this command to split a service in two by specifying the previously undefined version with the -T flag and using the -force flag.
mergeServices command to merge all endpoints from one service version to another.
See Resolving Discovery Issues, for a discussion of the use of this command in resolving discovery issues.
btmcli moveEndpoints -n friendlyName | -qname qname -w wsdlUrl | -e endpointUrl -V version -T targetVersion [-P] -s sphereUrl -l username:password
|-n||-name||The friendly name of the service whose endpoints are moved.
If two versions do not have the same friendly name, you must use the qname flag to specify the service name.
|-qname||--||The qualified name of the service whose endpoints are moved.
The qualified name has the form WSDLtargetNamespace:serviceName. For example: http://amberpoint.com/orderService:CreditServiceSOAP.
|-w||-wsdlURL||The URL of the WSDL file that defines the service whose endpoints are moved.|
|-e||-endpointUrl||The URL of an endpoint in the source version of the service.
The endpoint URL might identify multiple endpoints if the WSDL defines more than one endpoint at the same URL with different bindings. This is a common case for WSDLs that define more than one endpoint for a service.
|-V||-version||The version of the service that will be merged into the specified target.
Use the "-" string to represent the default, unnamed version.
|-T||-targetVersion||The service version in which to merge the source version (-V). After the merge, this version will contain the endpoints from both versions.|
|-P||-preview||Specify this flag to preview the results of the move without actually moving endpoints.|
|-f||-force||Create a new service version if the specified target version does not exist. You can assign this service a name different from that of the source version using the -newServiceName flag.|
|-newServiceName||If you use the -f option, you can use the -newServiceName flag to specify a friendly name for the target version that is to be created. If a target version already exists, this flag is ignored.|
|-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
btmcli moveEndpoints -n catalogService -e http://test.myhost.com:7412/catalogMgmt/svcs/CatalogSvc -V 1.5 -T 1.6 -s http://localhost:8080/btmcentral/sphere/ -l admin:abracadabra