Configuring the Digital Product Traceability(DPT) Extension in ThingWorx

A ThingWorx installation with ThingWorx Flow is required to configure the integration of Windchill with Integrity Lifecycle Manager.

• ThingWorx is enabled to import the Windchill extension. To know more about how to enable the setting, see Importing Extensions in the ThingWorx Help Center.

• ThingWorx is configured to allow Cross-Origin requests. To know more about the Cross-Origin Resource Sharing (CORS) setting, see Making a REST Call from an External Website to ThingWorx Flow in the ThingWorx Help Center.

• You have permissions required to perform actions in ThingWorx. To know more about permissions, see the section Permissions for ThingWorx Entities. For more information about the user profiles and organizations in ThingWorx, see the topics Organizations and Securing the Applications Built on the ThingWorx Platform Using Visibility and Permissions in the ThingWorx Help Center.

• Windchill is added to secured domains in Windchill RV&S OSLC Server to access the delegated interface from Windchill. For more information about how to add domains as secured, see the Windchill RV&S OSLC Server document on Reference Documents.

• You have downloaded the Windchill_Digital_Product_Traceability-extension zip from the PTC Software Download page on PTC.com. The zip is available under the Windchill PDMLink product family.

If you get certificate error in the browser, use Standard SSL certificates that are issued and verified by a trusted Certificate Authority (CA). If you have self-signed certificates, import the self-signed certificate as trusted certificate in your browser.

Windchill DPT does not support ThingWorx configured with Windchill authentication. For more information, see the article Support for ThingWorx Platform which implements Windchill PDMLink Authentication with Digital Product Traceability (DPT) on PTC.com.

Following permissions are required for the ThingWorx user profiles, who use the Traces functionality:

Thing Template	Runtime	Visibility
OslcDataServicesThingTemplate	Service Execute: Yes to instances	Yes to instances
OslcMappingConfigThingTemplate	NA	Yes to instances and itself
OslcFlowTemplate	Service Execute: Yes to instances	Yes to instances

Following permissions are required for the ThingWorx user profiles who configure the integration:

Thing or Thing Template	Runtime	Design	Visibility
OslcDataServicesThingTemplate	Service Execute: Yes to instances	NA	Yes to instances
OslcMappingConfigThingTemplate	NA	Read: Yes to instances	Yes to instances and itself
OslcFlowTemplate	Service Execute: Yes to instances	NA	Yes to instances
Collection:Things	NA	Create: Yes Read: Yes	NA

1. In the ThingWorx platform, from Composer, import the extension Windchill_Digital_Product_Traceability-extension. See Importing Extensions topic in the ThingWorx Help center.

◦ OslcDataServicesThing — This Thing contains the services that are invoked from Windchill.

◦ OslcFlowsThing — This Thing contains the flow services that are used to fetch data from the remote system.

◦ OslcMappingConfigThing — This Thing contains the configuration tables.

◦ DPTIntegrityOslcConfigThing — This Thing contains example configuration for remote OSLC system.

◦ PTC.PLM.TraceLinks.OslcDataServicesThingTemplate — This template has services defined for Windchill.

◦ PTC.PLM.TraceLinks.OslcFlowsTemplate — This template contains the flow services.

◦ PTC.PLM.TraceLinks.OslcMappingConfigThingTemplate — Use this ThingTemplate to create configuration Thing for each remote system.

◦ PTC.PLM.TraceLinks.OslcDataServicesThingShape — This ThingShape contains the service contract definition for Windchill.

Ensure correct permissions are enabled on the above listed entities. See the section Permissions for ThingWorx Entities in this page.

3. Create a new Connection for the OSLC system to which integration is required. See the topic Creating and Managing Connections in ThingWorx Help center.

▪ Integrity Lifecycle Manager OSLC system Catalog URL— Refer to the Integrity Lifecycle Manager OSLC Client guide on Reference Documents.

▪ Login credentials to the Integrity Lifecycle Manager service account to access the OSLC server.

▪ Concurrent Requests — The number of simultaneous resource requests invoked from ThingWorx Flow. The default value is 5.

You can enter any value, as required. The value should be based on the server that you are trying to reach.

a. Create a configuration Thing using template PTC.PLM.TraceLinks.OslcMappingConfigThingTemplate.

b. Configure the mappings as explained in the following tables. You can refer to the DPTIntegrityOslcConfigThing as example and enter the details for OSLC system.

Server Name	Name of the Integrity Lifecycle Manager OSLC server.
BaseURL	Base URL of the Integrity Lifecycle Manager OSLC server.
Connection Object	Name of the Connection created for the Integrity Lifecycle Manager OSLC server.

Windchill Type	Internal name of the Requirement Resource from Type Management in Windchill. The trace link is created to this Resource.
OSLC ResourceType	Name of the Requirement Resource in Integrity Lifecycle Manager OSLC server. This can be a user-defined name.

For information about the internal name of Requirement Resource, see Types and Attributes in System Compatibility and Requirements.

Windchill TableId	Table ID in Windchill where the data from Integrity Lifecycle Manager OSLC server is displayed.
Windchill Type	Internal name of the Requirement Resource from Type Management in Windchill.

You can configure the tables such as Change Management table to display the remote columns Name, Number and Identity. For more information, see Creating and Editing New Table Views.

Windchill Attribute	Name of the Windchill attribute to be displayed in the Windchill table.
OSLCResourceAttribute	Name of the OSLC resource attribute.
WindchillAttributeDataType	Data type of the Windchill attribute.
IsPreview	If preview information is required from Integrity Lifecycle Manager OSLC system for the Windchill attribute.

To find out the Table ID and column names for mapping as explained above, enable the JCA Debug feature. To know more about JCA Debug and how to enable it, see the topics Debugging and What information does jcaDebug display?.

c. Enter the Connection Label of the connection created in the above step as the connection name.