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?
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...
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'