Integration with Other Applications > Digital Product Traceability > Windchill as an OSLC Client > System Compatibility and Requirements
System Compatibility and Requirements
The following are the system requirements to integrate Windchill with external systems such as PTC RV&S, PTC Modeler, Codebeamer, Siemens Polarion, or IBM Rational Doors NG:
• Windchill
• ThingWorx Platform with Flow, OSLC connector, and Cross-Origin Resource Sharing (CORS) setting
• External OSLC Server
* 
For information about software compatibility and platform support, open the View Matrix Page link for this release on the Release Calendar page.
Windchill Properties
By default, the following properties are available in the <windchill>\site.xconf file:
Property Name
Default Value
Description
com.ptc.twx.host
—
ThingWorx Flow server is the host.
Example: thingworx.ptc.com
* 
PTC recommends that ThingWorx and Windchill servers be on the same top-level domain. For example, https://windchill.ptcnet.ptc.com and https://thingworx.ptcnet.ptc.com have the top-level domain as ptc.com. If the top-level domains are different for ThingWorx and Windchill, behavior may vary across different browsers.
com.ptc.twx.port
443
TCP/IP port to which ThingWorx connects for direct server-to-server HTTP requests from Windchill.
com.ptc.twx.protocol
https
TCP protocol used by Windchill to connect to the ThingWorx host when ThingWorx is installed in standalone mode.
Specify the required values for these properties and use the xconfmanager utility to propagate the changes. For more information, see Using the xconfmanager Utility.
For example, if you set com.ptc.twx.host to thingworx.ptc.com, com.ptc.twx.port to 443, and com.ptc.twx.protocol to https, the URL created will be in the following format: https://thingworx.ptc.com:443/Thingworx/Composer
Ensure that the output URL is valid and accessible from your browser based on your system configuration.
Types and Attributes
In the Type and Attribute Management utility of Windchill, the following modeled types and soft types are available out-of-the-box:
Modeled Types
Soft Types
Instantiable
Subtypeable
Requirement External Resource
Requirement Collection
No
* 
All soft types of Requirement External Resource are instantiable.
Yes
Requirement
Architecture External Resource
Activity
No
* 
All soft types of Architecture External Resource are instantiable.
Yes
Block
Class
Class Diagram
Model
Package
Use Case
Use Case Diagram
Requirement Object to Object Trace Link
Satisfy
No
Yes
Requirement Version to Version Trace Link
Allocate
No
Yes
Architecture Object to Object Trace Link
Implement
No
Yes
Architecture Version to Version Trace Link
—
No
Yes
External Change Issue Types
External Defect
No
* 
All soft types of External Change Issue Types are instantiable.
—
External Enhancement
External Issue
External Variance
External Change Notice Types
External Change Notice
No
* 
All soft types of External Change Notice Types are instantiable.
—
External Change Request Types
External Change Request
No
* 
All soft types of External Change Request Types are instantiable.
—
External Change Review Types
—
No
—
* 
• In the Type and Attribute Management utility, you can create soft types for Requirement External Resource and Architecture External Resource modeled types as well as out-of-the-box supported trace link types.
• The relationship constraint for the soft types Satisfy, Allocate, and Implement for parts, options, choices, documents, resources, and standard control characteristic are available out-of-the-box.
◦ To support traceability for all out-of-the-box soft types, such as electrical parts, select the supported trace link type in the New Relationship Constraint window. For more information, see Creating a Relationship Constraint.
Isto foi útil?