Integration definition file

Every integration of an external tool that is done using the MBSE Integration Services must have an integration definition file. Configuration of the integration definition file is mandatory for the following SOAs:

• exportCollection()
• importCollection()
• updateCollection()

The integration definition file provides a way to configure mapping of tool artifacts and its metadata to Teamcenter business objects and properties. This integration definition file is one per tool. It is stored in a dataset with name APPLICATION_NAME_BHM_INT_DEF_FILE, where APPLICATION_NAME is a unique identifier name for a tool that is being integrated. The dataset must have administrative control.

This topic's full content (definitions of unique application name, connector class, containers, components, attribute mapping, stereotypes, file mappings, standard folders, and extension points) is identical to the "Integration definition file" topic in the companion "MBSE Integration Services ─ Deployment" book — see mbse/integration-services-deployment/integration-definition-file.md for the complete reference including all XML examples.

Where this topic is used from here

• Classify objects and attributes between your modeling tool and Teamcenter using the integration definition file
• Understanding how objects and attributes are inherited in the integration definition file
• Overview of Integration Mapping Editor