Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
319 views

TQL export to xml from one ucmdb and import to another fails

Jump to solution

Hi experts

we have two similar ucmdbs. One new and one old. I have around 200 queries and respective pattern views. I have exported to xml all these and I am trying to import to my new ucmdb that is filled with CIs but has no queries. And when I try to import in IMPORT FROM XML in modelling studio I get the UNDEFINED ERROR CODE without any other exaplnation

 

Is this the correct way to import export QUERIES (not the CIs) but just the tqls?

Does anybody know anything about that?

 

THANK YOU

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Hi there,

 

I had experienced a similar scenario in the past. The reason was I had exported only the views and not the associated queries. But you don't seem to be doing that. 

 

I'd recommend you to use package manager and bundle all your pattern views and the associated queries(of the same name) and export it out of one UCMDB instance and import it into the destination UCMDB instance. 

 

Administration --> Package Manager --> Create Custom package Wizard --> Enter package properties

In Resource Selection -- > Under Query --> Select Views and associated Queries

Click Finish

 

Hope this helps.

Praveen

View solution in original post

0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Hi ,

 

Would you please let us know the UCMDB version.Did you tried the following?

Open the UCMDB Server query manager, and export the query as local xml file.

The please export query as local xml file.

Run UCMDB connector wizard and configure the exported query for the connector

Following is to configure the business model of UCMDB, import the exported query. And there is one option to extract model. When there is name conflict in the query, extract business model should be set to avoid the name conflict. If the option is set, the query of server is not executed but the client-defined query definition.

 Wizard to import the query definition

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

on both sides

9.05.314

 

I will try your suggestion Ronald. But one question. Do I have to do this in the destination ucmdb for every of the 200 tqls that I have? 

 

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Hi

 

could you please elaborate a little bit on the below instructions with a little bit more details

 

Run UCMDB connector wizard and configure the exported query for the connector

Following is to configure the business model of UCMDB, import the exported query. And there is one option to extract model. When there is name conflict in the query, extract business model should be set to avoid the name conflict. If the option is set, the query of server is not executed but the client-defined query definition.

 Wizard to import the query definition

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Hi there,

 

I had experienced a similar scenario in the past. The reason was I had exported only the views and not the associated queries. But you don't seem to be doing that. 

 

I'd recommend you to use package manager and bundle all your pattern views and the associated queries(of the same name) and export it out of one UCMDB instance and import it into the destination UCMDB instance. 

 

Administration --> Package Manager --> Create Custom package Wizard --> Enter package properties

In Resource Selection -- > Under Query --> Select Views and associated Queries

Click Finish

 

Hope this helps.

Praveen

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.