Import Export Best Practices

Import and export of packages is typically used to move a package the from a development environment to a test environment, or from a test environment to a production environment.

In order to avoid failures during this process, review these best practices:

Domain requirements – A package can only be imported in the same domain as it was exported. Therefore:
1. (Required) Ensure the same domain exists in the target import server before the import action takes place.
2. (Required) Ensure you create domains in the same order in both export and import server environment. This shared ordering ensure that an internal ID assigned to the domain exists in both server environments. Verify the internal ID assigned to a domain by looking at the prefix used in the package folder of the exported file.
Server connection isolation – Only import a package if server connections used by MBOs and Operations in the package do not already exist. If you rely on import/export for package transport between systems, create server connections for dedicated use within one package and thus isolated from other packages. This enables deletion of the package and its server connections for subsequent import to be successful.
First deployment restrictions – The export/import functionality is intended for use in the first deployment of an MBO package. Import is only successful when the MBO package and server connections used in the package do not already exist in the target domain. Unwired Server prevents existing package and server connections form being overwritten by certain deployment methods including import. This restriction ensure the compatibility of the changes from client application perspective.
If this is not the first instance the best practice is to then use an appropriate deployment method instead of using import. Perform deployment in update mode (with verification), which ensures that only compatible changes are allowed to update an existing package.
Versioning recommendations – If a developer has updated the package version number, follow these recommendations:
1. (Required) Verify that this new package version is added to the application.
2. (Recommended) Use the update mode over import whenever possible. If it is not possible, delete the existing package and server connections before importing. This delete action removes all runtime data for the package including cached data, registered subscriptions, subscription templates, client log, MBO/Operation history, and registered package users. Therefore, such deletion should be done only after serious consideration.