FNMS Integration with ServiceNow - Installations Missing in ServiceNow
After performing a full applications export from FNMS to ServiceNow, there are missing installations in ServiceNow which exists in FNMS. The applications do not exist in the staging table for ServiceNow, indicating that it was not brought in by the export from FNMS.
By default, the configuration for data transfers from FNMS to ServiceNow limits the number of records of each data type to be included in the transfer. For applications export, this number is 10,000,000.
The following Online Help article lists the default configured limit for data transfers between FNMS and ServiceNow
To check whether you are running into this limit, the following query can be run against the FNMSCompliance database to get an estimate number of records to be exported:
SELECT count(*) FROM( SELECT SoftwareTitleID, ComplianceComputerID, ComplianceHistoryTypeID, HistoryDate, ROW_NUMBER() OVER (PARTITION BY ComplianceComputerID, SoftwareTitleID ORDER BY HistoryDate DESC) AS RowRank FROM ComplianceHistory WHERE ComplianceComputerID IS NOT NULL AND SoftwareTitleID IS NOT NULL AND ComplianceHistoryTypeID IN (4, 5) ) AS hist WHERE hist.RowRank = 1
If it has been determined that you are running into the record limit, the value can be adjusted to allow additional rows to be exported. The following steps will set the row limit for applications export to unlimited:
1.Navigate to the ServiceNow Export folder on the FNMS Application Server, which is by default at:
C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\DotNet\bin\ServiceNowExport
2.Open the Export configuration file with notepad: fnmp_servicenow_export.exe.config
3.Change the maxRows limit to -1 for unlimited applications within the <application /> node.
The following Online Help article discusses all the configuration options and defaults for fnmp_servicenow_export.exe.config file