Name Binding

Arthur Foster

Hillman House, 4, Madeira Road,

Parkstone, Poole, Dorset BH14 9ET

Description of GDMO
Name Binding

e-mail:	arthur@arthurfoster.com
tel:	+44 (01202) 469468
fax:	+44 (01202) 469861

Name Binding Example
Create Operation
Delete Operation

A GDMO managed object can only exist if it has a name. A name is used in the CMIP protocol to identify an instance of a managed object class. In general a managed object instance is named relative to another named object instance. The NAME BINDING template specifies the means by which instances of managed object classes are named. It represents the naming relationship between one managed object class called the superior object class and another managed object class called the subordinated object class.

A specially designated attribute of every managed object, known as the naming attribute, is identified by the name binding. The value of the attribute used as the naming attribute uniquely identifies the contained (subordinate) managed object instance relative to the parent (superior) managed object instance. There can only be one naming attribute associated with managed object class. In addition, there are some restrictions on the type and value of the naming attribute.

        name   NAME BINDING
                SUBORDINATE OBJECT CLASS
                      class ....;
                NAMED BY SUPERIOR OBJECT CLASS
                      class ...;
                WITH ATTRIBUTE  attribute;
                BEHAVIOUR  behaviour  ...;
                CREATE create modifier;
                DELETE delete modifier;
        REGISTERED AS object identifier;

The SUBORDINATE OBJECT CLASS class references a managed object class that is named using this name binding.

The NAMED BY SUPERIOR OBJECT CLASS class references a managed object class from which names can be generated using this name binding.

Both the superior and subordinated managed object class references must be present.

The WITH ATTRIBUTE clause specifies the attribute that is used in the naming of the object. This clause is mandatory.

The behaviour identifier in BEHAVIOUR clause identifies a behaviour template that specifies the associated behaviour. The behaviour definition is optional.

The CREATE and DELETE clauses define the details of behaviour that is required when instances of managed object class are created and deleted.

The create modifier specifies the options available when the CREATE operation is performed. The create modifier values are as follows:

WITH-REFERENCE-OBJECT: This modifier when present specifies that a reference managed object can be used to specify the source of default values and conditional packages on creation. If the modifier is not present then a reference object cannot be used on creation

WITH-AUTOMATIC-INSTANCE-NAMING: This modifier when present specifies that the instance name can be omitted on creation. If this modifier is not present the instance name must be present in create request.

The delete modifier specifies the options available when the DELETE operation is performed. The delete modifier values are as follows:

ONLY-IF-NO-CONTAINED-OBJECTS: This modifier when present specifies that the managed object specified in the delete request can only be deleted if there are managed objects contained in the specified managed object.

DELETES-CONTAINED-OBJECTS: This modifier when present specifies that the managed objects contained in the specified managed object are deleted when the managed object is deleted. If the contained managed objects themselves contain other managed objects then they too must specify DELETE-CONTAINED-OBJECTS.

The REGISTERED AS object identifier is a unique identity that is used in the protocol to identify this particular name binding. The object identifier that represents the name binding of a managed object instance is present in every managed object instance. This means that a manager system can work out how any particular managed object instance is named from this value.


Author: Arthur Foster 28 May 2002	Arthur Foster is a founder member of
Author: Arthur Foster 28 May 2002		Hosted by