Inventory Connection to ServiceNow

ServiceNow can be used as an inventory source from which you can import the raw hardware and software inventory "discovered" by ServiceNow. (In IT Asset Management, the term "discovery" refers only to finding devices on the network; but ServiceNow tends to use that term to include the collection of inventory information.)

There are two sides to the ServiceNow inventory connector:

Side #1—ServiceNow must be configured to export the inventory details to .csv files saved on a MID server of your choice. This requires:
Setting up the Flexera Integration application
Making sure that there is a suitable account configured to run that application
Scheduling operation of the integration application.
Side #2—On an inventory beacon in your IT Asset Management implementation, a simple PowerShell connector reads data from the saved .csv files on the MID server, and uploads it for import into your software asset management system.

For full details (including setup procedures), see the ServiceNow Inventory Connector section of the Inventory Adapters and Connectors Reference. The process below provides a high-level summary of steps in ServiceNow, and goes into more detail about configuring the connector on the inventory beacon.


Select an inventory beacon that meets these requirements:

Inventory Beacon Requirements for Connection to ServiceNow



FlexNet Beacon

An installation of FlexNet Beacon 16.0.0 or later is required, with good network access to your chosen ServiceNow MID server on the one hand, and to the central application server for IT Asset Management on the other.


PowerShell 5.1 or later is running on Windows Server 2012 or later, or Windows 7 SP1 or later is required.

PSModulePath variable

The Microsoft Windows environment variable PSModulePath must be set to include the following path:


Creating an Inventory Connection to ServiceNow

To create an inventory connection to ServiceNow:

1. Obtain the Flexera Integration application:
a. Log into the ServiceNow Store with ServiceNow HI credentials.
b. Search for, and select, Flexera Integration, and in the right pane, click Get, and then Continue.
c. On the purchase page, minimize costs by making the integration application available only on the specific ServiceNow instance(s) where the collection of inventory details is required.
d. Accept the T&Cs and click Get.
2. Log into your chosen ServiceNow instance using an account with administrator privileges.
3. Complete installation of the Flexera Integration app:
a. Navigate to the Applications list.
b. Click the Downloads tab.
c. Scroll to the Flexera Integration application, and click Install.
4. Create your ServiceNow integration user account:
a. Navigate to User Administration > Users.
b. Click New, complete the properties for your new user, and click Submit (noting the user ID and password for later use).
c. Click the hyperlinked User ID, scroll to Roles, and click Edit.
d. Select x_fls_flexera_fnms.admin and add to the Roles List, and click Save.
5. If you have not already done so, set up the MID server that stages the inventory data from ServiceNow:
a. In the navigation bar, expand MID Server and click Downloads.
b. Click the link for your platform.
c. In the navigation bar, in the MID Server group, click Installation Instructions, and click the link appropriate to your version of ServiceNow. Step through the instructions to complete installation of your MID server (and take note of its name for later use).
d. Use the Validate the MID Server link on the installation page.
6. Schedule the export of inventory data to your chosen MID server:
a. Navigate to Flexera Integration > Integration Properties, scroll down to the MID server name field, and enter the full name of your MID server.
b. Optionally, in the Enter file path field, create an alternative location for saving the exported .csv files.

If you do not do this, the default location is the export folder in the MID server installation folder. The inventory beacon must have access rights to your chosen folder (file share), so that it can read the data from the saved .csv files.

c. Click Save.
d. Navigate to Flexera Integration > Advanced > Scheduled Data Exports.
e. In turn, select each of the following jobs, and change the Run field to your desired schedule:
Flexera Scheduled Computer Export
Flexera Scheduled Software Export
Flexera Scheduled Software Install Export

As exported files may grow quite large (depending on the volume of inventory collected by ServiceNow), do not schedule more frequently than really required. A weekly export is commonly sufficient in a stable environment.

f. Click Update to save changes, and repeat for remaining jobs.
g. On the Scheduled Script Execution page, click Execute Now to test each export. Monitor progress in ServiceNow by navigating to Flexera Integration > Export History > Export Runs.
h. Check the .csv files saved on the MID server.
7. Ensure that your ServiceNow configuration includes at least the Discovery plugin, and preferably also the SAM plugin (for example, use the navigation Search field to search for "Discovery", and so on). You can then log out of ServiceNow.
8. In the FlexNet Beacon interface, ensure that you have your preferred schedule for imports from Salesforce set on the appropriate inventory beacon:
a. Log into the inventory beacon interface as an administrator (for example, in the Windows Start menu, search for FlexNet Beacon, right-click it, and select Run as administrator).

