Marcelo,
As for relationship names, there is a white paper entitled "Mapping Your
Data to BMC Atrium CMDB 7.x Classes" that has a Relationship
Normalization table with suggested names for all relationships.
Brian
Petrus Johansson wrote:
**
Rather than having a dependency relationship between the DC and the
RemedySystem I would suggest doing an Impact Relationship between the
DC and the actual domain. That way you (your boss) would see all
impacted application systems being hosted on a computer system of that
domain affected by a potential reboot of the DC
Best Regards / Mit freundlichen grüssen / Med Vänliga Hälsningar
Petrus Johansson
Senior Product Responsible BMC Discovery Solutions
IKEA IT AB
Sweden
------------------------------------------------------------------------
*Från:* Action Request System discussion list(ARSList)
[[email protected]] för Martinez, Marcelo A [[email protected]]
*Skickat:* den 8 december 2009 23:55
*Till:* [email protected]
*Ämne:* Re: CMDB mapping question: dependency vs. component
Shawn,
Thanks for the image. It helps!
The reason I (or better said - my boss) wants to include the exchange
server and DC is because IF the DC or Exch servers was to be rebooted,
this way would list all the "application systems" that the reboot is
affecting.. But I do see what you mean, the view can get obnoxiously full.
As far as the DB server and database, your example makes sense. I need
to relate the application to the database, not necessarily to the DB
server. Then relate the database to the DB server... I'll need to run
this pass the boss.
One question: what class did you use to load "Remedy Production
ARSystem"? did you use BMC_ApplicationSystem or just BMC_Application?
(I think ApplicationSystem is the superclass of Application)
Thanks again Shawn.
Marcelo Martinez
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Pierson, Shawn
Sent: Tuesday, December 08, 2009 4:27 PM
To: [email protected]
Subject: Re: CMDB mapping question: dependency vs. component
Marcelo,
I hope this image of my layout helps. Basically, I think you are
using the correct classes, but I don't know that I would put
everything you are putting there. For example, do you really need to
list the Exchange Server and Domain Controller? They are sort of
implied, and you may not want to list it and risk making either the
Remedy view or the Domain Controller's views too full.
Also, if you look at my layout, I built dependencies between the
Remedy Application with the database, and the database with the SQL
Server, but I did not relate the Remedy Application with the DB Server.
Thanks,
Shawn Pierson
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Martinez, Marcelo A
Sent: Tuesday, December 08, 2009 3:27 PM
To: [email protected]
Subject: CMDB mapping question: dependency vs. component
I'm mapping out a few "critical systems" in my CMDB and wanted some input.
Remedy System: BMC_ApplicaitonSystem
Rem001 Server: BMC_ComputerSystem - Component of Remedy System
SQL0001 Server: BMC_ComputerSystem - Component of Remedy System (or is
this a Dependency??) ARSystem database: BMC_Database - Component of
Remedy System Exchange Server: BMC_ComputerSystem - Dependency of
Remedy System
DomainController: BMC_ComputerSystem - Dependency of Remedy System
Does this make sense? Or am I mapping it all wrong? Also what is a
good naming convention for relationships: RemSysComp01, RemSysDepen01??
I am doing this manually because I do not know how/where to mass
relate these items. I have about 2000 CIs in Computer systems form.
Specs:
CMDB: 2.1.00
ARS: 7.1.00
ITSM 7.0.03
Thanks,,
Marcelo Martinez
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/> Platinum Sponsor:[email protected]
ARSlist: "Where the Answers Are"
Private and confidential as detailed here:
http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access
the link, please e-mail sender.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/> Platinum Sponsor:[email protected]
ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/>
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
_Platinum Sponsor: [email protected] ARSlist: "Where the
Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"