Get RTC source control file Path

Hi Naveen,

It seems that your goal is to go from a file in the sandbox to the URI of it so that you can read its contents in the web UI using API's so that the code doesn't break. Unfortunately, there is no API that will allow you to get the remote path of the versionable represented by a file in a sandbox. Also, the URI of the file in the web UI is not API and cannot be counted on being permanent between releases.

If your goal is stability then I recommend using the intended linking between DOORS and RTC, which is the OSLC linking between requirements and work items. Otherwise, if you are willing to support it yourself you can try using internals, but be aware that it is not supported. Also, you may need to fix the tool after every upgrade of client or server.

Provided that you are ok with the caveats and are willing to do some investigation you can try using an internal interface known as the IFilesystemRestClient. Check out the getExtendedAttributes(). It can be invoked from a plugin you install into the eclipse client or via a http REST call (provided you authenticate with magic keys). In either case that call will return a versionable ID. The versionable can then be located within a repository workspace or stream using Plain Java Client API. Retrieve an IConfiguration via the IWorkspaceManager and IWorkspaceConnection. From the configuration, you can call determineAncestorsInHistory() to get the path within the component.

For more details on the Plain Java Client API (not the IFilesystemRestClient, which is internal) check out this article:
https://jazz.net/library/article/1229

If you require API to do the linking from requirements to files within a stream then please raise an RFE in developer works. The development team will determine whether it fits into the 24 month planning window and will update the RFE with details about whether it will be planned for completion within 24 months or not.

Cheers,
Chris