This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Defining class properties in the Class Manager

The BMC Atrium CMDB Class Manager helps you define properties for Configuration Item (CI) and relationship classes. The properties of a class define the class and how it stores data.

Creating or modifying classes process




For more information on class and relationship properties, see Common CI and relationship class properties.

To define class properties

  1. In the Class Manager, browse the data model until you have selected the class that will be the superclass for the new class.
  2. In the toolbar, click either New CI Class or New Relationship Class.
  3. In the Properties section of the Generaltab, enter information as described in the following table.

    Note

    You cannot modify the Data Storage Method, Final, and Singleton fields after you have saved a class.

  4. (optional) In the Additional Information section of the More Information tab, enter a description of the class in the Description field.
  5. If the class is a relationship class, define relationship type properties as described in the following table; otherwise skip this step.
  6. Perform one of the following actions:

    Action

    Steps

    You want to provide additional information for the class

    Continue with the process described in Process overview for creating or modifying classes.

    You are finished working with this class

    1. Click OK.
    2. In the confirmation dialog box, click OK.

Common CI and relationship class properties

This section describes the common CI and relationship properties you can define when defining a class.

  • For information on defining class properties, see Class properties. The class properties defined in the CI Class and Relationship Class dialog boxes are listed in the following table. This table also describes how you should enter information for those properties when creating a new class.
    Most of these properties are fields on the General tab of the CI Class and Relationship Class dialog boxes. The Description field is on the More Information tab.
  • For information on relationship classes that define how the relationship functions with CI classes, see Additional properties for Relationship classes.

Class properties 


Class properties

Property

Description

Class Type

Indicates the type of class.

Super Class

Select a class to be the parent class of the new class.

Namespace

Select a namespace from the list or enter a new namespace. For more information, see Namespaces and partitioning the data model.

Class Name

Enter a name that describes the class. Class names are limited to alphanumeric characters and underscores.

Status

Indicates the current state of the class. You cannot enter a new value in the Status field. When you create or modify a class, its Status is set automatically to Change Pending.

Author

Enter your name, as the person who created the class.

Final

Select the Final check box to prevent subclasses from being created for the new class. For more information, see How additional subclasses extend the data model.

Singleton

Select the Singleton check box if this class represents a unique CI. For more information, see How additional subclasses extend the data model.

Description

Enter a brief description of the class, such as information about the type of data stored by the class, how the class should be used, and any unusual characteristics of the class.

Note

This property is in the More Information tab.

Data Storage Method

Select an option:

  • Regular--The class stores instances on its own BMC Remedy AR System form. If the class is a subclass, the AR System form is a join form that joins the attributes of the superclass with the attributes unique to the subclass.
  • Categorization-- The class stores instance attributes in the AR System form of its superclass rather than in a join form. A join form is still created using the class name for your convenience, but it is not part of the inheritance tree.
  • Abstract with data replication--The class cannot hold any direct instances, but instances of its subclasses are replicated to a form that holds only the attributes of the superclass.
  • Abstract without data replication--The class cannot hold any direct instances and does not have an AR System form.
    For more information about data storage methods for classes, see BMC Atrium CMDB data storage methods.

Custom Properties

A list of user-defined custom characteristics for the class. The ID for each list item can be set to any user-defined characteristic but must be between 100000 and 199999. You must enter the custom properties in serialized format:
<listSize>\<propId>\<dataType>\<propValue>\<propId>\<dataType>\<propValue>\...
For example, the serialized property list could be represented as 1\100050\2\1.

  • listSize — The number of items in the properties list.
  • propId — The ID for the property, which is within the 100000-199999 range.
  • dataType — The data type for the property, which can be of any native data type as specified in the ar.h file. For example, an integer is 2 and a character string is 4. For more information, see BMC Atrium CMDB C API header files.
  • propValue — The value for the property. For some data types, the <propValue> can contain information about the value itself.

    For data types CHAR, DIARY, VIEW, and DISPLAY, the <propValue> contains both the data value length and the prop value, so the serialized format is:
    <listSize>\<propId>\<dataType>\<dataLength>\<propValue>

    For data type DECIMAL, the serialized format is:
    <listSize>\<propId>\10\<valueLength>\Value

    For data type CURRENCY, the serialized format is:
    <listSize>\<propId>\12\<valueLength>\Value\<currencyCodeLen>\<currencyCode>\<timeStamp>\<numItems>\<funcValueLength>\<funcValue>\<funcCurrencyCodeLength>\<funcCurrencyCode>

    For example, a Custom Properties list containing one value, an integer with ID 100050 and value 1 would be formatted: 1\100050\2\1

    For example, a custom property of data type CHAR, ID 100000, and value of Houston would be formatted: 1\100000\4\7\Houston

    For example, a custom property of data type CURRENCY, ID 100001, and value of $3.30 would be formatted: 1\100001\12\4\3.30\3\USD\1242870112284\1\4\3.30\3\USD

    Combining two properties in a list would be formatted:
    2\100000\4\7\Houston\300001\12\4\3.30\3\USD\1242870112284\1\4\3.30\3\USD

Additional properties for Relationship classes

Relationship classes require additional properties that define how the relationship functions with CI classes.

  • Member classes — Two CI classes must be members of a relationship class. Class 1 is the source member and Class 2 is the destination member. If you need directionless or directionally symmetric relationships, you can create another relationship with Class 1 and Class 2 switched.
  • Roles — Refers to the relationship roles of the member classes. You can use the default Source and Destination roles, or you can specify new roles when you create a relationship class. Role names are used as prefixes on the field labels of attributes pertaining to each member class.

The following table lists the properties defined in the Relationship Class dialog box, and how you should enter information for those properties when creating a new class.




Relationship type properties

Property

Description

Class 1

Select a class to use as the source class.

Class 2

Select a class to use as the destination class.

Role 1

Enter a role name for Class 1. By default, this is Source.

Role 2

Enter a role name for Class 2. By default, this is Destination.

Cardinality

Select a cardinality:

  • One to one--Each instance of Class 1 can have this relationship with one instance of Class 2.
  • One to many--Each instance of Class 1 can have this relationship with multiple instances of Class 2.
  • Many to one — Multiple instances of Class 1 can have this relationship with each instance of Class 2.
  • Many to many — Each instance of Class 1 can have this relationship with multiple instances of Class 2, and vice versa.
    BMC Atrium CMDB enforces the cardinality of a relationship class. Fulfilling a "many" cardinality means that multiple instances of the relationship exist.

Cascade Delete

Select the Cascade Delete check box to delete (or mark as deleted) the destination member whenever the source member is deleted (or marked as deleted). This field applies only to relationships with a left-hand cardinality of One to One or One to Many.

Weak Reference

Select the Weak Reference check box to create a composite object with the relationship and its member instances in which the destination member is a weak entity. This field applies only to relationships with a left-hand cardinality of One.

Propagated Attributes

If you have selected classes in the Class 1 and Class 2 fields and you have selected the Weak Reference check box, click Propagated Attributes to map attributes between members of a weak relationship. For more information, see Propagating attributes for weak relationships.

Was this page helpful? Yes No Submitting... Thank you

Comments