Jason, We create new classes in our own namespace. In the CMDB2.0 Concepts & Best Practices Guide - it recommends this as a best practice
Here's the snippet: "Whenever you extend the data model, you should use your own namespace instead of BMC.CORE. This prevents your extensions from being overwritten by new BMC classes when you upgrade to a future version of the CDM. When creating namespaces, use the naming convention COMPANYNAME.PURPOSE. For example, if the Acme Company created a set of classes for storing data about buildings and other facilities-related CIs, they might store them in the namespace ACME.FACILITIES." Hope this helps! Cindy On Wed, 15 Nov 2006 12:19:08 -0800, Jason Miller <[EMAIL PROTECTED]> wrote: >Hi all, > > > >I am wondering what people are using for naming conventions when adding >classes to the CMDB. There is the convention of adding a plus sign to the >beginning of homegrown forms (and workflow). This doesn't appear to be an >option when using the Class Manager unless you create a new Namespace >starting with a plus. > > > >So here is the poll. > > > >1) If you use the BMC Namespace how do you name your classes to >indicate they are homegrown? > >2) Does anybody create their own Namespace for their custom CMDB >classes? > > > >Jason > > >___________________________________________________________________________ ____ >UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
