Customizing imports from the Ivanti Neurons Platform

asset administrators can create device parent type/subtype filters and field mappings that define how the ivanti neurons connector will import source asset data these customizations provide a high level of control over how data is displayed in the hardware assets workspace and are useful when importing many records at once you can export the connector customizations as a package, then test them in a staging or uat environment before using in a production landscape to sync data from the ivanti neurons platform the package enables you to duplicate the customizations across multiple tenants, each of which must be installed with the most recent version of ivanti neurons for itam cloud to access this feature, you're required to apply content package update drop #21 (202002) and above, which is downloadable from the ivanti marketplace https //marketplace ivanticloud com/ (note that drop #21 may be part of a consolidated package ) non computer asset type support this content package also provides snmp connector support for importing non computer asset types from the ivanti neurons platform for example, printer data can be imported as a printer subtype into the target database to enable support, you must first create a new subtype mapping for the non device type in the asset sub type workspace under one of the existing parent types you can then add the required mapping for the snmp connector by following the next procedure to customize asset data imports log in to itam as asset administrator click the icon in the menu bar at the top of any workspace the configuration console displays in a new browser tab in the left navigation pane, expand extend > integration tools > data import connections the data source manager page lists all data import connections currently defined for your installation scroll down the list to the ivanti neurons connector – device link ensure the connector is set to on and click the link to open connection setting page we recommend leaving the defaults as they are, though you can change as needed click test connection near the bottom of the page to verify that your connection settings work if successful, click next object mapping page we recommend leaving the defaults as they are, though you can change as needed source mapping tables is a list of populated tables based on settings defined on the previous page batch size is the number of records processed at a time for any given job max size is the number of records retrieved each time the connector queries the source database root table is the primary table containing the master data that defines all devices in your organization unique key uniquely identifies all devices in your organization change time column is not currently in use click next filter setting page define optional filter conditions for the records you want to import based on the filters defined, only those records will be imported from the source database for example, you can choose to import an asset type of laptop by creating the filter value laptop as shown below in the left drop down, select a field from the source database for this procedure, select device type , but you can create filters for different fields as well do not select a field that results in a collection of values being imported from ivanti neurons—filters will not work for those fields for example, don’t select a value such as device bios biossettings in the middle drop down, select an operator in most cases, you’ll want to select equal important the operator isnotempty must be used for filtering out null parameters instead of nocontain for example, use isnotempty when syncing devices from ivanti neurons that don't have a serial number in the field to the right, enter your filter condition you can only add one filter per row use the and/or conditions as necessary and click the icon to add more filters to the list to remove a filter, click the icon when finished, click next field mapping page use this page to define how fields in the source database are mapped to fields in the target itam database the newly added map types of ciparenttype and cisubtype reconcile the asset parent type and subtype of the imported records based on the “type” received from ivanti neurons (as defined in the asset sub type workspace) always ensure that both the parent type and subtype mapping are up to date in the asset sub type workspace this mapping will determine the asset import categorization also note the following if ciparenttype reconciliation doesn't find a proper parent type in the asset sub type workspace, then the parent type will be mapped to the new ci type category as defined in the asset processor configuration workspace (by default, ivnt unmanagedasset) the device record will display in the hardware assets workspace under the same category if cisubtype reconciliation doesn't find a proper subtype in the asset sub type workspace, then the asset import will fail the left column displays the source field names, and the right column displays the target field names it’s assumed that you know the source mapping names in advance if you need sample mapping scenarios, see the section below scroll down the page until you find the device type source field in the left column (there will be two device type sections in the first, you’ll select the ciparenttype mapping in the second section, you’ll select the cisubtype ) note that to have a cisubtype field mapping, it's mandatory to first have a ciparenttype mapping under the device type source, use the drop downs to select the asset parent type you want imported into the database from the middle column drop down, select ciparenttype from the right column drop down, select computersystem property citype for the field you want to map to scroll down to the second device type source field in the left column use the drop downs to select the asset subtype you want imported into the database from the middle column drop down, select cisubtype from the right column drop down, select computersystem property subtype when finished, click next schedule setting page use this page to schedule when the connector will sync with ivanti neurons to import data into itam available options are located in the schedule list; click the schedule you want to enable if needed, you can select more than one schedule using the ctrl button on your keyboard to create a custom schedule, see about the schedule entry and scheduled jobs workspaces https //help ivanti com/ht/help/en us/ism/2022/admin/content/configure/schedules/schedule entry htm?highlight=schedules in the ivanti neurons for itsm online help review & publish page click preview to ensure that the mappings look as expected click back to make any changes when you’re satisfied with the results, click publish to save your settings and run the connector at the schedule(s) you set, or click publish & run now to save your settings and run the connector immediately in either case, once the connector is finished running, device records will display in the hardware assets workspace, and invoice records will display in the invoices workspace click publish & test run to conduct a test run of the connector but not save the records to the target itam database this a one time configuration that is saved until you manually change it again after publishing, you'll want to test that the customizations work as intended for details, see the following section sample mapping scenarios use case 1 for the mapping portable > computer = ciparenttype = computersystem property citype shown below, the asset imported from ivanti neurons having device type > portable is mapped to the parent type computer in the target database hence, the device is imported under the parent type of computer mapping scenario for use case 1 use case 2 if you create a mapping of laptop > computer = ciparenttype = computersystem property citype , it won't work if laptop isn't also defined in the asset sub type workspace in this situation, devices of type laptop will be moved to the new ci type category defined in the asset processor configuration workspace (by default, ivnt unmanagedasset) and will display in the hardware assets workspace under that same category use case 3 if a ciparenttype mapping is not defined in the ivanti neurons connector field mapping page, then the new ci type category defined in the asset processor configuration workspace will be used (by default, ivnt unmanagedasset), and the device will display in the hardware assets workspace under that same category use case 4 with the subtype mapping portable > laptop = cisubtype = computersystem property subtype shown below, the device type received from ivanti neurons as portable is imported as subtype laptop under the parent type of computer mapping scenario for use case 4 use case 5 if a device type is received as laptop, which does not exist in the mapping (left panel), then this subtype will be considered as laptop in the target database testing the connector customizations it's recommended that you export your customizations as a metadata package and test them in a staging or uat environment before importing into a production landscape the process for doing so follows these general steps and is explained in the procedure below export the customizations (created in the procedure above) as a package contact ivanti customer support to have them point the neurons platform to your staging or uat tenant import the package to the same staging or uat tenant and test it make any necessary changes contact ivanti again to have them point the neurons platform to your production tenant import the package to your production tenant in preparation for importing data from the neurons platform in all cases, the latest version of ivanti neurons for itam must be installed on your tenants important the following procedure is applicable only for an update scenario; exported packages won’t create new connections if the connector doesn't already exist as part of your installation before applying the package, back up your database clone and delete actions for ivanti neurons connectors (device and invoice) are currently disabled or have been removed to test and verify the customizations log in to itam as asset administrator click the icon in the menu bar at the top of any workspace the configuration console displays in a new browser tab in the left navigation pane, expand extend > integration tools > data import connections scroll down the list to the ivanti neurons connector – device link scroll to the far right of that link and click the icon to export the customizations as a package in the warning dialog that displays, click continue the package is exported to your downloads folder contact ivanti to have them point ivanti neurons to your staging or uat tenant from your browser, log into a staging or uat tenant and open the configuration console in left navigation pane, click build > development package > packages ensure that you're in the list view, then click import package (top right of the toolbar) browse for and open the customization package in the dialog that displays, click preview impact to view details about how this package may impact your database click execute to apply it; this process may take a few minutes to complete verify that the package works as intended and make any necessary changes contact ivanti again to have them point the neurons platform to your production tenant import the package to your production tenant if needed, you can duplicate the package across multiple production tenants once you've completed this procedure, you can begin importing asset data for details, see the import process section in importing from the ivanti neurons platform docid\ wpoh386uhl7gpi49sdlbz