Conversion to Different Deployment Types
REST APIs are enabled with AdminStudio Enterprise Edition.
When you send this request, you can convert one deployment type to another supported Deployment Type
| Request Type | Description |
|---|---|
| API | http://localhost:8086/catalog/deploymenttypes/conversions { "PackageID" : "1", "AACSettings" : "C:\\Users\\Administrator\\Desktop\\Conversion.aacx", "Target" : { "OutputPath" : "C:\\Users\\Administrator\\Desktop\\Output", "TargetType" : "1" } } “App-V to MSIX” and “Intune” conversions when the Output path is specified: (Json Body) { "PackageID" : "3", "Target" : { "TargetType" : "9", "OutputPath" : "D:\\Output" } } “App-V to MSIX” and “Intune” conversion without specifying Output path: (Json Body) { "PackageID" : "3", "Target" : { "TargetType" : "9" } } When the output path is not specified then it will consider the path configured in the respective Plugin options. |
| Method | POST |
| Parameters | List all parameters in the following format: PackageId = Id of the package in the Catalog. AACSettings = Location of the AAC project file. OutputPath = Location of the output generated. TargetType = Id of the Target Deployment Type. 1 - APPV 2 - XenApp 4 - MSI 5 - MSIX 6 - App-V to MSIX 9 - Intunewin |
| Connection Info | Provides the connection information of the package as mentioned in Setting Up Connection to Run REST APIs |
| Response | Example: http://localhost:8086/catalog/deploymenttypes/conversions Response: <data> <data> <Receipt xmlns:json="http://james\.newtonking\.com/projects/json" json:id="1"> <ReceiptID>4c942ee4-f471-4936-9d39-b88bbea0a115</ReceiptID> <FileName /> <GroupPath /> <ParentReceipt /> <PackageID>0</PackageID> <PackageRequestId>0</PackageRequestId> <NonPluginTestData /> <PackageConversionData /> <PackageFeedRequestData /> <PackageFeedAutomationRequestData /> <MonitorPackageAutomationRequestData /> <PackageFeedCustomRequestData /> <BacklogItemRequestData /> </data> </data> By using ReceiptID, you can see the transaction messages for the request. For more details, see Getting Status of a Request. |