Use the setDefaultLoadBalancer command to set the default device used to model routing entry points discovered from observed message traffic.
In a simple environment with only one known load-balancer, that device is automatically used as the default. If you register additional devices, use this command to set which device should be used to model routing entry points.
See Setting up Load Balancers, for a complete discussion of load balancers and how the default is set.
btmcli setDefaultLoadBalancer -baseAddress baseAddress | -fn friendlyName -s sphereURL -l username:password
| Name | Long Name | Description |
|---|---|---|
| -- | -baseAddress | The base address of the URL for the load balancer. For example, https://myf5:443/ |
| -fn | -- | The friendly name of the load-balancer in the sphere. This name is displayed in the summary pane when you select Devices from the navigator. It is the name you assigned when you registered the load balancer. |
| -s | -sphereUrl | Required. The URL of the sphere with which you want to register the container.
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 specifies the default routing device:
btmcli setDefaultLoadBalancer -baseAddress https://myF5:443/
-s http://localhost:8080/btmcentral/sphere -l admin:abracadabra