Page Comparison

AssetTrack's Out-of-Box Integration with CA APM and Service Desk

AssetTrack integrates with CA APM and Service Desk out-of-the-box. Native fields in AssetTrack are mapped to corresponding default fields in CA APM. This mapping works for most customers. For extended fields created by APM administrators, you can simply create corresponding custom fields in AssetTrack with the same name.

If this out-of-box configuration works for you, which it does for most customers, you don't need to customize field mappings using dynamic field mapping.

What is dynamic field mapping (DFP)?

Some customers have heavily customized CA APM and must change the out-of-box mappings. The out-of-the-box mappings are static mappings, meaning they're hardcoded and cannot be edited at runtime*. The asset tag fields maps the to the AltAssetID field, etc.

 "Field mapping" means "Which AssetTrack fields connect to which repository fields?" For example, here are a handful of well-known out-of-the-box field mappings:

DFP allows us to create mappings that don't come out-of-the-box. For example, if you create a 'Foo' extended field in APM, and we'd like to collect data into this field, you will need to create or designate a field in AssetTrack for that, then map the AT field to the 'Foo' extended field.

*In AssetTrack Settings, for certain fields, you can edit the mapping for some fields.

Modifying ATConfig files

ATConfig files contain all configuration information for a given instance of AssetTrack. You can export your configuration by selecting Transfer Config > Export Configuration from the AssetTrack web interface. You must have Administrator privileges to do this.

There is currently no user interface to do create/manage mappings. It must all be done by defining mappings in ATConfig files, then importing those ATConfig files into AssetTrack.

Supported repository products

• CA APM 11
• CA APM 12
• CA Service Desk

You can map any combination of field types (e.g. native-to-native, native-to-extended, custom-to-native, etc).

*We don't support writing to any APM 12 extended fields, so for that repository, you can't map to any extended field.