...
The following guide lays out a step-by-step procedure to migrate the scan-engine to use a different back-end database connection.
Please note that it is not recommended to migrate the database to a new server and upgrade between versions of iQSonar in one step.
Migrate a single-scan-engine installation
...
- Pause all active projects, and wait until the server is idle
- stop the iQSonar ScanEngine service
- Back up the iQSonarSE database from the old server
- Restore the iQSonarSE database to the new server
- Make a backup of your iqsonar.key file, and your iQuate.iQSonar.ScanEngine.exe.config files. These are found in the folder "C:\Program Files\iQuate\iQSonar ScanEngine 4.0\bin" in a default installation.
- Uninstall iQSonar, and then delete the folder “C:\Program Files\iQuate\iQSonar ScanEngine 4.0\”
- Install the new version of iQSonar using a “custom” install, but make sure you do not allow it to start the service. When prompted for the iqsonar.key, point to the location of the key you backed up in step 5
- In Notepad or Notepad++, open the iQuate.iQSonar.ScanEngine.exe.config you backed up in step 5. This is copy 1 of the config file.
Run Notepad or Notepad++ as an Administrative user, and open the new Restore the copy of iQuate.iQSonar.ScanEngine.exe.config in to the C:\Program Files\iQuate\iQSonar ScanEngine 4.0\bin folder. This is copy 2 of the config file. - From copy one of the config file, find the section <appSettings file="user.config">, and copy the following keys over into copy 2, replacing the values for any keys that already exist, and adding in new keys for the ones that don’t exist:
- KSitePrivate
- KSitePublic
- KSiteSignature
- installation-uuid
- Save copy 2 of the config file.
- ONLY NOW can you start the service.
- Once the service has started, you can log in to the UI and unpause the project.
...
- Pause all active projects, and wait until the server is idle
- Stop the iQSonar ScanEngine service on all servers
- Back up the iQSonarSE database from the old server
- Restore the iQSonarSE database to the new server if you are migrating the DB to a new location.
- We will upgrade the scan engine server which hosts the User Interface first.
- Make a backup of your iqsonar.key file, and your iQuate.iQSonar.ScanEngine.exe.config files. These are found in the folder "C:\Program Files\iQuate\iQSonar ScanEngine 4.0\bin" in a default installation.
- Uninstall iQSonar, and then delete the folder “C:\Program Files\iQuate\iQSonar ScanEngine 4.0\”
- Install the new version of iQSonar using a “custom” install, but make sure you do not allow it to start the service. When prompted for the iqsonar.key, point to the location of the key you backed up in step 5. Ensure you have the correct database settings for the new database location/credentials.
- In Notepad or Notepad++, open the iQuate.iQSonar.ScanEngine.exe.config you backed up in step 5. This is copy 1 of the config file.
Run Notepad or Notepad++ as an Administrative user, and open the new Restore the copy of iQuate.iQSonar.ScanEngine.exe.config in to the C:\Program Files\iQuate\iQSonar ScanEngine 4.0\bin folder. This is copy 2 of the config file. - KSitePrivate
- KSitePublic
- KSiteSignature installation-uuid
- From copy one of the config file, find the section <appSettings file="user.config">, and copy the following keys over into copy 2, replacing the values for any keys that already exist, and adding in new keys for the ones that don’t exist (Note: the installation-uuid is different for each scan engine. The other three values should be consistent across all your servers):
- Save copy 2 of the config file.
- Restart the service on the UI server. This should upgrade the DB.
- Wait until the DB has finished upgrading and the version-number shown for the scan-engine in the UI is correct.
- Repeat step 5 a – g d for all other scan engines, without starting the service on the servers.
- Once all the scan engine servers -engines have been upgraded, and the database upgrade has been completed by the UI servermigrated, THEN you can restart the service .
At this point touch base with iQuate support staff to double check if there are any additional SQL commands to be executed.Verify that all your scan engines display the correct build number in the UIon all the servers. - Now you can unpause any projects which were paused in step one.
...