Super Contributor.. chuchi Super Contributor..
Super Contributor..
170 views

AMGenericAdapter Push DisplayMonitors

Hello:

We have an issue in our Push Integration between UCMDB 2019.02 and AssetManager 9.63.

Let me explain it:

We have in UCMDB a scanned computer (i98822) that contains a DisplayMonitor (with serial number CNT702013V). This represents as the computer with a composition relation to the displayMonitor

node-displaymonitor.JPG

 

We have in Asset the same computer (i98822) that contains another different Monitor (with serial number CND6521G4M). This represents as the computer with a component of Monitor.

node-monitor.JPG(The Monitor CNT702013V is associated to another computer)

The am-push-config-xml is:

 

    <am-mapping ci-type="Monitor-amPortfolio" name="AddOn" primary-key="lPortfolioItemId"
                operation-type="update_else_insert" parallel-push-allowed="true"
                merge-allowed="true" from-version="9.5">
        <reconciliation>
            <reconciliation-keys>
                <reconciliation-key>GlobalId</reconciliation-key>
            </reconciliation-keys> 
            <reconciliation-keys>
                <reconciliation-key>Folder</reconciliation-key>
                <reconciliation-key>lParentId</reconciliation-key>
            </reconciliation-keys>
        </reconciliation>
        <reference-attribute ci-name="Monitor-amModel" datatype="STRING" name="lModelId" reference-direction="child"/>
        <reference-attribute ci-name="Portfolio" datatype="STRING" name="lParentId" reference-direction="parent"/>
        <action-on-delete condition="Model.Nature.code='MON'">
            <set-attribute-value name="seAssignment" datatype="INTEGER" value="6"/>
        </action-on-delete>
    </am-mapping>

 

What we want is that ,the Push Integration associates in Asset the right monitor (CNT702013V) to the computer I98822, and then the monitor that already associated (CND6521G4M) with the computer stays "missing"

Any idea for the code of am-push-config-xml

 

 

Thanks.

0 Likes
2 Replies
Micro Focus Contributor
Micro Focus Contributor

Re: AMGenericAdapter Push DisplayMonitors

Hi

Based on the screenshots that you sent us the code number of the monitor looks correct HP L1706, also we would like to check what is the AMGenericAdapter that you are using for the integration. If you have addtional concerns can be good idea work this request on a new support case. 

BR

Andres VM

 

0 Likes
Super Contributor.. chuchi Super Contributor..
Super Contributor..

Re: AMGenericAdapter Push DisplayMonitors

Hello AndresVM1:

 

The AMGenericAdapter is 1.04 (integrated with UCMDB 2019.02).

 

Don't look at the code number, because UCMDB detects all displaymonitors of this kind with this code number (HP L1706).
You should look at the serialnumber of the DisplayMonitor. (this attribute identifies unique display monitor)

The UCMDB situation is this:

node-monitor2.JPG

The AssetManager situation is this:

node-monitor.JPGAs you see, the computer in UCMDB contains a monitor (CNT702013V) which is different from the one in AssetManager (CND6521G4M)

 

What we want with the code of am-push-config.xml, is that the Integration associates the right monitor (CNT702013V) to the same computer in AssetManager.

The different monitor (CND6521G4M) that was associated with the computer in AssetManager should stays in "missing"

 

BR.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.