H3C Technologies H3C Intelligent Management Center - Manual (Page 499)

485
Table 11 Properties supported by the Operation element
Property
name
Description Required Remarks
id Operation ID Y
A character string consisting of letters or digits; unique in
a file.
Label
Operation
display name
Y A resource string starting with %.
categoryId
Category ID of
the operation
Y
The operation category is defined in the categoryDef.xml
file. See the later sections for more information.
actionId Primary action ID Y
Action executed for the operation. The value must have
been defined in the operation. Other actions can be
called secondary actions.
actionType
Primary action
type
Y Enumerated value: 1(REST) or 2(ASN1).
operLevel Operation level N
Indicates whether the operation is port level or device
level. It is an enumerated value: 1(DEVICE) or 2(PORT).
The default value is 1—device level.
devCapability
Device
capability set
N
Indicates the device capability set supported by the
operation. The capability set must be defined in the
<component name>_devCapabilities.xml file. The
default is the device capability set defined by the
Operations element (rather than ALL).
The operations with the same name in different registration files are considered one operation. The
following information for the operations must be consistent:
• Operation ID (id)
• Category ID of the operation (categoryId)
• Operation display name (label)
• Operation level (operLevel)
• For parameters of the actions (primary and secondary actions) of the operation, the values,
numbers, sequence (compiling sequence), and property values (unique for each property) must be
the same.
For the operations with the same name in different registration files, the following items are typically
different.
• Capability set (devCapability) (If the capabilities are the same, the defined operations are
meaningless.)
• Primary action name (actionName).
• Primary action type (actionType).
• Action (primary and secondary) properties, excluding the parameter information.
CAUTION:
If the operations with the same name do not satisfy the requirement of information consistency, the system
discards the loaded operations and logs the event.