Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
675 views

INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

Hi,

We have several problems with the integration of uCMDB 10.31 and Asset Manager 9.63:
- If the scanner of a computer detects 1 monitor, why do the properties of the node keep the relationships with other monitors previously connected?
- The same happens with the Software Installations.
- According to the manuals, delta sync would only load the equipment received since the last execution of the integration, but in our case  it reprocesses all the equipment. We had to add a filter to the TQL am-node-push to process the modified equipment in the last 24 hours.
- During the execution of the integration, all monitors in Asset Manager that are not associated with any equipment, are placed in a "missing" situation.

I enclose the file am-push-config.xml in case you can help me check your configuration.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

- If the scanner of a computer detects 1 monitor, why do the properties of the node keep the relationships with other monitors previously connected?

LA1951 monitor from your screenshot is beind deleted so will disappear from the connection to your node (you can see the serial numbers changed). maybe you talk about i99794. I see the last access time to be from 2017. Maybe it has been removed before you enabled AutoDelete. Maybe there was error in the synchronization and the cache has been removed, or the DFP was reinstalled. There are different reasons why it is not removed automatically and if a recent case for that happens, it can be eventually looked for a resolution. Best solution to find such cases is an enrichment, which will start aging items, which haven't changed their LastAccessTime in the last 24 hours even though the scanned has been processed in the last 24 hours. 


- The same happens with the Software Installations.

Same as above.
- According to the manuals, delta sync would only load the equipment received since the last execution of the integration, but in our case  it reprocesses all the equipment. We had to add a filter to the TQL am-node-push to process the modified equipment in the last 24 hours.

Delta sync finds the differences from the TQL since last execution and pushes them to AM. In many cases only if you push DisplayMonitor, it is not enough to make the reconciliation in AM. Therefore the related CIs have to be sent with the changed CI as well. Can you show example when something is pushed, but it shouldn't?
- During the execution of the integration, all monitors in Asset Manager that are not associated with any equipment, are placed in a "missing" situation.

I believe this is more a question for AM and not UCMDB?

Likes are appreciated!

View solution in original post

5 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

Hi MVOB,

can you please verify what integration are you using. Is it push or population? Are you talking about UD scanner? Where does the relationship with other monitors stay - in UCMDB or AM? There is no software installation CI type in UCMDB. 

If you talk about that the scanner has detected 10 Installed Software first run, and then scanner has detected 9 Installed Software, there are two methords to take care of the one Installed Software which went missing - either through aging or through auto deletion. 

Where are you doing the delta sync from? Is the data flowing from AM to UCMDB or through UCMDB to AM? If you make delta sync from AM, you can check the SQL query sent to AM and see why it returns more results. There is no TQL with name am-node-push in UCMDB to check it. 

 

Likes are appreciated!
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

Good morning and thank you very much for your interest.
I answer your questions:

We are using push integration.
We execute the UD scanner.
The relationship with other monitors is maintained in uCMDB, and the Ucmdb-Asset push integration replicates the monitors' association in Asset (see attached document).
The situation with the software is what you expose.
We have activated the aging and also the automatic removal (see attached document).
Our synchronization is only from uCMDB to Asset.
Attachment file am-node-push.xml for checking.

Thank you!

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

- If the scanner of a computer detects 1 monitor, why do the properties of the node keep the relationships with other monitors previously connected?

LA1951 monitor from your screenshot is beind deleted so will disappear from the connection to your node (you can see the serial numbers changed). maybe you talk about i99794. I see the last access time to be from 2017. Maybe it has been removed before you enabled AutoDelete. Maybe there was error in the synchronization and the cache has been removed, or the DFP was reinstalled. There are different reasons why it is not removed automatically and if a recent case for that happens, it can be eventually looked for a resolution. Best solution to find such cases is an enrichment, which will start aging items, which haven't changed their LastAccessTime in the last 24 hours even though the scanned has been processed in the last 24 hours. 


- The same happens with the Software Installations.

Same as above.
- According to the manuals, delta sync would only load the equipment received since the last execution of the integration, but in our case  it reprocesses all the equipment. We had to add a filter to the TQL am-node-push to process the modified equipment in the last 24 hours.

Delta sync finds the differences from the TQL since last execution and pushes them to AM. In many cases only if you push DisplayMonitor, it is not enough to make the reconciliation in AM. Therefore the related CIs have to be sent with the changed CI as well. Can you show example when something is pushed, but it shouldn't?
- During the execution of the integration, all monitors in Asset Manager that are not associated with any equipment, are placed in a "missing" situation.

I believe this is more a question for AM and not UCMDB?

Likes are appreciated!

View solution in original post

Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

Thank you very much for the reply.

Indeed, we have made reinstallations of DFP
Following your suggestions, we have managed the CIs that had not been automatically deleted, and we have made some changes in the integration TQL and we have verified that the delta synchronization works correctly.
After correcting delta synchronization, the problem with the monitors has not happened again in AM!
We assume that it has been a punctual failure

0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: INTEGRATION UCMDB 10.31 - ASSET MANAGER 9.63

Jump to solution

Hi!

In case it is of interest, the problem of the monitors placed in a 'missing' situation by the integration, was again produced in the following executions of the data sync from uCMDB to Asset.
I found the solution by adding an additional filter in the monitors' treatment, in <action-on-delete> (am-push.config.xml):

   <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> AssetTag </ 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" />
        <attribute-reconciliation attribute-name = "seAssignment" update-script = "(vOldVal == null || vOldVal.equals ('Missing'))? vNewVal: vOldVal" />
        <action-on-delete condition = "Model.Nature.code = 'MON' and lParentId> 0">
            <set-attribute-value name = "seAssignment" datatype = "INTEGER" value = "6" />
        </ action-on-delete>
    </ am-mapping>

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.