This is located on the same pattern name but the syncmapping syntax has been simplified:
Source := hosting_ci,
Destination := softwareserver,
Impacted := softwareserver,
Name := "APPLICATIONSYSTEMCOMPUTER"
Impacted word basically summarizes what HasImpact and ImpactDirection were saying and sets them under the cover.
Thanks for the info. How would one go about overriding this in Discovery? We have a need to alter this between host and si. Much rather do it in ADDM versus CMDB. Thanks,
What do you want to alter about it?
To alter the relationship behaviour of a standard mapping, you should make a copy of it and declare that it overrides the base one. Then you can change the logic however you want. Syncmapping block - BMC Discovery 11.0 - BMC Documentation
Hey Duncan, We would like to have the ability to set the HasImpact to "No" on most SI to Host dependency relationships. As an example in the old syncmapping I would build an override mapping and set that value to 10.
1 of 1 people found this helpful
In your override, you simply remove the Impacted := softwareserver part, then there won't be an impact set.
Out of interest, why don't you want an impact to most SoftwareServers?
The short answer is those software instances and all underlying software components really slow down and clog up the UI display in the BMC Change module when running impact analysis against servers that have been related to change requests. The company and change mgmt would like the focus of the impact analysis tool to be on any Applications and Business Services that the server unavailability would impact.