Discovery Process Classifiers creating duplicates
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2014 06:45 AM
While i think i have seen an article on my problem, the past two days of searching have gone in vain...so maybe someone knows and i am looking in the wrong place (points to Doug)...
I have a simple process classifier that creates a record on cmdb_ci_appl based on an executable running (provenirADMIN.exe). Setting this up was easy enough, but when i discover two servers that have the process running, it creates unique values. These are typically:
provenirADMIN.exe@servername1 Runs on::Runs servername1
provenirADMIN.exe@servername2 Runs on::Runs servername2
The best i have been able to do is to strip the server designation off, but since the value is still unique (a'la SYS_ID), it creates a "duplicate"...
What i need is to have one application automatically associate itself with all servers it finds:
provenirADMIN.exe Runs on::Runs servername1 and servername2
I know this is possible, i am just having trouble finding the right instruction...
Anyone have an article handy?
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2014 07:28 AM
Hi John,
I will look into the CI Identifiers to find out what is being used as the unique ID for CIs. I'm assuming you are using Serial Number as your unique ID, so make sure this is active in the list.
Also, look at the Discovery Log to check at what point the Discovery Job is creating a new CI (likely because it couldn't find a match for your selected identifier).
Regards,
/Amado
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2014 07:56 AM
John, (were my ears burning)
Unfortunately It just don't work that way, for we do not have the concept of a one (application) to many (computer) reference for running applications....its a one to one relationship because each application is truly its own entity..think of the confusion if adding a single application to a business service and try to figure out what server its running on that supports that business service because we found it running on on 200 devices throughout your environment..
In respect to Amado's reply.. Amado, not a bad shot there.. We do have the identifiers to be sure that we are creating or updating an absolute Hardware record, it is not used for applications as John is having concern with.
With that said i WISH that Aleck would get us some level of identification process for applications, that would really help with those folks that want to import something that already exists and not have us create a duplication because we found out own...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2014 08:21 AM
Haha...i thought that would wake you up Doug...thanks for the response.
While I will accept your response, i do so as a challenge as i am confident that with some creative scripting, this can be done... After all, i cannot seem to say "no" and "servicenow' in the same sentence...
Wish me luck on this one...i will post something when i get a prototype started, but i am sure it will take some time as i am still junior in the java area...
Thanks!!
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2014 08:35 AM
I hear you, with ServiceNow its (near) never really if.. can it be done.. but more of 'should' it be done...so think about the impact as you start down this path... you change it, you own it!
But to get your brain rollin more then it already is, I would envision something along the lines of how we do software where its a one to many reference between the instance and the parent running process "package" then a relationship between that instance and the server it was discovered on...
Man, just typing that a whole mess of script includes would have to be changed came to mind.. I envy you not Sir