Request
JSON
{
  "name":"Example",
  "servers":
    [
      "local$26f2fea8-3b7c-45a7-84a8-d1509e73fca4"
    ],
  "applications":
    [
      "local$75e22cd7-ce94-422a-9987-aa0403713e3e"
    ]
}
| Key | Type | Summary | Child of | 
|---|---|---|---|
name  | 
String  | 
Name of the deployment to be created. Must be unique  | 
—  | 
servers  | 
Array  | 
List of server or server group IDs  | 
—  | 
clusters  | 
Array  | 
List of cluster IDs  | 
—  | 
applications  | 
Array  | 
Version IDs of applications to be part of the deployment  | 
—  | 
| You cannot create a deployment using the server names and application names. Instead, use the server or version ID. | 
Using CURL on Windows
Note that this syntax is an example. Be sure to replace http://locahost:8585/mmc-console-3.7.3 with your own MMC hostname, port number, and setting for mmc-console-3.7.3 (which is usually the name of the deployed mmc .war file).
 curl --basic -u admin:admin -d  "{\"name\" : \"ExampleDeployment\" , \"servers\": [ \"local$26f2fea8-3b7c-45a7-84a8-d1509e73fca4\" ], \"applications\": [ \"local$32bb47d3-d180-4bb9-8906-2378dad9ae21\" ]}" --header "Content-Type: application/json" http://localhost:8585/mmc-console-3.7.3/api/deployments
Using CURL on Linux
 curl --basic -u admin:admin -d '{"name" : "ExampleDeployment" , "servers": [ "local$26f2fea8-3b7c-45a7-84a8-d1509e73fca4" ], "applications": [ "local$32bb47d3-d180-4bb9-8906-2378dad9ae21" ]}' --header 'Content-Type: application/json' http://localhost:8585/mmc-console-3.7.3/api/deployments
Response
JSON
{
  "applications":
    [
      "local$1b8ee6e2-043c-403c-b404-af3aa74d6f92"
    ],
  "clusterIds": [],
  "clusterNames": [],
  "href": "http://localhost:8585/mmc-console-3.7.3/api/deployments/local$97e3c184-09ed-423e-a5a5-9b94713a9e36",
  "id": "local$97e3c184-09ed-423e-a5a5-9b94713a9e36",
  "lastModified": "Mon, 5 Sep 2011 12:19:15.138 GMT",
  "name": "Example",
  "reconciled": false,
  "servers":
    [
      "local$3a99adfe-e942-4b52-b082-1a351de01420"
    ],
  "status": "UNDEPLOYED"
}
| Key | Type | Summary | Child of | 
|---|---|---|---|
applications  | 
Array  | 
List of valid application version IDs to be assigned to the new deployment  | 
—  | 
clusterIds  | 
String  | 
List of cluster IDs used as deployment target  | 
—  | 
clusterNames  | 
String  | 
List of cluster names used as deployment target  | 
—  | 
href  | 
String  | 
Full link to the resource  | 
—  | 
id  | 
String  | 
ID of the deployment  | 
—  | 
lastModified  | 
String  | 
Creation time-date  | 
—  | 
name  | 
String  | 
Name of the deployment to be created  | 
—  | 
reconciled  | 
Boolean  | 
Default value is false. A deployment is unreconciled when at least one server is down and/or at least one app has not been deployed on at least one server  | 
—  | 
servers  | 
String  | 
List of servers IDs used as deployment target  | 
—  | 
status  | 
String  | 
Deployed, Undeployed. When a Deployment is created, default value is Undeployed  | 
—  | 
XML Editor or Standalone
200  | 
The request has been fulfilled and resulted in a new Deployment being created/ Deployment created with some errors  | 
400  | 
Policies do not allow adding that deployment/Missing Deployment Name/Missing target/Missing application/Malformed new deployment request  | 
401  | 
Invalid name  | 
402  | 
Irrecoverable errors when creating the Deployment  | 
404  | 
Fatal Error: Deployment created but incorrectly persisted  | 
409  | 
A deployment with that name already exists  | 
500  | 
Fatal Error  | 
MMC version
From  | 
3.2.2  | 



