Cisco CiscoWork QoS Policy Manager 4.1.2 User Guide

QPM allows external applications to trigger the deployment of a deployment 
group, by issuing an HTTPS request. This feature allows you to implement event 
or time-based triggering of deployment, as required. 

You can only trigger the deployment of the current version of a deployment group.

Certain parameters must be included in the HTTPS request. They are:

Username.

User password.

Device group name.

Deployment group name.

Job Name and Job Description are optional parameters that may be included in the 
HTTPS request.

The format of the HTTPS request is as follows (there are no spaces in the URL):

https://<host_name>/MDC/servlet/com.cisco.core.mice.direct? 
command=directOneTimeConnection 
&username=<user_ID>&password=<user_password> 
&url=/qpm/servlet/ExternalDeploymentServlet 
&deployment_group=<deployment_group_name> 
&device_group=<device_group_name> 
&job_name=<job_name>&job_description=<job_description>

The following provides an example of an external HTTPS request:

https://localhost/MDC/servlet/com.cisco.core.mice.direct? 
command=directOneTimeConnection &username=john&password=abc 
&url=/qpm/servlet/ExternalDeploymentServlet 
&deployment_group=Default%20Deployment%20Group 
&device_group=Default%20Device%20Group 
&job_name=external%20deployment 
&job_description=auto%20deployment%20on%20weekend

If the input parameters are correct, the deployment process will be activated. The 
request will respond with either a success or failure message, including 
descriptions of any errors or warnings.