This documentation supports the 18.05 version of BMC Atrium Core.

To view the latest version, select the version from the Product version menu.

Creating a Version Rollup rule

You can create a Version Rollup rule to assign a single value to the MarketVersion attribute of a product. BMC Remedy ITSM uses this value for license management. The rule also defines a qualification to select the instances that are assigned the new value. A rule normalizes multiple VersionNumber strings to a particular MarketVersion value.

Version Rollup default behavior  

  • The Version Rollup feature is enabled for data sets, and it checks all active Version Rollup rules. 
  • Version Rollup rules apply to CIs in the BMC_Product class. 
  • The MarketVersion value in the Version Rollup rule takes precedence over a Product Catalog entry.

The Normalization Engine includes Version Rollup rules for a number of products from manufacturers such as Microsoft Corporation, Oracle Corporation, and Adobe Systems. You must create rules for other products.

When you create new rules for the products, you can check whether the Version Rollup rules already exist for a product or a manufacturer by using the Filter By field available on the Version Rollup tab.

Best Practice

  • BMC recommends that you do not edit or delete the Version Rollup rules that are shipped with the product.
    Instead of editing a rule, create a new rule and copy the desired qualification and other values to it. You can then modify this new rule.
  • BMC recommends that the Version Rollup rule be based on normalized product names, and are used after alias application. For more information, see Normalization process.
  • When you search for existing Version Rollup rules, the search results depend on the case sensitivity of the underlying database.
    For example, for a case-sensitive database, if you enter a search string as "adobe", it treats "adobe" and "Adobe" differently. The search result does not list the rules for "Adobe". However, if the underlying database is case insensitive, the search string "adobe" lists the rules for "adobe" as well as "Adobe".
If the Normalization Engine does not find a specific rule for a product, and if the CI  does not have a value for  MarketVersion, the Normalization Engine uses a default rule to set  MarketVersion to the  VersionNumber value. If the CI  does have a value for  MarketVersion, the Normalization Engine retains this value. 

Use manufacturer aliases to reduce the number of Version Rollup rules that the Normalization Engine uses to match the ManufacturerName attribute as explained in Normalization process

To create a Version Rollup rule

  1. On the CMDB Dashboard, click Configurations.
  2. From the list, click Manage Normalization Rules > Features.
  3. Select the Version Rollup tab.
  4. Click  to create a new Version Rollup rule.
    With the Filter by field, you search for existing Version Rollup rules for a particular manufacturer or product. You can use % (percentage sign) for a wildcard search. 
  5. In the Create Version Rollup Rule page, configure the following parameters.

Parameter Description
Rule Name Specify a unique name for the rule.
Active Click the toggle button to activate the rule so that the Normalization Engine applies the rule to data sets.
Precedence Enter a value to determine the rule's execution order. The value can be 0 to 9999999, both inclusive, with higher numbers determining a higher priority. If more than one rule applies to an instance, the Normalization Engine applies the rules sequentially from the highest precedence value to the lowest, until a match is found.
Product Name Specify the Model the instance need to have to qualify for this rule. If you are using product aliases, make sure that the value in this field is the same as the value in the ActualName field in the Normalization Alias form. The value in the ActualName field should in turn match the Product Name field in the corresponding Product Catalog entry.

Class Name Select the name of the class from the list, for which the qualification returns instances.
Manufacturer Name Specify the ManufacturerName the instance need to have to qualify for this rule. If you are using manufacturer aliases, make sure that the value in this field is the same as the value in the ActualName field in the Normalization Alias form. The value in the ActualName field should in turn match the Manufacturer Name field in the corresponding Product Catalog entry.
Market Version Specify a value to apply to the MarketVersion attribute of the instances that match your qualification. You can specify either an exact value, such as 2003, or an expression that generates the MarketVersion value. If you specify plain text with special characters, you must put the entire text in double quotation marks.

The following examples are of expressions that you can specify in the Market Version field:  

  • MAJOR($VersionNumber$) — This expression extracts the major version from the VersionNumber attribute of the qualified instances and applies that value to the MarketVersion attribute. For example, if the VersionNumber attribute value is 11.5 or 11.7, this expression populates 11 as the value of the MarketVersion attribute. 
  • MAJORMINOR($VersionNumber$) — This expression extracts the major and minor version numbers from the VersionNumber attribute. For example, if VersionNumber contains 5.1.2, this expression populates 5.1 as the value of the MarketVersion attribute. 
  • $VersionNumber$ — This expression applies the VersionNumber attribute value of the qualified instances to the MarketVersion attribute. For example, if the VersionNumber attribute value is 10.20.01, this expression populates 10.20.01 as the value of the MarketVersion attribute.
Qualifier

Enter the qualification or to build it, click . Use BMC Remedy AR System qualifications to define the CIs or relationships to which the custom rule applies. For information about using the Qualification Builder, see Using the Qualification Builder.

The additional qualification can also be written using an alias name.

       6. Click Save.

To edit a Version Rollup rule

  1. On the CMDB Dashboard, click Configurations.
  2. From the list, click Manage Normalization Rules > Features.
  3. Click the Version Rollup tab.
  4. Select an existing Version Rollup Rule that you want to edit, and click .
  5. In the Edit Version Rollup Rule page, configure the required parameters as explained for creating a Version Rollup Rule.

6. Click Save.

To delete a Version Rollup rule

  1. On the CMDB Dashboard, click Configurations.
  2. From the list, click Manage Normalization Rules > Features.
  3. Click the Version Rollup tab.
  4. Select an existing Version Rollup Rule you want to delete, and click 
  5. In the Delete Version Rollup Rule dialog box, click OK to confirm the deletion.

To enable or disable Version Rollup for a data set

  1. On the CMDB Dashboard, click Configurations.
  2. From the list, click Manage Normalization Rules > Dataset Configurations.
  3. On the Dataset Configurations page, select the data set for which you want to enable or disable the Version Rollup rule, and click 

    Note

    Only rules that are active are executed.

  4. On the All Datasets Configurations page, Supported Features section, select or clear the Version Rollup check box to enable or disable the feature.


  5.  Click Save to apply the change.


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

Comments

  1. Thomas Schuhn

    Is it possible to use further classes? For example BMC_OperatingSystem. In older versions you could add additional classes.

    Oct 10, 2018 09:47