One point about Impact relationships - BMC plans to drop them!

The base relationship class now includes impact information.

In the future any relationship will be able to hold impact information
which should reduce the number of relationship CIs needed to model an
environment.

Cheers

Peter



> When we were mapping that out, we made Remedy be a SoftwareServer.  We
> also included SoftwareServers for the database servers (the database
> software, not the hardware) and made the Databases depend on the Software
> Servers.  But then, we were tracking more information about databases in
> general.  If you don't care about what software database servers are
> hosting what database instances but rather just the host the database is
> on, then you're probably fine doing it the way you have or like Shawn did.
>
> As far as the relationship types, I would go with Dependency and/or
> Impact.  I'm not sure you can even make some of them components - I think
> that that requires that the child class be a subclass of SystemComponent.
>
> Lyle
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of Martinez, Marcelo A
> Sent: Tuesday, December 08, 2009 3:55 PM
> To: [email protected]
> Subject: 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 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 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"
>
>
>  NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited. If
> you are not the intended recipient, please contact the sender by reply
> email and destroy all copies of the original message.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> 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"

Reply via email to