Self-Certification Workflows

Self-Certification workflows are examples of real use cases that you may encounter. Use the workflows as a model to help you with self-certification:
capm360
HID_Self-Cert_Workflows
Self-Certification workflows are examples of real use cases that you may encounter. Use the workflows as a model to help you with self-certification:
 
 
Basic Self-Certification Workflow
You can use the following basic self-certification workflow to create a vendor certification.
This workflow covers the basic concepts and requirements to create a component, metric family, and vendor certification using the available REST services:
 
 
2
 
 
The following graphic provides a high-level overview of some common self-certification scenarios:
Self-Cert
Self-Cert
 If you design a new vendor and technology certification containing only device-level metrics, a component definition is unnecessary (for example, see the Availability metric family).
For more information, see the following pages:
Create a New Component
You can use the components XML to introduce a new managed item type. The components XML defines how a discovered component is synced over to 
Performance Center
. The XML creates a component in your inventory and is required only when a component does not exist already.
 
Follow these steps:
 
  1. Customize the following XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <!--Auto-generated by the type catalog local manager.-->
    <DataModel namespace="http://im.ca.com/inventory"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="ComponentFacet.xsd">
    <Author>Custom</Author>
    <Version>
    Version
    </Version>
    <FacetType name="
    Name
    ">
    <Documentation>
    Clear_Text_Description
    </Documentation>
    <FacetOf namespace="http://im.ca.com/core" name="Item" />
    <Component>true</Component>
    <ItemSyncDefinition itemTypeName="component"
    itemSubtypeName="
    Internal_Name
    "
    itemTypeLabel="
    External_Name
    "
    itemTypeLabelPlural="
    External_Names_Plural
    "
    categorize="false"
    groupBy="false"
    context="true">
    </ItemSyncDefinition>
    </FacetType>
    </DataModel>
    •  
       
      Version
       
      Specifies the sequential number of the version definition. If you configure the version correctly, it should not change frequently.
      Example: 
      1.0
       
    •  
       
      Name
       
      Specifies the component name. Each component must have a unique name that identifies it internally within the system. Carefully choose a name with a minimal possibility of naming conflicts with future similar components. For example, define a naming scheme that ensures that these component names are unique. This string is used in the Component Facet Definition in the Metric Family and cannot be updated.
      Possible values: Alphanumeric and underscore. Dot and dash are not permitted.
       This name is never exposed externally. To display a component name in the user interface, use the ItemSyncDefinition, itemTypeLabel,
       
      and itemTypeLabelPlural elements.
    •  
       
      Clear_Text_Description
       
      Specifies internal comments for the component. To make these comments useful, describe why and when you added or changed the component.
      Possible values: Plain text
      Effect of updating: None
      When does the update take effect: Immediately
      Required Actions for updates to take effect: None
    •  
       
      Internal_Name
       
      Specifies the internal name of the component in 
      Performance Center
      . This value must be unique for all components. Use a naming convention that avoids conflicts with future factory and custom components, such as using a prefix representing your organization, '
      acmeFan
      '.
      Can be updated: No
      Possible values: Alphanumeric, unique for all components
    •  
       
      External_Name
       
      Specifies the user interface label that is used when displaying a single component of this type. For example, this value is used in the Inventory, Device Components UI “Type” column.
      Can be updated: Yes
      Possible values: Plain text, unique for all components
      Effect of updating: Label is displayed in 
      Performance Center
       Inventory user interfaces.
      When does the update take effect: Allow for resync to occur and up to 15 minutes to complete updates.
    •  
       
      External_Name_Plural
       
      Specifies the user interface label that is used when displaying multiple components of this type. Used by the Inventory menu (see 
      groupBy
      ) and the Group name (see categorize).
      Can be updated: Yes
      Possible values: Plain text, unique for all components
      Effect of updating: Label is displayed in 
      Performance Center
       Inventory UIs.
      When does the update take effect: Allow for resync to occur and up to 15 minutes to complete updates.
    •  
      categorize
      Instructs 
      Performance Center
       to create an inventory group under Inventory, All Items. This group contains all items of this component type. The group is named '
      {
       
      itemTypeLabelPlural
       
      }'.
       
       The inventory group that is created cannot be used for reporting dashboards. Instead, this group is for inventory purposes only. If the group is selected for reporting, then no data displays. Other, device-based inventory groups (under Inventory, All Items) can be used for reporting, such as Routers and Servers. However, component-based inventory groups cannot, such as Device Components.
      Can be updated: Yes
      Possible values: true, false
      Effect of updating: Creates or removes an Inventory group in 
      Performance Center
      . For 
      Performance Center
       group administrators, on the Manage Groups page, the group is created under Inventory, All Items, 
      {
       
      itemTypeLabelPlural
      }
       
      .
      When does the update take effect: Allow for resync to occur and up to 30 minutes to complete updates.
      Required actions for updates to take effect: Items typically appear in the group within 30 minutes. If they do not, manually resync the Data Aggregator data source. Select 'Perform a Full Resynchronization' before clicking the Resync confirmation button.
    •  
      groupBy
      Instructs 
      Performance Center
       to create an inventory menu item (under Inventory) for viewing all items of this component item type. The menu is named "
      {
       
      itemTypeLabelPlural
       
      }.
      " This attribute also causes the component type show up in the Context Type drop-down list when setting a view context. When false, the components are listed in the Inventory, Device Components table with the type of "
      {
       
      itemTypeLabel
       
      }
      ." The 
      groupBy
       property does not create a group (see categorize).
      Can be updated: Yes
      Possible values: true, false
      Effect of updating: The menu item is created when true, or removed when false.
      When does the update take effect: Allow for resynchronization to occur and allow up to 15 minutes to complete updates.
    •  
      context
      Makes each component item name a context hyperlink in the Inventory component views that, when clicked, navigate to the individual component context page.
      Can be updated: Yes/No
      Possible values: Plain text
      Effect of updating: Makes each component item name a context hyperlink in the Inventory component views.
      When does the update take effect: Allow for resynchronization to occur and allow up to 15 minutes to complete updates.
    You can create a component without the 
    ItemSyncDefinition
     tag. In this case, a component discovered in Performance Management for this managed item type is not synced over to 
    Performance Center
     (like CPU, or memory). Although the component is not synced over, you can still report on these managed items at the device level.
  2. Set up a REST client with a connection to the Data Aggregator server.
  3. Use the following format for the URL in the REST client:
     
    http://
    DA_host
    :8581/typecatalog/components
     
     
  4. Select
    POST
    for the
     'HTTP' Method
    .
     To update an existing component, select 
    PUT
    .
  5. Select 
    'application/xml'
     as the 
    'Body Content-type'
    .
  6. Add the customized XML within the "Body" text section.
  7. Run the method.
