This documentation supports the 19.08 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Common CI and relationship class properties

The following information consists of the common CI and relationship properties that you can define when defining a class. 

 

Common 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.

Property

Description

Class Type

Indicates the type of class.

Super Class Name

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.

Author

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

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.

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 by 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 How CMDB data is stored in Remedy forms.

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 between 100000 and 199999. You must enter the custom properties in the following format:

{ “fieldID1”: <value1>}

For example, { "100050": 1, "400090": "PrimaryCapability" } 

To remove an existing property, for example, to remove the property for 400090, change the list to:

{ "100050": 1, "400090": "" }

 Additional properties for Relationship classes

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

  • Member classes — You must ensure that the CI classes are 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 describes how you should enter information for those properties when creating a new class.



Common 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:

  • 1-1 — Each instance of Class 1 can have this relationship with one instance of Class 2.
  • Many-1 — Multiple instances of Class 1 can have this relationship with each instance of Class 2.
  • 1-Many — Each instance of Class 1 can have this relationship with multiple instances of Class 2.
  • Many-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 Creating or modifying classes by using Class Manager.

Related topics

Creating or modifying classes by using Class Manager

Modifying the data model by using Class Manager



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

Comments