I don't know about you, but I'd look in the documentation
Also, if you have autodiscovery tools I'd look into if it/they have any preferences.
Most importantly though. If you don't need it. Don't use it.
Your CMDB should not express more than you need it to.
As a side note - you are probably going to need more than you thought at first. When your users start to understand what a wonderful tool the CMDB is they are going to have requests. Some of them might even be good/useful.
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Wed Nov 12, 2008 7:51 pm Post subject:
it seems to me you are thinking backwards. Do not ask "how do I use this?" but rather "what do I want this to do?".
How did you select and acquire a tool without first defining what it was required to do?
If you analyse the tool before you analyse your requirement, then the probability of using it effectively is infinitesimal.
Obviously you may not require all of its functionality, but how much of your requirement will it meet? That is what lies behind Pel's response.
The "when to use which" conundrum will disappear when you start out with knowing what you want to do. The much more problematic "how can I make it do this?" will loom large in its place. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Thanks for your quick responses. I understand what you telling me. Just a little background, I did not select the tool. It was already in place and I have to use what we have. I am trying to understand the differences between the various types of relationships.
It seems to me that what relationship type I use will depend on whether the relationship is describing the flow from the parent to the child or the other way around. Am I way off base here?
Posted: Sat Nov 15, 2008 1:03 pm Post subject: Relationships
Don't get too hung up on the types of relationship - many just choose one to show there is a relationship between two CIs. Even if you did use lots of relationship types you get into the areas you mention - parent child may be different to child/parent. What do you do where there are 3 valid relationship types between a parent and child - do you enter them all?\and will the CMDB display each of them?. Think about the poor sod who has to validate the CIs and relationships, making sure they're right.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum