Considerations for Configuration Management maps

While Service Manager provides both an entity file (device) and attribute files (for example, server), it is not necessary that both files exist to represent the characteristics of every device type. You can often fully describe a device using only the fields in the device file.

The map record for the type field (field #9 in standard events) defines how Service Manager selects and displays information about a device once the data is added. The type field in the device file refers directly to the associated attribute file of each device. If no attribute file associated with a device, the type field must contain device or be empty (NULL).

Similarly, the format.name field in the device record defines the name of the form that displays the device within Service Manager and, by extension, the name of the join file that temporarily stores information for review and update. The formatctrl record for the format name stored in the device record must contain device as the file name for all device types that do not have associated attribute files.

If an external agent detects an unknown device type, Service Manager processes the event, updating the device file with the information provided. If no attribute file exists for that device type, a Warning message is written to the Message list for the event but the device is still added or updated in the Service Manager data repository. If event mapping indicates processing in more than one table, but the number of fields passed to the event is less than the position of the first field in the second table, there is no attempt to open the second table.

Related topics

Change Management input event registration
Change Management output events
Considerations for Configuration Management maps