1 of 1 people found this helpful
Yes a similar process can be used.
1. You don't necessarily need to make separate custom categories for these, you could use attributes associated to the location. Like region, country, and site could go in address or description (or some combination of both). You could also make Prod/Dev/QA/Staging a lifecycle status category and map that, so it'd need a separate CMDB sync pattern to get to the CMDB. There are some helpful threads about linking hosts to lifecycles here and here.
An easy thing to do would be assigning these as "display" attributes to your discovery nodes, so there would be no need for additional Categories, unless you really want them. When you write your TPL to figure out the subnet and assign the location and other related fields, use model.addDisplayAttribute. Here's some documentation on that: (Displaying custom attributes - BMC Discovery 11.3 - BMC Documentation )
2/3. If you use the Location attributes then you'd just map these additional attributes from that same pattern. If you use display attributes, you'd just map those attributes from your host node. template_cmdb_hostname_override could be used as a starting point, since it does the initial mapping right and then instead of the hostname work, you'd say something like computersystem.CMDB_Attribute_Name := host.display_attribute_name;
Lots of patterns are available for reference here as well if you'd like to see examples from the community: https://communities.bmc.com/community/bmcdn/discovery/pages/patterns
You can also see examples of sync patterns in your appliance by going to Manage -> Knowledge -> BMC Discovery Operation -> CMDB Sync
Thanks Brian, this helps !