Create a New Metric Family
A metric family describes the metrics available for collection for a component. Different vendors can provide information for all or part of the metrics in a metric family. For each metric, a metric family defines the behavior of the system. For example, a metric family can define whether to calculate baselines, percentiles, minimum, maximum, or projections. They also define how to calculate rollups. Only some fields in the metric family XML require changes. The 
Indexes
Names
, and 
Description
 attributes are mandatory. You should add one or more metric attributes to reflect the number and type of metrics in the metric family.
 
Follow these steps:
 
  1. Customize the following XML:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- Auto-generated by the type catalog local manager. -->
    <DataModel xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance namespace="http://im.ca.com/normalizer" xsi:noNamespaceSchemaLocation="IMDBCertificationFacet.xsd">
    <Author>Custom</Author>
    <Version>1.0</Version>
    <FacetType name="
    Internal_Metric_Family_Name
    "
    descriptorClass="com.ca.im.core.datamodel.certs.NormalizedFacetDescriptorImpl">
    <Documentation>
    Metric_Family_Description
    </Documentation>
    <FacetOf namespace="http://im.ca.com/core" name="Item" />
    <AttributeGroup name="AttributeGroup" external="true" list="true">
    <Documentation />
    <Attribute name="Indexes" type="ObjectID[]">
    <Documentation />
    <Polled>false</Polled>
    <Baseline>false</Baseline>
    <IsDbColumn>false</IsDbColumn>
    <Variance>false</Variance>
    <StandardDeviation>false</StandardDeviation>
    <Minimum>false</Minimum>
    <Maximum>false</Maximum>
    <WriteOnPoll>false</WriteOnPoll>
    <RollupStrategy />
    <AttributeDisplayName />
    <Percentile>0</Percentile>
    </Attribute>
    <Attribute name="Names" type="String">
    <Documentation>
    Element/Component_Name
    </Documentation>
    <Polled>false</Polled>
    <Baseline>false</Baseline>
    <IsDbColumn>false</IsDbColumn>
    <Variance>false</Variance>
    <StandardDeviation>false</StandardDeviation>
    <Minimum>false</Minimum>
    <Maximum>false</Maximum>
    <WriteOnPoll>false</WriteOnPoll>
    <RollupStrategy />
    <AttributeDisplayName />
    <Percentile>0</Percentile>
    </Attribute>
    <Attribute name="Description" type="String">
    <Documentation>
    Element/Component_Description
    </Documentation>
    <Polled>false</Polled>
    <Baseline>false</Baseline>
    <IsDbColumn>false</IsDbColumn>
    <Variance>false</Variance>
    <StandardDeviation>false</StandardDeviation>
    <Minimum>false</Minimum>
    <Maximum>false</Maximum>
    <WriteOnPoll>false</WriteOnPoll>
    <RollupStrategy />
    <AttributeDisplayName />
    <Percentile>0</Percentile>
    </Attribute>
    <Attribute name="
    Metric_Name
    " type="
    MIB_Metric_Type
    ">
    <Documentation>
    Metric_Description
    </Documentation>
    <Polled>true</Polled>
    <Baseline>false</Baseline>
    <IsDbColumn>true</IsDbColumn>
    <Variance>false</Variance>
    <StandardDeviation>false</StandardDeviation>
    <Minimum>false</Minimum>
    <Maximum>false</Maximum>
    <WriteOnPoll>false</WriteOnPoll>
    <RollupStrategy>Sum</RollupStrategy>
    <AttributeDisplayName />
    <Percentile>0</Percentile>
    </Attribute>
    </AttributeGroup>
    <Attribute name="SourceFacetTypes" cached="true" list="true" persistent="true" type="QName">
    <Documentation />
    </Attribute>
    <DisplayName>
    External_Metric_Family_Name
    </DisplayName>
    <Expressions>
    <ExpressionGroup destCert="{http://im.ca.com/core}Item">
    <Expression destAttr="Name">Names</Expression>
    </ExpressionGroup>
    <ExpressionGroup destCert="{http://im.ca.com/inventory}DeviceComponent">
    <Expression destAttr="IndexList">Indexes</Expression>
    </ExpressionGroup>
    </Expressions>
    <TableName>
    DB_Table_Metric_Family_Name
    </TableName>
    <ComponentFacets>
    <Facet>{http://im.ca.com/inventory}
    Component_Name
    </Facet>
    </ComponentFacets>
    <Protocol>IMDB</Protocol>
    <Normalized>true</Normalized>
    </FacetType>
    </DataModel>
     
    •  
       
      Internal_Metric_Family_Name
       
      Specifies the metric family name. For each metric family, the name must be a unique name that identifies it internally within the system. Carefully select a name with a minimal possibility of naming conflicts with future similar metric families. For example, define a naming scheme that ensures that these metric family names are unique.
      This name is never exposed externally. To display a metric family name in the user interface, use the DisplayName
       
      element.
      Can be updated: No
      Possible values: Alphanumeric and underscore. Dot and dash are not permitted. The value must be unique across all metric families.
    •  
       
      Metric_Family_Description
       
      Specifies the external description for the metric family. To make these comments useful, describe why and when you added or changed the metric family.
      Possible values: Plain text
      Effect of updating: None
    •  
       
      Element/Component_Name
       
      The documentation is also displayed in tool tips when you hover the cursor over the attribute name.
    •  
       
      Element/Component_Description
       
      Displays the attribute description in the user interface. The documentation is also displayed in tool tips when you hover the cursor over the attribute name.
      Possible values: Plain text
      Effect of updating: Hovering the cursor over the attribute name shows the updated documentation.
       
       
       
    •  
       
      Metric_Name
       
      Specifies the unique, internal name. For metrics, this name is also used for naming the database column.
       This name is never exposed externally. To display an attribute name in the user interface, use the AttributeDisplayName
       
      element. To change the AttributeDisplayName, see Create or Extend Metric Families and update the metric family properties.
      Possible values: Alphanumeric and underscore.
      Effect of updating: For metrics, the values for this attribute are stored in a new database column corresponding to the updated name. The user loses the historical data that is collected for this metric (with the older name). The custom reports that report on this metric fails.
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
       
      MIB_Metric_Type
       
      Indicates the data type of this attribute. The most frequently used data types are 
      Int
      Long
      Double
      String
      , or 
      ObjectID
      . The database stores metric attributes as a float. Therefore, these attributes must use a numeric type (we recommend a Double). Other types are used for item attributes.
      Possible values:
       Boolean, Int, Long, Double
       (floating-point), 
      BigInteger, String, DateTime, IPAddress, MACaddress, IPSubnet, OctetString
       (hex representation), 
      ObjectID, ItemID, QName
       (Qualified Name)
      The type names are case insensitive, for example, "boolean" is the same as Boolean.
      Effect of updating: For metrics, none. All metrics are stored in the database as a float. For item attributes, the device must be deleted and rediscovered.
      When does the update take effect: For metrics, next poll. For item attributes, on rediscover.
      Required actions for updates to take effect: For metrics, none. For item attributes, delete the device and rediscover.
    •  
       
      Metric_Description
       
      Displays the attribute description in the user interface. The documentation is also displayed in tool tips when you hover the cursor over the attribute name.
      Possible values: Plain text
      Effect of updating: Hovering the cursor over the attribute name shows the updated documentation.
    •  
      Baseline
      Indicates whether to calculate a mean value for this attribute. If it is set to true, a corresponding 
      BaselineList
       
       
      definition must be defined.
      The Baseline
       
      attribute requires that the StandardDeviation
       
      attribute is set to true.
      Possible values: true, false
      Effect of updating: Baseline values are calculated when true.
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
      Variance
      This tag has restricted use in custom and extended metric families. The value of this tag must be 'false'.
    •  
      Standard Deviation
      Indicates whether to calculate the standard deviation of this attribute during the rollup. Creates a '
      std
      _' column in the database table. If 
      RollupStrategy
       is defined, this attribute must also be defined.
      Possible values: true, false
      Effect of updating: True provides a calculation of, and a reporting field for, “Standard Deviation.”
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
      Minimum
      Indicates whether to calculate the minimum of this attribute during the rollup. Creates a '
      min
      _' column in the database table. If 
      RollupStrategy
       is defined, this attribute must also be defined.
      Possible values: true, false
      Effect of updating: True provides a calculation of, and a reporting field for, “Minimum.”
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
      Maximum
      Indicates whether to calculate the maximum of this attribute during the rollup. Creates a 'max_' column in the database table. If 
      RollupStrategy
       is defined, this attribute must also be defined.
      Possible values: true, false
      Effect of updating: True provides a calculation of, and a reporting field for, “Maximum.”
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
      RollupStrategy
      Specifies the operation that is performed every cycle during the rollup of the individually polled values. When Polled
       
      and 
      IsDbColumn
       
       
      are set to true, this element is required.
      Possible values: Sum (a summation for counters), Avg (an average for gauges)
      Effect of updating: The specified strategy is used to perform rollup calculations.
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
      Percentile
      Indicates whether to calculate the 95th percentile of this attribute during the rollup. Creates a 'pct_' column in the database table. If 
      RollupStrategy
       is defined, this attribute must also be defined.
      Possible values: 0, 95
      Effect of updating: A value of 95 provides a calculation of, and a reporting field for, “95th Percentile.” Zero specifies that no calculation is performed, and the reporting field is not available.
      When does the update take effect: Next poll
      Required actions for updates to take effect: None
    •  
       
      External_Metric_Family_Name
       
      Specifies the metric family name that displays in the user interface.
      Possible values: Plain text
      Ensure that the DisplayName property is unique to the metric family.
      Effect of updating: Change to the name in the administrator user interface.
      When does the update take effect: Immediately
      Required actions for updates to take effect: Refresh the user interface.
    •  
       
      DB_Table_Metric_Family_Name
       
      Specifies the database table name that is used to store the metrics that the metric family collects.
      Possible values: Uppercase alphanumeric and underscore. The value must begin with a letter. The value must be unique across all metric families.
      Example: PROCESS_STATS
      Effect of updating: Poll data is stored in a new set of database tables.
       When you update the
       
      TableName, the old poll data is lost. Old report views are broken.
      When does the update take effect: Immediately. Before new views can be created, there is a delay of up to 5 minutes while 
      CA Performance Management
       loads the new MIB files.
      Required actions for updates to take effect: Views must be recreated.
    •  
       
      Component_Name
       
      Specifies a facet that is attached to the component item during component discovery.
      Can be updated: Yes
      Possible values
      :QName
       of the facet
      Effect of updating: If the component facet is synchronized to 
      Performance Center
      , the component is visible in 
      Performance Center
      .
      When does the update take effect: Rediscover
      Required actions for updates to take effect: Delete the device and rediscover.
  2. Set up a REST client with a connection to the Data Aggregator server.
  3. Use the following format for the URL in the REST client:
     
    http://
    DA_host
    :8581/typecatalog/components
     
     
  4. Select
    POST
    for the
     'HTTP' Method
    .
     To update an existing component, select 
    PUT
    .
  5. Select 
    'application/xml'
     as the 
    'Body Content-type'
    .
  6. Add the customized XML within the "Body" text section.
  7. Run the method.
Create a New Vendor Certification
A vendor certification provides a link between the vendor MIB and the metrics in the metric family. A vendor certification specifies which MIB variables are used for the relevant metrics. A vendor certification also specifies the formulas or expressions that are used to calculate the relevant values. Some variables directly match a metric (for example, rate, errors, discards, and volume). Others variables require calculations (for example, utilization or free disk space).
If scalar OIDs need to be polled in the vendor certification, the definition of attributes changes slightly. If you are grouping scalar OIDs for better organization within an 
AttributeGroup
, set the list variable to false (list=”false”). Or, omit the variable in the 
AttributeGroup
 tag definition. 
list=”true”
 in a vendor certification appends the index to the OID when polling. When you define the attribute source, append a ‘.0’ to the end of the OID. You can also have scalar OIDs defined outside of an 
AttributeGroup
.
 
Follow these steps:
 
  1. Customize the following XML:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- Auto-generated by the type catalog local manager.-->
    <DataModel namespace="http://im.ca.com/certifications/snmp" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="SNMPCertificationFacet.xsd">
    <Author>Custom</Author>
    <Version>
    Version
    </Version>
    <FacetType name="
    Internal_Vendor_Cert_Name
    "
    descriptorClass="com.ca.im.core.datamodel.certs.CertificationFacetDescriptorImpl">
    <Documentation>
    Vendor_Cert_Description
    </Documentation>
    <FacetOf namespace="http://im.ca.com/core" name="Item" />
    <AttributeGroup name="AttributeGroup" external="true" list="true">
    <Documentation />
    <Attribute name="INDEX" type="ObjectID">
    <Documentation />
    <Source>
    Index_OID
    </Source>
    <IsIndex>true</IsIndex>
    <IsKey>false</IsKey>
    <NeedsDelta>false</NeedsDelta>
    </Attribute>
    <Attribute name="
    Internal_Metric_Name
    " type="
    Data_Type_from_MIB
    ">
    <Documentation />
    <Source>
    MIB_Variable_OID
    </Source>
    <IsIndex>false</IsIndex>
    <IsKey>true</IsKey>
    <NeedsDelta>true</NeedsDelta>
    </Attribute>
    </AttributeGroup>
    <Protocol>SNMP</Protocol>
    <DisplayName>
    Vendor_Cert_Name
    </DisplayName>
    <Expressions>
    <ExpressionGroup destCert="{http://im.ca.com/normalizer}
    Metric_Family_Name
    " name="
    Metric_Family_Name
    ">
    <Expression destAttr="Indexes">INDEX</Expression>
    <Expression destAttr="Names">"
    Element_Name
    " + INDEX</Expression>
    <Expression destAttr="
    Metric_Name
    ">
    Internal_Metric_Name_or_MVEL_Expression
    </Expression>
    </ExpressionGroup>
    </Expressions>
    <MIB>
    MIB_Name
    </MIB>
    </FacetType>
    </DataModel>
     
    •  
       
      Version
       
      Specifies the vendor certificate version.
      Example: 1.0
    •  
       
      Internal_Vendor_Cert_Name
       
      Uniquely identifies a vendor certification.
      Recommendation: Conform to "
      <MibName><TableName>Mib
      ."
      Can be updated: No
      Possible values: Alphanumeric and underscore. Dot and dash are not permitted.
    •  
       
      Vendor_Cert_Description
       
      Describes what is certified with the vendor certification.
      Recommendation: Include the details about the vendor, MIB name, and table name.
      Effect of updating: None
    •  
       
      Index_OID
       
      Specifies the 
      ObjectID
       of the attribute.
      Recommendation: Set to the fully qualified MIB variable OID that the OBJECT-TYPE defines.
      Possible values: Dot-separated numbers (for example, 1.3.6.1.4.1…)
      Effect of updating: Data is polled from the specified OID.
      When does the update take effect: Next poll
       By default, the 
      Source
       attribute specifies an OID to poll from the device. This default behavior is defined with 
      src='polled'
      . You can set 
      src='mvel' 
      to process an MVEL expression using any polled attribute instead of an OID. For example, you could use the 
      src='mvel'
       parameter to combine two 32-bit OIDs into a single 64-bit counter. You could also use the 
      src='mvel'
       parameter to poll a counter that is not stored as a numeric type.
      Example: The following example uses the 
      src='mvel'
       parameter to combine two 32-bit OIDs into a single 64-bit counter:
      <Attribute name="memberbitsout" type="Long">
      <NeedsDelta>true</NeedsDelta>
      <Source
      src='mvel'
      >snmpCounter64(memberbitsoutHi32,memberbitsoutLo32)</Source>
      </Attribute>
      The 
      src='mvel'
       parameter can only be used during polling. This parameter cannot be used during the discovery phases. For example, this parameter cannot be used as part of the Name or Description.
    •  
       
      Internal_Metric_Name
       
      Specifies the attribute name.
      Recommendation: Set to the MIB variable name, which the OBJECT-TYPE clause defines in the ASN.1 file.
      Possible values: Alphanumeric and underscore. Dot and dash are not permitted.
      Effect of updating: Update any expressions that reference this attribute.
    •  
       
      Data_Type_from_MIB
       
      Specifies the data type of the attribute.
      Recommendation: Use the attribute type that best matches the variable type that the SYNTAX clause defines in the ASN.1 file.
      Possible values: 
      Boolean, Int, Long, Double, BigInteger, String, DateTime, IPAddress, MACaddress, IPSubnet, OctetString, ObjectID
      Effect of updating: Polled SNMP data is converted to this type.
      When does the update take effect: Next poll
       
       
       
       
       
       
       
    •  
       
      MIB_Variable_OID
       
      Specifies the 
      ObjectID
       of the attribute.
      Recommendation: Set to the fully qualified MIB variable OID that the OBJECT-TYPE defines.
      Possible values: Dot-separated numbers (for example, 1.3.6.1.4.1…)
      Effect of updating: Data is polled from the specified OID.
      When does the update take effect: Next poll
       By default, the 
      Source
       attribute specifies an OID to poll from the device. This default behavior is defined with 
      src='polled'
      . You can set 
      src='mvel' 
      to process an MVEL expression using any polled attribute instead of an OID. For example, you could use the 
      src='mvel'
       parameter to combine two 32-bit OIDs into a single 64-bit counter. You could also use the 
      src='mvel'
       parameter to poll a counter that is not stored as a numeric type.
      Example: The following example uses the 
      src='mvel'
       parameter to combine two 32-bit OIDs into a single 64-bit counter:
      <Attribute name="memberbitsout" type="Long">
      <NeedsDelta>true</NeedsDelta>
      <Source
      src='mvel'
      >snmpCounter64(memberbitsoutHi32,memberbitsoutLo32)</Source>
      </Attribute>
      The 
      src='mvel'
       parameter can only be used during polling. This parameter cannot be used during the discovery phases. For example, this parameter cannot be used as part of the Name or Description.
    •  
       
      Vendor_Cert_Name
       
      Specifies the name of the vendor certification as it displays in 
      Performance Center
      .
      Recommendation: Start with the vendor name and include the MIB and functionality information.
      Effect of updating: A change to the name in the Administrator user interface.
      When does the update take effect: Immediately
      Required actions for updates to take effect: Refresh the user interface.
      Ensure that the DisplayName property is unique to the vendor certification.
    •  
       
      Metric_Family_Name
       
      Specifies the metric family that contains the 
      destAttrs
       to populate.
      Possible values: Any valid metric family
      Effect of updating: Changes the permissible expression 
      destAttr
      .
    •  
       
      Element_Name
       
      Specifies to use the vendor certification attributes to collect configuration data. This configuration data helps define the MVEL expression to provide the value for the Names metric family attribute.
      Recommendation: Include as much information as necessary to identify an instance uniquely.
      Possible values: String MVEL expression using available Attributes
      Effect of updating: Component name change
      When does the update take effect: After component rediscovery
      Required actions for updates to take effect: Update the metric family or change the vendor certification priority.
    •  
       
      Metric_Name
       
      Specifies the metric name as defined in the metric family.
    •  
       
       
       
      Internal_Metric_Name_or_MVEL_Expression
       
       
       
      Specifies the internal metric name as defined in the attribute section. Or, specifies the relevant formula that is used to calculate the metric from the MIB variable represented by the internal metric name.
    •  
       
      MIB_Name
       
      Specifies the name of the MIB, which the DEFINITIONS clause defines in the ASN.1 file.
      Recommendation: Conform to "<MibName>”
      Effect of updating: Change to the “SNMP MIB Name” column in the Vendor Certification tab of the Administrator user interface.
      When does the update take effect: Immediately
      Required actions for updates to take effect: Refresh the user interface.
  2. Set up a REST client with a connection to the Data Aggregator server.
  3. Use the following format for the URL in the REST client:
     
    http://
    DA_host
    :8581/typecatalog/certifications/snmp
     
     
     To update or extend a vendor certification, use the following format for the URL in the REST client:
     
    http://
    DA_host
    :8581/typecatalog/certifications/snmp/
    cert_name
     
     
     
     
    cert_name
     
     
    Specify the name of the existing certification.
  4. Select
    POST
    for the
     'HTTP' Method
    .
     To update or extend a vendor certification, select 
    PUT
    .
  5. Select 
    'application/xml'
     as the 
    'Body Content-type'
    .
  6. Add the customized XML within the "Body" text section.
  7. Run the method.