Configuration Details
FlexNet Code Insight 6.13.2
Configuring additional FlexNet Code Insight Scan servers is similar to configuring the first FlexNet Code Insight Scan server with a few exceptions. For each additional Scan Engine server, do as follows:
|
1.
|
Register each additional FlexNet Code Insight Scan server on the Core server. |
|
2.
|
In core.properties (<Code Insight_ROOT_DIR>\<version>\config\core\) on the Core server, add an alias for the new FlexNet Code Insight Scan server and define the associated properties. Separate multiple aliases with commas. |
scan.server.aliases = <ALIAS1>, <ALIAS2>, <ALIAS3>
scan.server.<ALIAS>.web = http://<SCAN_SERVER_IP_ADDRESS1>:<HTTP_PORT>/Code InsightScanEngine
scan.server.<ALIAS2>.web = http://<SCAN_SERVER_IP_ADDRESS2>:<HTTP_PORT>/Code InsightScanEngine
scan.server.<ALIAS3>.web = http://<SCAN_SERVER_IP_ADDRESS3>:<HTTP_PORT>/Code InsightScanEngine
|
3.
|
Modify the configuration files on each additional FlexNet Code Insight Scan server. The configuration changes required to configure additional FlexNet Code Insight Scan servers are as follows: |
|
a.
|
The core.db.properties (<Code Insight_ROOT_DIR>\<version>\config\core\) file defines the database connection details for use by the FlexNet Code Insight Scan server. Copy this file from the FlexNet Code Insight Core server. This is the only file required in the core directory on each remote FlexNet Code Insight Scan server. |
|
b.
|
Update scanEngine.properties (<Code Insight_ROOT_DIR>\<version>\config\scanEngine\) with your scan server settings:: |
|
c.
|
Set the coreServerUrl to point to your FlexNet Code Insight Core Server URL. |
|
d.
|
Set serverURL to point to the URL of the FlexNet Code Insight Scan server you are configuring. |
|
e.
|
Set the scanServerName to the alias name of the server you are configuring from core.properties on the Core server, denoted as <ALIAS> in Step 2, that registers this instance of the FlexNet Code Insight Scan server |
|
4.
|
Copy the FlexNet Code Insight Key to each FlexNet Code Insight Scan server. Contact Flexera Software if you need to obtain a key. |
Note • FlexNet Code Insight Analyzer requires a new key with data services enabled.
|
5.
|
Copy the FlexNet Code Insight Data libraries to each additional FlexNet Code Insight Scan server. See Installing the Compliance Library for additional information. |
|
a.
|
Only the FlexNet Code InsightScanEngine directory (exploded war file) is required in the Tomcat web applications directory (<Code Insight_ROOT_DIR>\<version>\tomcat\webapps). |
|
b.
|
Remove the FlexNet Code Insight directory before starting Tomcat. |
|
c.
|
Ensure that the Tomcat cache is flushed. You can do this by removing all contents from the <Code Insight_ROOT_DIR>\<version>\tomcat\work\Catalina\localhost\ directory. |
Visit the FlexNet Code Insight Customer Community at https://flexeracommunity.force.com/customer/CCContactSupport for assistance if you need to generate custom source code fingerprints on multiple servers.
Open topic with navigation