As an example, we used the Microsoft System Center Configuration Manager (SCCM) source. We show how a server Asset is read from SCCM and then updated and updated in TOPdesk. We make use of the New Asset Module of TOPdesk not the Configuration Management Module.
Keep in mind that it is a test scenario is made up of a number of scenario-specific settings. Of course we can take into account you / your specific settings. For example, the scenario is almost the same when you get the Assets from PRTG or another operational source.
Create / Define TOPdesk Template
In the Asset Module you have to create so called Templates:
These templates contain different fields of different types:
String, Number, Search. Date/Time etc
The TOPdesk Asset Connector retrieves the Templates and creates tables that the Asset Connector uses to send Asset Data.
With our platform Data Manager, the columns in the various Inpu_Assets tables can be filled from an Asset Inventory Tool, for example SCCM. SCCM has an inventory module with which the device and the associated attributes of a Device can be inventoried.
Create Asset in TOPdesk
In this example there are 8 devices that are inventoried by the SCCM agent. The different Devices have to be mapped to the different templates / templates on the basis of business ruls. In Topdesk none of these devices are in the New Asset module. In this example all devices are servers, except for S4MTST-SCOM-01, which is a Workstation.
Datamanager (ETL +) collects all the relevant properties of the devices. These will eventually end up in the previously mentioned Input_Assets (_Server) table of the TOPdesk Asset Management Connector database.
The connector also has functions to extract data from TOPdesk. This is needed to determine what to do with the Asset, for example a Create, Update or Delete (Archive) for example.
In this example, 3 (out of 7) have been transferred to the connector. In Data Manager, the business rules determine whether and is a Create of Update, you can also leave a create or update to the connector by setting ProcessStatus to Automatic. The connecter then checks whether it is a create (assets do not exist in TOPdesk) or an update (Asset exists). You will always have to define a Delete yourself.
By executing the connector to send the data to TOPdesk. The Assets will appear almost immediately in TOPdesk.
The result of the webcall appears in the used Input_Asset_Server table in the database:
The WebResult is 200 (successful) and in Process status you see it being changed to Processed. If for any reason an error has occurred you will also find this in the table. If we zoom in on S4MDMO-AFAS in this case, we see the different fields with the correct value in SCCM.
Update Asset in TOPdesk
It is possible that the attribute of an asset change(s) in SCCM and/or TOPdesk. In the example below the memory of this server in TOPdesk is manually set to 16. In the next run, the TOPdesk SCCM Connector together with Data Manager will reset the memory to 4 because from SCCM it tells us that the server has 4 instead of 16gb. Obviously it can decide for itself which fields should be updated automatically or left alone. This is done via the connector.
After performing the connector, the memory will be reset to 4.By using our workflow engine this can all be automated.
Manually update TOPdesk Assets
With the Data Manager Portal it is possible to let non-technical user(s) decide which record(s) should be transferred to TOPdesk.
In addition to the assets, the connector also contains the other elements (depending on the API status of that element) for example people and branches / site, but also incident registration can be done with this TOPdesk connector.
It is possible (with our connector) to extract the OData (https://blog.topdesk.com/updates/reporting-power-bi) from TOPdesk from your TOPdesk Saas environment into the database for further processing, for example in your BI tool .