The setBaselines command sets baselines for the specified objects. Setting baselines enables you to then create a baseline SLA policy.

You can use the retrieveObjectData command to retrieve and output historical performance data to a file; then you can use that file as input to the setBaselines command. If you create the input file by hand, use the same format as the output of the retrieveObjectData command.

You can also use this command to delete existing baselines for the specified object or for all managed objects.

Command Syntax

btmcli setBaselines -i inputFile [-delete] [-all] 
                    -s sphereUrl -l username:password
Name Long Name Description
-i -- An XML document that indicates the baseline values for services, service operations, endpoints, endpoint operations, and transactions. Baseline values can be used for baseline service level agreements (SLAs based on historically-derived performance thresholds).
-delete -- Delete any existing baselines for the referenced managed objects before setting new baselines.
-all -- When combined with the -delete option, deletes all existing baselines for all managed objects. In this case, an input file is not required.
-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 encryptPassword command.


The following example shows the setBaselines command.

btmcli setBaselines -i MyBookmartBaselines -delete
            -s http://mySphereHost:1771/btmcentral/sphere/ 
            -l my_btm_admin_username:my_btmadmin_password