An approach to software development lifecycle operations for Cloud Application Integration assets

Back Next

Export files

The export file includes a spreadsheet that lists the objects within the file.

The following image is an example of an export spreadsheet:

The export spreadsheet includes columns for the path, name, type, and ID for each object.

Export file structure

The export file retains the file structure of the source organization's

Explore

page for projects, folders, and assets. The Explore folder contains assets in the XML format. If you exported Data Integration assets, you see a SYS folder with connections and runtime environments.

The following image shows the contents of an export file:

The image shows the Explore folder with the AccountsByArea project folder and the connections and October 2018 folders within the project folder.

The following image shows the contents of the

Explore\AccountsByArea\connections

folder:

The directory has three connections in the XML format.

The following image shows the same folders in the AccountsByArea project of the source organization's

Explore

page:

The following image shows the assets contained within the connection folder of the source organization's

Explore

page:

There are three connections within the sub folder.

Object names

Each asset is contained in a ZIP file along with its associated metadata and JSON file. The ZIP file includes the asset name appended by the asset type.

For example, a mapping with the name of m_totals in the source organization has the name of m_totals.DTEMPLATE in the export file. When you export the m_totals mapping to the target organization, the asset has its original name of m_totals.

The following table lists the asset types and the associated extension appended to asset names: