A Collaboration Link is a link between two elements that belong to different applications. Typically, when a Collaboration Link is created from one Application A to one Application B, a back link is created (automatically) from Application B to Application A, so both elements may have a way to navigate to each other. In this scenario, where a link can exist either because it was created on its own, or because it was created as the back link of the other link, it is often useful to distinguish their nature with a role name:
Outgoing link: is the Collaboration Link that was created on its own.
Incoming link: is the Collaboration Link that was created as the back link of the other link.
Henceforth, when a Collaboration Link in Windchill is said to be an outgoing link, it means it is a link whose creation was triggered from Windchill (creating a back link on the CLM Application), whereas if it is an incoming link it means it is a link that was created as back link on Windchill (due to a creation triggered from the CLM Application).
Creating Collaboration Links is speaking about trust between different applications. The triggering application of the Collaboration Link creation must access to the resources (artifacts) of the other application, and this one must allow the modification of them in order to create the link. All this must happen in an atmosphere of trust: applications must be registered in each other to allow this behavior only between registered applications. Now, the application allowing the access/modification of its resources is called the friend application, whereas the one requesting such access/modification is called the consumer application.
In this scenario, if Windchill wanted to access/modify the resources of DOORS Next Generation (DNG), for example, DNG would need to be registered in Windchill as a friend, and at the same time, Windchill would need to be registered in DNG as a consumer... All this would be good enough if only Windchill required to create Collaboration Links, but what about if DNG users also wanted to create links from their side? In this case, and to allow bidirectional creation of links, Windchill would need to be registered also as a friend in DNG, and at the same time, DNG would need to be registered as a consumer in Windchill.
There are normally two ways to establish this connectivity:
As you can see, everything is about a key and a password, the difference between last approaches is how they generate and share the key. Getting back to the Windchill-DNG example, you will need to:
This would be a good moment to get in touch with the CLM Application administrator and agree on which method you both will use, keep in mind that whereas OSLC Connect for Windchill supports one the method of making friends with an existing key, most CLM Applications just support the method of requesting provisional keys. But wait a moment, which CLM Applications need become friends of Windchill? And how is a friend or consumer registered on Windchill?
Following is what you need to do to complete this configuration:
If Global configurations are used, you need also to:
If Jazz Reporting Service and/or RELM are required, you need also to:
CLM LDXconsumer credentials .