Importing resources – do not clean up repository before importing

When you upgrade to 5.6, you must migrate the data from the old runtime repository to the new 5.6 runtime repository. In this case you must run the Repository Migration Tool in IMPORT mode. See the Upgrading Instructions for more information on how to upgrade to 5.6.

When you import resources to a runtime repository, you import the resources from the zip file exported from the source repository. You can specify whether to include resources in all areas (Composer, CompositionCenter, and Security), or in specific areas only.

Note:

You must always include the Security area.

In this mode, security data and resources in the selected areas (Composer and/or CompositionCenter) are NOT removed from the repository before data is imported from the zip file.

Example 13

Importing data (MSSQL)

strs-migrate.bat -d MSSQL -m IMPORT -n strsDataSP3 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip

 

Example 14

Importing data (Oracle)

strs-migrate.bat -d ORACLE -i abc321 -m IMPORT -n strsDataSP3 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip

 

Forcing data into the runtime repository

By default, Repository Migration Tool will only import rows with primary keys that do not already exist in the runtime repository. This means that only new rows may be inserted, and no data will be overwritten. If you want to overwrite data in the runtime repository, you can use the -f (--force) parameter.

Example 15

Forcing data into a runtime repository (MSSQL)

strs-migrate.bat -d MSSQL -f -m IMPORT -n strsDataSP3 -o 1433 
-p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip

 

Example 16

Forcing data into a runtime repository (Oracle)

strs-migrate.bat -d ORACLE -f -i abc321 -m IMPORT -n strsDataSP3 
-o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip