Established Member..
Established Member..

Best practices for UCMDB package builds migration between environments.

What are the suggested best pratices for performing UCMDB build propagation to other environments?

Ex. from Dev to Test to Prod, etc.


Packages containing all the related elements is the recommended way.


How about existing user data? Can that get affected in any way?


What are best practices and things to take care when performing package deployment to other environment?



Labels (1)
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: Best practices for UCMDB package builds migration between environments.

If you are just trying to push CIs from one UCMDB to another, use the UCMDB to UCMDB integration point in the integration studio.  When sending the CIs take care to send all reconciliation attributes plus any custom attributes you want to send.  In addition, make sure that the class models align for the 2 servers (so if you added a custom attribute to one UCMDB, you'll need to do so to the other as well, or a custom CI Type...

Hope this helps,
Keith Paschal
UCMDB Worldwide Support Lead
Micro Focus Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."

Click the KUDOS star on the left to say 'Thanks'
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.