UCMDB Support Tip: How to handle uCMDB-BSM class model differences
In the event RTSM population job in BSM fails when trying to load uCMDB data, seemingly caused by class model differences. Product versions are old but cannot be upgraded due to environment restrictions.
uCMDB 09.x BSM 9.x
The class model in uCMDB has been modified extensively, with the following types of changes: - new CI types added within 'Configuration Item'. - new CI types added within 'Infrastructure Element'. - CI type label definition format changes on some standard CI types. And specifically: - New and modified attributes on some standard CI types (e.g. Node, Printer). - Modified 'Managed Application' CI type to add 'Service ID' as key field and remove 'Name' as a key field.
As a result, the following potential options has been identified:
- Export class model from uCMDB and import into BSM (does this cause an issue down the line for CP upgrade).
>> Yes, this will cause an issue, have you done this already,, since BSM is more complex product and most of the CP and some things should remain unchanged.
2. Apply discovery packages and other manual changes to BSM as have been applied to uCMDB.
>>No CP updates to BSM product should be applied, since BSM is more complex product, it is not allowed to update the CP package on it.
3. Modify the population job to exclude the added classes (is this enough given the other changes that have been made to the class model).
>>Yes, but please let us know what changes you have made, so that we can have a better understanding and advice.
4. Manually apply all changes to the class model in BSM as have been applied to uCMDB.
>>Yes, this is the best method to do it.
5. Is it primarily the new/changed attributes on the CITs that would be causing the population job to fail? Rather than other CITypes that are not involved in the query?
>> Only differences in the CIT being populated would cause the error
6. How do one easily compare class models between the two products? If one can only find an export to PDF option in the CIT list.
>> One can export the class model to xml file via jmx console then use file compare to compare the differences.
7. Unable to find any documentation on the process to exclude CITypes (or attributes) from the population job - for example the BasicInfrastructureSync job. Is there any available?
>> Please refer to the attached file, which contains such procedures.
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'