Integrations (PTC products, 3rd party products and code) > Managing product traceability when working with external systems > OSLC Integrations > Overview of OSLC > Configuring Modeler OSLC consumer capabilities
  
Configuring Modeler OSLC consumer capabilities
Configuring link types
The link types that are available when creating OSLC Links can be configured. In the C:\ProgramData\PTC Integrity Modeler\ModelerATFiles directory, a file called TraceLinks.xml defines the link types available for that Modeler Server.
The file contains mappings between Modeler types (e.g. Requirement, RequirementDiagram) and OSLC resource categories (e.g. Architecture, Requirement, Product) and specifies the available link types (candidates) for each mapping. Configuration points:
Candidate trace links can be added, removed or renamed for existing mappings.
Additional type specific mapping can be added. For example, it is possible to specify the links that are available when linking a Modeler Use Case and an OSLC Requirement resource. An example of this type of custom mapping is shown below.
When defining the Modeler type within a mapping, use the <stereotypeoption> tag if the type is a stereotype, otherwise use the <metatypeoption> tag.
* 
If no mapping exists for a given Modeler type, a set of default mappings and link types is used. These are defined within the <default> tag.