Administrators can define packages to exchange resources between different Adobe Campaign instances through structured XML files. These can be configuration parameters or data.
This may be useful for transferring data from one server to another or for replicating the configuration of an instance.
Packages are available under the Administration > Deployment > Package exports or Package imports menus. The two menus function similarly.
The elements of each list are displayed by default according to their modification or installation date, from the most recent to the least recent.
Platform and Administration are two built-in packages, each containing a predefined list of resources to be exported. They can be opened in read-only mode and they are only suitable for exporting.
Exporting packages is not authorized if the resources exported have default IDs. Therefore, the IDs of exportable resources must be changed by using a name that is different from the templates provided as standard by Adobe Campaign Standard. For example, to export test profiles, an ID containing the value "SDM" or "sdm" must not be used. When trying to export packages containing default IDs, you can see errors such as: "The 'Brands (branding)' entity type uses a default ID ('BRD1') that may cause a conflict when importing the package. Change this name and repeat the operation."
The package export steps are described in the Exporting a package section.
The contents of these two packages cannot me modified. In contrast, these packages always contain the most up-to-date data available. You can create your own packages to export specific elements.
Exporting a package allows you to save a specific state of a resource that you will be able to reimport on another instance or later on the same instance.
Exporting packages is not authorized if the resources exported have out-of-the-box IDs. Therefore, the IDs of exportable resources must be changed by using a name that is different from the templates provided as standard by Adobe Campaign Standard. For example, to export test profiles, an ID containing the value "SDM" or "sdm" must not be used.
The exported file is stored in the download folder of the browser in use. It is automatically named "package_xxx.xml", whereby "xxx" corresponds to the package ID.
When selecting an element from the package content list that has already been exported, the Log and Last export tabs are still available.
The package import list above anything contains the automatic imports linked to updates performed by Adobe.
The Execution logs tab stores all of the import steps. A side panel displays the general information.
These elements are accessible in read-only mode.
An administrator can manually import a package originating from an export executed earlier from an Adobe Campaign instance. For more on this, refer to the Package exports section.
The manual package import consists of two steps: first, you have to upload a file, then you can import its content.
Once a package has been imported, you cannot re-import it from the same element. You can only modify its label and ID.