Import and export data

This topic contains instructions for importing and exporting Application Deployment data from Server Automation (SA). It contains the following topics:

• Working
• Special considerations

Working

You can export Application Deployment data to an XML file or import data from an XML file. This is useful when you want to copy or move your Application Deployment data from one SA core to another, back up your data for archival purposes, or create an Application Deployment scenario using scripts.

The following items are imported and exported:

• Lifecycles
• Environments
• Applications
• Application Groups
• Tiers and Tier Groups
• Releases
• Components
• Scripts
• Source Types

You can preview the results of a potential import to see what would be created and determine whether any conflicts (collisions) would occur with existing Application Deployment data.

You can import or export the entire Application Deployment database, or you can import or export specific applications. When you import or export a specific application, all items associated with that application—releases, lifecycles, environments, source types, components (including rollback and undeploy scripts, if applicable), and tiers—are included.

Special considerations

The following items are not exported:

• Release versions
• Deployment jobs
• Targets or target groups
• Environment pre- or post-deployment flows
• Application Settings (on the Administration screen)
• Application permissions
• Environment permissions
• SA library objects (Software Policies, Application Configurations, and Packages)
• HPE OO flow content or definitions
• These items also cannot be imported.

Because you cannot import or export release versions, there is no way to import or export delta release information.

For an import operation, if an SA library item does not exist on the SA Core where the import is performed, that item will not be visible in the object that contains it. For example, if a tier has a policy, and that policy does not exist on that SA Core, the policy will be blank.

You can specify what happens if a conflict is encountered during an import operation: skip the item or overwrite it. The default behavior is to skip the item and continue the import. If you specify --importConflict overwrite, however, conflicting items are updated based on the contents of the import XML file.