FlexNet Code Insight 2018 R3 Upgrade Guide

[#1]

Summary

This article documents the procedure to upgrade to FlexNet Code Insight 2018 R3 from FlexNet Code Insight 2017 R1 and above

Synopsis

This upgrade procedure is applicable only when migrating FlexNet Code Insight version 2017 R1 or later to the latest version. It does NOT apply to Code Insight v6 migration.
In the following procedure, vCurrent refers to the version of FlexNet Code Insight (for example, FlexNet Code Insight 2017 R3 SP1) that is currently installed, and vNew refers to the latest version of FlexNet Code Insight (for example, FlexNet Code Insight 2018 R2) to which you want to upgrade.

Please note the following:
? For a product upgrade, do not use the FlexNet Code Insight Installer. Instead, download the zip Archive version of the FlexNet Code Insight 2018 R3 release and follow the step-by-step instructions in the next section.
? Ensure that you backup the database schema prior to upgrade. Note: The database schema does not need to be installed again. You only need to point to the existing database installation and copy some files to the vNew directory.
? Any time you receive a new codeinsight.key file, such as when you are upgrading from an evaluation version to a full version of FlexNet Code Insight or renewing an expired license, it may be necessary to change the encrypted password in the core.db.properties file to its unencrypted plaint-text form. Perform this step prior to starting Tomcat.

1. Open <vCurrent>\config\core.db.properties file with a text editor.
2. Change the db.password= entry to the following: db.password=<Database_Password>, for example: db.password=MyPassword
3. Save the core.db.properties file.
4. Restart the Tomcat server.

? FlexNet Code Insight no longer allows uppercase or mixed case when entering the application?s URL. To start FlexNet Code Insight in a browser, you must enter codeinsight in lowercase.
? For existing scan agent installations (e.g. the Jenkins plugin), remove the scan agent index on the remote agent server to force an install of the latest plugin included with the release. This will create a new index.
? If you have any customized property files (e.g. a customized codeaware.properties file) in your vCurrent installation, be sure to copy the file to the same location in the vNew directory.
? The initial scan or rescan of an existing project may take longer due potential re-indexing of projects and pre-scan download of NVD data.
? Plugin backwards compatibility to older Code Insight versions is not guaranteed. Each plugin is only compatible with the Code Insight version that it is shipped with. If necessary, install the new plugin and reconfigure it based on the instructions provided with the release.
? This release of Code Insight ships with a copy of the 7-zip tool for extraction of archives on the Code Insight server, as well as on the scan agent server where a Code Insight plugin is installed (e.g. for a Jenkins plugin this would be the Jenkins build server). If you already have a plugin installed, verify that 7-zip is included on the scan agent server. If missing, copy 7-Zip from <vNew>\7-zip to the scan agent server. Also, ensure that the environment variable CODEINSIGHT_ROOT is correctly set on the scan agent server to point to the top-level location of 7-Zip.