|
|
System Migration |
|
|
|
||
System Migration |
|
|
|
|
|
|
System Migration |
|
|
|
||
System Migration |
|
|
|
|
|
|
||
In the System migration section you can transfer settings from a QPR 8.0/8.1 installation into QPR 2017.1 or perform additional operations to the QPR 2017.1 database. Some fields are pre-filled if this section is opened from the QPR 2017 installation.
The Source INI file path field defines the folder where QPR 8.0/8.1 settings files (qpr.ini, actiontypes.ini, and terms.ini) are located. When this value is defined by the installation, the default instance is used, so you need to change the value in the case you want to migrate a different instance.
The Target INI file path field defines the folder where QPR 2017.1 settings files (QPR_Servers.ini, actiontypes.ini, and terms.ini) are located.
In the Migrate INI files section you can select which of the three settings files to migrate:
•QPR.ini: The main configuration file. Applicable contents will be included in QPR_Servers.ini in QPR 2017
•Actiontypes.ini: Action types available in QPR Portal
•Terms.ini: Terminology customization file
The files are selectable in the case the corresponding files are found in the source folder and the target folder is defined.
In the Source database section you can define the QPR 8.0/8.1 data source from which data is migrated to QPR 2017.1. Define the data source and the user name and password (if any) required for the database into the corresponding fields. When the migration is launched from the installation, these values are read from the default QPR 8.0/8.1 instance.
In the Target database section you can define the QPR 2017.1 data source into which data is imported from QPR 8.0/8.1 or to which additional operations are performed. Define the data source and the user name and password (if any) required for the database into the corresponding fields. When the migration is launched from the installation, the 2017 demo database is suggested as the default.
Warning |
Any possible QPR tables in the target database are overwritten, so make sure the database is either empty or you have up-to-date backup copies. |
In the Options for database migration section you can select additional operations to be performed during the database migration:
•Migrate QPR ProcessGuide custom attributes: This option merges possible duplicate (i.e. name, description and other information match) custom attribute types into one, which is linked to all element types that were using the previous duplicate versions. This setting is useful if you have duplicate custom attribute types originating from e.g. a database or file models created with QPR 7.5 or older. You can use this option also when you have only the target database defined.
•Migrate QPR ProcessGuide web publishing options: This option converts the old web publishing options into web styles, and overwrites any existing global web styles in the database. Settings will be imported to QPR Modeling Client.
Warning |
Make sure to have full backups of the QPR 2017.1 database before using the migration options. |
When the desired options are selected, click Run Migration to start the migration. After the migration is completed, you can choose to view the log file to see which operations were performed.
Note |
After migration, before QPR Portal is taken into use, all published models must be opened once in QPR Portal, so that QPR Web Application Server can create cache files. This can be done by manually opening the models or by configuring WAS to load all models at start up. |
