Highlighted
Valued Contributor.. Valued Contributor..
Valued Contributor..
169 views

Push TQL results from HP UD 10.3 to BSM 9.21

Jump to solution

How to push the TQL results from HP UD  10.3 to BSM 9.21 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Push TQL results from HP UD 10.3 to BSM 9.21

Jump to solution

Data Push is the recommendation, if you have less than 500K CIs + Relationships to sync.

The CITs which are added automatically for reconciliation are done actually based on the source system. That's another reason to add the CITs to the TQL because you can control it and add the CITs which are needed for the target system reconciliation.

IP Address and Interface should be enough for reconciliation (look at the OOTB integration TQL for basic infrastructure).

Push TQLs are different than Pull TQLs. for PUSH there are no TQLs OOTB, but you can look at the SM Push TQLs and mimic them for RTSM. the Node sync should work as is. note that in PUSH TQLs you need 2 TQLs: one for the CIs and one of the Links. the object to sync must be named Root***, but you will find this in the SM examples.

Hope this recommendation helps,

MICRO FOCUS Software Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Please hit the Kudo botton, if you find this post useful.

View solution in original post

0 Likes
1 Reply
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Push TQL results from HP UD 10.3 to BSM 9.21

Jump to solution

Data Push is the recommendation, if you have less than 500K CIs + Relationships to sync.

The CITs which are added automatically for reconciliation are done actually based on the source system. That's another reason to add the CITs to the TQL because you can control it and add the CITs which are needed for the target system reconciliation.

IP Address and Interface should be enough for reconciliation (look at the OOTB integration TQL for basic infrastructure).

Push TQLs are different than Pull TQLs. for PUSH there are no TQLs OOTB, but you can look at the SM Push TQLs and mimic them for RTSM. the Node sync should work as is. note that in PUSH TQLs you need 2 TQLs: one for the CIs and one of the Links. the object to sync must be named Root***, but you will find this in the SM examples.

Hope this recommendation helps,

MICRO FOCUS Software Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Please hit the Kudo botton, if you find this post useful.

View solution in original post

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.