Sign into Packager and accept the EULA. Do not sign out while using the automation process.
Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.
We recommend that you use the create package workflows provided in the Adobe Admin Console.
See how to create Named User Licensing packages and Shared Device Licensing packages.
You can automate the creation of the packages. Using an input XML file that specifies the various settings and options in the package, you can automate the package creation with Creative Cloud Packager.
Sign into Packager and accept the EULA. Do not sign out while using the automation process.
Create an XML file with the following options specified in it.
Your XML file should conform to the attached XSD (schema): pkgConfigFile.zip.
In the input XML file, if you set the appsPanelEnabled flag for false, then you must also set the adminPrivilegesEnabled flag to false.
Example 1: The following XML file automates creation of a serialized package that includes all entitled latest updates:
<CCPPackage> <CreatePackage> <packageName>AllLatestUpdates Package</packageName> <outputLocation>C:\Temp\CCPPkg.9a137bb2-d7b4-4302-bf90-e9f89c502afa\WIN32\mul</outputLocation> <is64Bit>true</is64Bit> <customerType>enterprise</customerType> <organizationName>Adobe Production Validation: GAR</organizationName> <matchOSLanguage>true</matchOSLanguage> <rumEnabled>true</rumEnabled> <updatesEnabled>false</updatesEnabled> <appsPanelEnabled>true</appsPanelEnabled> <adminPrivilegesEnabled>false</adminPrivilegesEnabled> <serialNumber>11111111111111111111111</serialNumber> <ProductCategory>AllLatestUpdates</ProductCategory> <IncludeUpdates>true</IncludeUpdates> <Language> <id>en_US</id> </Language> </CreatePackage> </CCPPackage>
Example 2: The following XML file creates a team device pool package with all latest updates:
<CCPPackage> <CreatePackage> <packageName>All Product Package</packageName> <outputLocation>C:\Temp\CCPPkg.9a137bb2-d7b4-4302-bf90-e9f89c502afa\WIN32\mul</outputLocation> <is64Bit>true</is64Bit> <customerType>team</customerType> <organizationName>Adobe Production Validation: GAR</organizationName> <matchOSLanguage>true</matchOSLanguage> <rumEnabled>true</rumEnabled> <updatesEnabled>false</updatesEnabled> <appsPanelEnabled>true</appsPanelEnabled> <adminPrivilegesEnabled>false</adminPrivilegesEnabled> <devicePoolName>Complete</devicePoolName> <ProductCategory>AllLatestProducts</ProductCategory> <IncludeUpdates>true</IncludeUpdates> <Language> <id>en_US</id> </Language> </CreatePackage> </CCPPackage>
Example 3: The following XML file creates an enterprise named package with a custom list of products and updates:
<CCPPackage> <CreatePackage> <packageName>Custom Package</packageName> <outputLocation>C:\Temp\CCPPkg.9a137bb2-d7b4-4302-bf90-e9f89c502afa\WIN32\mul</outputLocation> <is64Bit>true</is64Bit> <customerType>enterprise</customerType> <organizationName>Adobe Production Validation: GAR</organizationName> <matchOSLanguage>true</matchOSLanguage> <rumEnabled>true</rumEnabled> <updatesEnabled>false</updatesEnabled> <appsPanelEnabled>true</appsPanelEnabled> <adminPrivilegesEnabled>false</adminPrivilegesEnabled> <ProductCategory>Custom</ProductCategory> <IncludeUpdates>true</IncludeUpdates> <Language> <id>en_US</id> </Language> //Add the products tag for a custom list of products to be deployed. Inside the Products tag add a Product tag for each of the products to be deployed and specify its sap code and version in it <Products> <Product> <sapCode>AEFT</sapCode> <version>12.0</version> </Product> </Products> //Add the HDUpdates tag for a list of updates to be deployed for products that can be installed without their base versions. Inside the HDUpdates tag add an HDUpdate tag for each of the updates to be deployed and specify its sap code and version in it <HDUpdates> <HDUpdate> <sapCode>AEFT</sapCode> <version>13.8.1</version> </HDUpdate> </HDUpdates> //Add the Updates tag for a list of updates to be deployed for products other than the products that can be installed without their base versions. Inside the Updates tag add an Update tag for each of the updates to be deployed and specify the update's refId in it <Updates> <Update> <refId>AdobePhotoshopCC2015-16.0/16.1.2</refId> </Update> </Updates> </CreatePackage> </CCPPackage>
To specify a custom list of products to be deployed in the XML file, add the Products tag. For each of the products to be deployed, add a Product tag and inside it specify the Sap Code (<sapCode>) and Version (<version>) for each of the products to be deployed. The sap code and versions for the applications that can be deployed without their base versions are listed on this page. For other applications, you can view the Sap Codes and Versions on the CCP Application screen.
To specify a custom list of updates in the XML file, you need to enter one of the following:
Optionally, you can use the following customizations in the XML:
Run the PDApp with the following parameters specified:
Parameter |
Value |
Path of the PDApp executable |
Specify the path of PDApp executable on your machine in double quotes Mac: Applications/Utilities/Adobe Application Manager/core/Adobe Application Manager.app/Contents/MacOS/PDApp Win: C:/Program Files/Common Files/Adobe/OOBE/PDApp/Core/PDApp.exe |
--appletID |
CCP_UI |
--appletVersion |
1.0 |
--workflow |
ccp |
--automationMode |
ccp_automation |
--pkgConfigFile |
Name and path of the XML package configuration file as created in step 1. |
Following is an example of command for Windows.
"C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\PDapp.exe" --appletID=CCP_UI --appletVersion=1.0 --workflow=ccp --automationMode=ccp_automation --pkgConfigFile="<path of input XSD>"
The package gets created. In the same path as your input XML file, another XML file gets created with the name [pkgConfigFileName]_result.xml.
In case of any errors, you can use the [pkgConfigFileName]_result.xml file for more information on the errors and debugging the errors. PDApp and other logs are created as usual.
Sign in to your account