Mapping from one relationship semantic to another should be fairly straightforward in the connector policy.
The challenge is in dealing with service specific custom/operative propagation policies, as the connector (or CMDB for that matter) has no concept of these propagation types and therefore cannot expose them.
BUT... if the default policies are suitable, or if you've predefined a service-specific policy, a simple mapping in the connector policy from XXXXX --> isAffectedBy (for example) should do the trick.
Here is the relevant section of ServiceDeskManager_policy.xml:
<EventClass name="BinaryRelationship" extends="CMDB_BinaryRelationship">
<Normalize>
<Field output="Semantic" type="map" input="ci_rel_type" >
<mapentry mapin="^HasImpactOn$" mapout="IsImpactedBy"/>
<mapentry mapin="^requires$|^is required by$" mapout="HasRequirementFor" />
<mapentry mapin="^connects to$" mapout="IsBoundTo" />
....
Change the bottom "mapentry" to:
<mapentry mapin="^connects to$" mapout="IsAffectedBy" />
You will need to recycle the connector.
Jeff Vaught
Sr Architect, SOI team
CA Technologies