Previous Topic: CA Clarity PPM Connector Mappings OverviewNext Topic: CA Clarity PPM Connector Example: Person CI Mapping


CA Clarity PPM Connector Mapping Configuration Files

The CA Clarity PPM connector mapping configuration files list all supported USM entities, their transformation scripts, and alerts for all USM CIs.

You can create and modify the following CA Clarity PPM connector mapping configuration files:

clarity_templates.xml

The clarity_templates.xml mapping configuration file contains the scripts that are used to drive the XOG input/output and transformation to key/value pairs. The scripts are Extensible Stylesheet Language Family Transformations (XSLT). The type attribute denotes the templates. The following types of templates are included:

While the templates are tied to specific CA Clarity PPM objects, you can include them in any number of object mappings.

Example: The person_get_userids template retrieves CA Clarity PPM user IDs. Use this template in the CA Clarity PPM Resource object to USM Person CI object mapping. And also in the Project object to CI mapping to determine project owners.

clarity_alerts.xml

The clarity_alerts.xml mapping configuration file specifies the alerts that the CA Clarity PPM connector supports.

See the "Alerts" section for more information.

clarity_policy.xml and clarity_policySB.xml

The clarity_policy.xml and clarity_policySB.xml mapping configuration files contain the policy definitions that are run against the maps produced by XOG requests. Inbound policies (create, update, delete operations) are defined in the clarity_policySB.xml file. These policies reverse some of the normalization and formatting policies defined in the clarity_policy.xml file so that they are usable in XOG requests.

See the CA Spectrum SA Administration Guide for details on the connector policy language.

clarity_mappings.xml

The clarity_mappings.xml mapping configuration file defines the workflow required to transform a CA Clarity PPM object to a USM CI and back to a CA Clarity PPM object. This mapping configuration file specifies the CIs and operations that are supported. Each operation consists of an ordered set of calls to one or more templates defined in the clarity_templates.xml file. A minimal outbound (get) operation requires two template calls. This first one retrieves the data using XOG, and the second converts the data to key/value pairs. A minimal inbound operation (create, update, delete) requires one template call as it is not necessary to map the XOG request results to key/value pairs.