Tip:Remember that you must run the inventory beacon software with administrator privileges.

b. From the Data collection group in the navigation bar, choose Scheduling.
c. If there is not already a suitable schedule in the list, click New... and complete the details (see the help topic for that page for more information). Otherwise, identify the schedule you will use.

Tip:A custom schedule may be helpful, particularly if you have chosen weekly exports of inventory data from ServiceNow. There is no point in scheduling repetitive uploads of unchanged .csv files, as these just create unnecessary system load. A useful schedule triggers shortly after the last of the ServiceNow export tasks, and sufficiently ahead of that night's central inventory import and license compliance calculations to allow for data collection, upload to the application server, and import to the staging tables.

9. Select the Inventory Systems tab (in the same navigation group).
10. To create a new connection, click the down arrow on the right of the New split button, and choose Powershell.
11. Complete (or modify) the values for the following required fields:
Connection Name—Enter a name for the inventory connection. The name may contain alphanumeric characters, underscores or spaces, but must start with either a letter or a number. Making the name meaningful within the first few characters helps when it is displayed in narrow columns. When the data import through this connection is executed, the data import task name is same as the connection name.
Source Type—Select ServiceNow from this list.

On inventory beacon versions 16.0.0 and later, two additional sets of controls (for test mode, and filter for overlapping records) appear in the lower part of the same dialog. (The proxy server settings remain disabled, as these cannot apply for this connector.)

12. Ensure that the Source Folder field contains the absolute path to the folder on the MID server where the .csv files are saved (refer back to step 6 for the folder name).
13. If your inventory beacon is version 16.0.0 or later, in the Overlapping Inventory Filter section, choose what action the importer should take if inventory for the same server(s) is returned from another source as well as from ServiceNow.
14. When all data is complete, click Test connection.

You cannot save the connection details if the connection test fails. Either:

If the Test connection fails and displays an error message:
a. Click OK to close the message.
b. Review and correct the connection details.
c. Retest the connection (and repeat until your changes are successful, in which case click OK and resume from the next step).
d. If you cannot get the connection test to succeed, click Cancel to cancel the addition of these connection details, and seek further assistance.
If the inventory beacon can successfully access the MID server folder using the details supplied, a Test connection succeeded message displays. Click OK to close the message, so that your new connector is displayed in the underlying list of connectors.
15. In the FlexNet Beacon PowerShell Source Connection dialog, click Save to save the connection.
16. Select your new connection from the displayed list, and click Schedule....
17. In the dialog that appears, select the name of your chosen schedule for inventory collection through this connection, and click OK.
18. At the bottom of the FlexNet Beacon interface, click Save, and if you are done, also click Exit.

Validating Your Configuration

To validate your configuration:

1. Wait until after the next scheduled execution of the ServiceNow export through the Flexera Integration application.
2. Then, on the ServiceNow MID server, use the File Explorer to check the contents of the output folder (by default, the export folder under the MID Server software installed directory, although you may have customized this location). You should see three .csv files (these file are not cleaned up between exports, and are over-written next time):

Tip:If you are not using the SAM plugin with ServiceNow, this exported flexera_software_install_export_set.csv file will be empty.

The presence of these well-formed .csv files confirms that all the configuration elements on the ServiceNow side are correct.

3. After the overnight inventory import and license consumption calculations, navigate in IT Asset Management to the All Inventory page, and apply a simple filter to the Last inventory source column, where the column contains ServiceNow.

The first-time appearance of even one entry with that value means that the export from ServiceNow, the collection by the inventory connector, the upload from the inventory beacon to the application server, the import, and the compliance calculations have all succeeded. Remember that some servers which were in fact discovered by ServiceNow may not be visible in your filtered list – if they were also inventoried by a higher priority inventory source (such as a locally-installed Inventory Agent), they will be listed against that higher-priority source (and may, for example, display FlexNet Manager Suite).