Import a backed-up Interchange system configuration

Use this procedure to import compressed files containing the backed-up configuration, communities, and partners for Interchange. You can import the Interchange configuration to the same instance of Interchange where you created the backup, or to a new instance with a new database. If you import to the same instance, you need to select the import mode for existing objects.

Before you begin

To successfully import a system backup, the platform to which you are importing the backup must have a valid Interchange node.

  • If you are importing to the same instance, all nodes are reconstructed with the configuration contained in the zip file.
  • If you are importing to a different instance (i.e. a different Interchange node name), none of the processing node configuration is imported.

In addition, consider the following before performing the import:

  • If the system configuration you are importing contains file path definitions defined in various objects, the import attempts to re-create them. If the user running Interchange has the appropriate rights, it succeeds. If not, the import succeeds but the created objects refer to non-existing paths that result in processing errors if used without modification (or manual creation of the referenced paths).
  • The system backup is a compressed file containing multiple XML files. Normally, you import the compressed file. It is possible to uncompress the backup file and import the XML files individually. However, such importing can be done only through the Interchange profile management API (PMAPI). You may need the help of Axway Professional Services consultants to use the API.

Peer Network limitation

Peer Network auto-cloning will not occur for the objects you import through the system import feature.

Workaround: After you execute a system import and restart Interchange, if you have Peer Network auto-cloning configured, you can force peer cloning by re-saving the objects that you want to clone.


  1. In the user interface, select System Management > System Management.
  2. Click the task Import entire system profile near the bottom of the page.
  3. Browse to the location where you stored your backup and select that file, or type the full path including the backup file name.
  4. Enter the password used by the export to protect private key certificates in both the Password and Confirm password text boxes.
  5. Select whether to update, ignore, or replace existing objects.
  6. Click Next to import the file. The Import entire system results page displays details about the imported configuration.
  7. Click Finish to exit.

Related topics

Related Links