CA Clarity PPM Connector and Domain Manager Interaction › CA Clarity PPM Connector Mappings Overview › CA Clarity PPM Connector Example: Person CI Mapping

CA Clarity PPM Connector Example: Person CI Mapping

This example shows how to convert a CA Clarity PPM Resource object to a USM Person CI and back to a CA Clarity PPM Resource object. The Person CI mapping does the conversion. This mapping supports the get, create, and update operations.

The get operation consists of three calls:

• get_core. This call invokes the person_get_core XSL template, which performs an XOG read request on the resource object.
• get_userids. This call invokes the person_get_userids template. The template calls the CA Clarity PPM NSQL query catalyst_get_internal_user_ids to retrieve the internal user IDs that are used to track the objects.
• map_persons. This call invokes the person_map template, which combines the data from get_core and get_userids into a single set of key or value pairs. The map template produces the key value pairs. These maps are then fed to the policy engine to create the final USM CIs.

The update and create operations invoke the same XSL template, person_write. Because the XOG request document is the same for create and update, only the generated parameters are different.

Note: The XOG requests for outbound (get) operations can contain results for multiple CA Clarity PPM objects. However, inbound (create, update, delete) operations can only handle one object at a time. Updating or deleting multiple CA Clarity PPM objects requires multiple connector calls.