Most IT Assets within HPE Asset Manager (AM) will be shared with the Universal CMDB (UCMDB); but similar to UCMDB, not all Assets are CIs (and vice versa). There is an added complexity, where AM has the concept of a Portfolio Item (PI), which is a Super Class that AM Asset Classes share in common. Therefore, to ensure we consider all possible AM references that can be populated to UCMDB, the term PI will be used here to represent an Asset or Portfolio Item that can be linked with a CI. This is also important, because the managed state attribute for Assets (including computers) is at the PI Class.
It is critical that IT Asset Management (ITAM) and CMS agree on a common set of methods and reconciliation rules for managing the lifecycle of PIs related to CIs. These methods or rules are described in the accompanying documentation. Using UCMDB population integration, AM will insert a new CI record in the following use cases:
- when the lifecycle managed state of a PI is In use, or
- when a PI in AM is not in use (such as in stock), but is available to the CMS
In the second use case, an IT Service Management (ITSM) process (SRM, CCRM, and others) requests AM to add the PI to UCMDB before it is in service. However, this also means an ITSM process is now responsible for updating the AM PI state to In use when the populated CI is transitioned into service.
AM utilizes UCMDB's GDB Adapter technology and population integration. The AMDBadapter is pre-configured with the supported PI -> CI mapping classes and is shipped with Asset Manager.
This version of the integration aligns with Software Data Model v1.1.
Version 2.0 introduces a new population/federation approach that is implemented by the UCMDB Generic Adapter.
Portfolio Items are populated from AM to UCMDB by AMAdapter. Which CI types will be populated is based on three TQLs--hostDataImport, networkDataImport and printerDataImport.
Version 2.0 CI types are populated by a new set of TQLs in the Generic Adapter:
- AM Node Population 2.0
- AM Location Population 2.0
- AM Interface Population 2.0
- AM Printer Population 2.0
- AM BusinessElement Population 2.0
- AM BusinessElement Relations Population 2.0
Documentation for this integration can be found using the following links:
For an older version of this integration, please see Integration ID #307