Configuring the Backend

The application is configured using a JSON configuration file (appsettings.json) located in the Backend directory. The following subtopics explain the configuration entries that may require editing.

Insight database

To be guided through the configuration of the the Insight database to use, run the script RunBackendAdminTool.bat and select option 3.

To manually configure the Insight database to use, set the ServerName and DatabaseName properties of the InsightEnvironment object:

NOTE: The ServerName and InstanceName must be escaped by two backslashes, as shown in the following example:

"ServerName": "MYDBSERVER\\INSTANCE",

The database information may be left empty if the Insight client is installed on the same machine. In this case, the backend will use the information from the inSight.ini configuration file.

License server URL

The license server to use is configured with the LicenseServerUrl property of the LicensingConfiguration object:

As with the database information, the LicenseServerUrl property may be left empty if the Insight client is installed on the machine.

Backend service options

Insight Backend instances are visible in the inResponse Console under the Backend Services node.

The backend service options object determines the service name and host name shown in the inResponse console for the service instance:

If the MachineName property value is empty, the DNS name of the machine is used.

NOTE: Be sure to use different ServiceName values if more than one instance of the Insight Backend is configured to run in the same Insight environment.

Configure logging

The log file path and the master log level are configured with the BackendLogging object. This value must contain the full path to the log, including the file name, using double backslash characters, as shown in the following example:

When the LogFilePath property is empty, the backend writes the log to the file inSight.Backend.log in the temporary files folder of the service user account (usually %LOCALAPPDATA%\temp).

NOTE: Be sure to use different LogFilePath values if more than one Insight Backend instance runs under the same service account on the same machine. 

URL configuration

To configure the URL the web server listens on, edit the URLs property of the service configuration:

If using the HTTP.sys web server (as assumed throughout this topic), enter the same URL that was registered with HTTP.sys.

If using a URL other than localhost, make the following adjustments:

In ... \Insight\components.json:

 If using a full qualified domain name, make the adjustments as shown in the following example. The components.json example file should look like this:

NOTE: If the default option “http.sys” is used, you must start the Backend from the command line with the option “/useHttpSys”. Otherwise, the service will behave differently.

In …\Backend\appsettings.json:

NOTE: The "RequestTiming" option is used for debugging.

Additionally, change the “urls” setting in “appsettings.json” to: