Importing resources

Before you import, you must decide whether to empty the target repository before importing. If you select not to empty the repository, you must decide whether to overwrite existing resources in the target repository.

Cleaning the repository before importing

If you select to empty the repository before importing, all resources in all areas (Message store, Security, Composer and Composition Center) are removed from the repository before data is imported from the zip file.

If there are dependencies to other areas, e.g. Document Broker, all these messages must be processed or removed separately before you import. If stored Messages are included in the export (Message store area), the recommendation is to process as many Messages as possible before the export.

If you intend to import into a newly created repository, please note that the repository contains default and basic data from start, i.e. it is not empty.

Overwriting resources when importing

•	If you select to overwrite existing resources, all rows are imported from the zip file. Existing rows in the repository are replaced by the corresponding rows imported from the zip file.

•	If you select not to overwrite existing resources, only new rows are imported from the zip file.

To import resources

1	Click the Runtime Repository category button.

2	In the Import section, click Browse. A file browser opens.

3	Browse to the zip file to import and click Import. The import path is displayed in the Import from field.

4	Select whether to Empty the repository before importing, and whether to Overwrite existing matching data.

5	Click Import. Data is imported to the repository.

Log for import failures

Errors during the import are logged in strs-rtmt.log and import-failures.log. You will find the log files in:

<user_home>\dbadmintool-files