Technical Bulletin
BMC Atrium Core
Version 7.6.04 Service Pack 2
英语的音标February 16, 2012
Announcing Product Catalog Data Prerequisite Patch 1, which introduces Normalization Engine enhancements. This patch is required for using the Product Catalog data entries shipped along with the BMC Atrium Core 7.6.04 - Product Catalog Data Update.
BMC Software is alerting urs of BMC Atrium Core 7.6.04 Service Pack 2 to the
availability of Product Catalog Data Prerequisite Patch 1. If you have any
questions about the patch, contact BMC Software Customer Support at 800 537naturalism
1813 (United States or Canada) or call your local support center.
Why apply Product Catalog Data Prerequisite Patch 1
Product Catalog Data Prerequisite Patch 1 introduces the following changes to the
Normalization Engine.
Support for the Product Catalog Data Update
So that the Normalization Engine can successfully normalize CIs using the Product
Catalog entries shipped along with the Product Catalog Data Update, you must
apply Product Catalog Data Prerequisite Patch 1.
BMC Atrium Core 7.6.04 - Product Catalog Data Update provides updated
Product Catalog entries instead of sourcing them from a third-party vendor. BMC
has created the Product Catalog entries bad on software products that are
discovered by the BMC Atrium Discovery and Dependency Mapping (BMC
Atrium Discovery) product.
For more information about the Product Catalog Data Update, e the online
documentation, located at /docs/display/pcdata.
241629
241629
*241629*
Software platforms
骚体
2Technical Bulletin February 16, 2012
Configuration changes to the Normalization Engine
Additionally, Product Catalog Data Prerequisite Patch 1 includes the following
changes to the Normalization Engine:
!
With this patch, configuration changes to the Normalization Engine are
introduced (e “Enhancements to the Normalization Engine” on page 3).
!
Applying the Atrium Core UI update contained within Product Catalog Data
Prerequisite Patch 1 significantly improves the loading performance of the
Version Rollup rules on the Normalization Engine console. For more
information e, “Applying the Atrium Core UI update” on page 13.Impact as an Attribute (IaaA) changes
The Product Catalog Data Prerequisite Patch 1 introduces new best-practice
relationship and impact normalization rules. With this patch:
! 1 best-practice relationship rule, which was shipped as a part of BMC Atrium
Core 7.6.04 Service Pack 2 is disabled,
! 1 best-practice relationship rule, which was shipped as a part of BMC Atrium
Core 7.6.04 Service Pack 2 is deleted,
! 1 new best-practice relationship rule is added and enabled,
!
1 new-best practice impact normalization rule is added and enabled.Thus, applying this patch enables 130 new best-practice relationship rules and 21
new best-practice impact normalization rules.
sofySoftware platforms
Product Catalog Data Prerequisite Patch 1 is supported on all the platforms
supported by BMC Atrium Core. For information about platforms supported by
BMC Atrium Core 7.6.04 Service Pack 2, e the Compatibility Matrix located at:
/support/reg/remedy-compatibilitytables.html .
Patch contents
Product Catalog Data Prerequisite Patch 1 includes the following folders:
!Atrium_Core_7604SP2_Update folder
托福培训班多少钱This folder contains the following folders and files:
!
arinfo.bat !
arinfo.sh !
NE-Enhancements !com_bmc_ne_feature_VersionRollupFeature.properties
Enhancements to the Normalization Engine
!datamig.bat
!datamig.sh
!
<
!
!
!install.bat
!install.sh
!neapi7604.jar
!l
!neplugin7604.jar
!l
!netools7604.jar
!
!
Atrium_UI-7604SP2_Update folder
This folder contains the following folders and files:
!aui-resources
!atrium-widget.jar
Enhancements to the Normalization Engine
This ction describe the enhancements to the Normalization Engine that Product
Catalog Data Prerequisite Patch 1 introduces.
Higher priority for Version Rollup rules
When you apply Product Catalog Data Prerequisite Patch 1, Version Rollup rules
get a higher priority than the Product Catalog data. The Normalization Engine
applies the Version Rollup rules to the discovered CI before arching for a
matching entry in the Product Catalog. When a CI is discovered, thealt
Normalization Engine first checks the applicable and activated Version Rollup
rules to t the MarketVersion attribute if required. The Normalization Engine
us this MarketVersion attribute for normalizing the discovered CI.
You can define Version Rollup rules to assign a value to the MarketVersion
attribute and a BMC Remedy AR System qualification to lect the instances that
are assigned the new value. The purpo is to allow you to normalize multiple
VersionNumber strings to a common value.
For example, you might have multiple versions for Microsoft Excel in your
environment: 11.0.5614.0, 11.0.6355.0, 11.0.7969.0, and 11.0.8173.0. However, you
bleedingmight want to track all the products by their MarketVersion of 2005.
To do this, define the following qualifier in the New Rule for Version Rollup dialog
box:
BMC Atrium Core Version 7.6.04 Service Pack 23
Enhancements to the Normalization Engine
(‘Name’ LIKE "Excel" AND ‘ManufacturerName’ LIKE "Microsoft %")
AND (‘VersionNumber’LIKE 11.0.%)
Set Market Version to 2005
steven是什么意思If the Normalization Engine encounters Microsoft Excel 11.0.5614.0, it first checks
this rule to t Market Version. Thus, Microsoft Excel 11.0.5614.0 has the
MarketVersion attribute value as 2005. The Normalization Engine now us the
value of the MarketVersion attribute to normalize the CI (in this example,
hoaMicrosoft Excel 11.0.5614.0).
Version Rollup Normalization feature is no longer optional With the Product Catalog Data Prerequisite Patch 1, version normalization no
longer remains an optional feature. The DML Bad Instance Normalization and
Version Rollup Normalization features are enabled for all datats by default and
cannot be configured for individual datats, including the custom datats.
IMPORTANT
Although the Version Rollup Normalization feature check box appears as an
option in the Configure Normalization Features dialog box, you need not lect
this check box. The Version Rollup Normalization feature is always run before the
DML Bad Instance Normalization feature.
Version Rollup Normalization feature is run before DML Bad Instance Normalization feature
The Normalization Engine now runs the Version Rollup Normalization feature
before the DML Bad Instance Normalization feature. Version Rollup
Normalization feature ts the MarketVersion attribute for instances to a common
value bad on default or custom rules.
With the DML Bad Instance Normalization feature, the Normalization Engine in
conjunction with the Product Catalog normalizes:
!Product categorization attributes: Category, Type, and Item (CTI)
!ManufacturerName
!Model (Product Name)
!MarketVersion
4Technical Bulletin February 16, 2012
Enhancements to the Normalization Engine
Normalization process
This ction describes the changed normalization process. Figure1-1 shows the
process of normalizing CIs in detail.
新概念英语第四册
Figure1-1:Version and DML Bad Instance Normalization process
BMC Atrium Core Version 7.6.04 Service Pack 25
