How to create the data collector workflow
You can create a data collecting workflow from the Generic inventory provider data collector - WF Template template. The data collector workflow needs to be configured to connect to the source system and fetch devices and their inventory from it.
To create a workflow from the template, you need to use Workflow Studio.
The general approach to using workflows to import data into Matrix42 Software Asset & Service Management is described in Integration Framework.
When you create a workflow from Generic inventory provider data collector - WF Template, you will need to set up the data collecting process in the TryCreatePackage > Create Package > Flowchart part of the workflow.
Hints on creating a data collector workflow:
- Set up a source of data. For example, this can be running a PowerShell script.
- Transform and map the obtained data to to the attributes of data definitions. For example, you can use an array of JSON objects for obtained assets. See What kind of data can be imported for computers for details on what attributes can be imported.
- Use the Add Connector Package Item activity to create an XML file that will be used by the Generic inventory provider workflow to import assets into the system.
Refer to this article to download a sample workflow and see how it is arranged.
What kind of data can be imported for computers
The Generic inventory provider workflow uses the new Import Assets activity that imports devices into Matrix42 Enterprise Service Management. Any attribute of the Computer configiration item can be updated this way. All attributes are updated with each next import.
If you import an attribute whose value is a relation to another entity, the value must be provided as a GUID. Only hosts, users, and domains are matched by a name as specified below.
Mandatory data definitions of the Computer configuration item that can be updated with imported attributes:
Relation to domain is saved as GUID in the database, but a domain name must be used as source data. The workflow will match it to existing domains.
Relation to host is saved as GUID in the database, but a host name must be used as source data. The workflow will match it to existing computers.
Relation to SKU
The SPSStockKeepingUnitClassBase data definition can also be updated although it is not a part of the Computer configuration item.
You can import an SKU value for a computer. The matching is made by Manufacturer and Model. If no match is found, a new stock keeping unit is created.
The following data definitions are multifragments of the Computer CI and can also be updated:
Relation to LoggedAccountName is saved as GUID in the database, but a login account must be used as source data. The workflow will match it to accounts. The User Logins grid is never overwritten and only new records are added to it.
Matching to existing fingerprints is done by Name, Manufacturer and Version. If such a fingerprint is not found, a new record is created. The Installed Applications grid is never overwritten and only new records are added to it.
Except for Installed Applications and User Logins, all records that belong to the multifragment data definitions are overwritten with each next import.