Both GUI and command-line clients of Collaborator integrate with PTC Integrity:

The GUI Client can find and upload changes by pending or committed PTC Change Packages, by specific file version number, or by modified working files in local sandboxes.

The Command-Line Client can find and upload changes by pending or committed PTC Change Packages, or by modified working files in local sandboxes.

Supported PTC Integrity Versions

Collaborator uses Java client API that communicates with the PTC client (PTC Source) installed on your system. Collaborator supports the client versions starting from MKS Source 2007 and later (MKS Source and MKS Integrity are former names of PTC Source and PTC Integrity). MKS 2006 clients with the latest fix packs are also supported.

Since Collaborator works with a client applications that is installed on your computer, it supports all the protocols, authentication types, proxies, and other configuration options that you are using.

Windows Installation

On Windows operating systems, Collaborator's integration modules require 32-bit Java Runtime Environment. 64-bit JRE is not supported at the moment.

Linux Installation

To integrate with PTC Source on Linux, Collaborator's Java client API requires the following environment variables to be set:

export PATH=[integrity-client-install-dir]/bin:$PATH

export LD_LIBRARY_PATH=[integrity-client-install-dir]/lib/linux:$LD_LIBRARY_PATH

Notes

If your PTC projects use variant sub-projects, then you may need to set the -Dcom.smartbear.ptc.forceprojectpath=true VM option on Collaborator clients to make the integration use project path instead of configpath.

Technical Details and Limitations

Collaborator does not guarantee that Diff Viewer will display correct comparison results for the following cases: