Assets Discovery Import-Mapping

[Carmen Odimba]

Jira Service Management Data-Center.

When configuring an Assets Discovery import to Assets, data mappings must be configured between the data file and the Assets object schema. This is not a problem for properties that are at the first level of the data file, but seemingly impossible for properties that are at lower levels or within an array.  

For example, the IP addresses of a virtual machine object (which is a 1:n relationship) are to be transferred to assets. The information is available in the data file, but the mapping cannot be configured. Only the virtual machine object can be mapped but not the other information within.

How can I solve this?

[Carmen Odimba · Accepted solution]

In case someone needs help on this matter, I got help from a colleague. In our example we have virtual machine objects that are on the first level and can therefore be mapped easily and the tricky part is to import attributes of these VMs, for example IP addresses.

There are 2 solutions:

1) Import the network interfaces as objects and then reference them with the solution described here: https://confluence.atlassian.com/servicemanagementserver/2-create-object-type-and-attribute-mapping-1044784497.html

> Object mapping (AQL) > Name IN (${DATA LOCATOR${0}})

2) Import everything under Network Interfaces (the complete string) and in a second step parse the IP address via RegEx

The first solution is the "best".

[Scott McDonald]

Am I correct in stating the Assets Discovery scanning tool does not do any mapping automatically?  Anything that needs to have dependency mapping needs to be done manual.

[Deivid Araujo]

I also want to know that. 

[Scott McDonald]

Am I correct in stating the Assets Discovery scanning tool does not do any mapping automatically?  Anything that needs to have dependency mapping needs to be done manual.

Scott