Integrating : Open Services for Lifecycle Collaboration (OSLC) : Linking System Architect and non-IBM products : Configuring System Architect as a provider for non-IBM products
  
Configuring System Architect as a provider for non-IBM products
You can configure System Architect encyclopedias so that non-IBM products can link to diagrams, definitions, and other artifacts.
Note Complete this task only if you are configuring System Architect as provider for non-IBM products. For consumers on a Jazz Team Server, you can configure System Architect as a provider by making it a friend. In this scenario, the System Architect REST Server updates the ConsumerKeyConfig.xml file automatically.
1 Open the System Architect installation folder. By default, the folder is:
C:\Program Files\UNICOM Systems\System Architect Suite\System Architect
2 Locate and run SAOSLCProviderConfig.exe.
3 Configure the Consumer Keys used for access through OSLC linking. On the Consumer Keys tab, add, edit, or remove Consumer Key settings. Many IBM Rational products such as IBM Rational Team Concert and Rational Design Manager automatically create a Consumer Key when you create the Friend relationship. However, other products that support OSLC may require you to create a Consumer Key manually.
To add a Consumer Key, click ADD and complete these fields:
Consumer Name
Name to identify the server that uses this key.
Consumer Key
Any unique text.
Consumer Secret
Password text to authenticate with Consumer Key.
User
Optional. Enter the Jazz user ID. This field is required only for tools pulling data out of System Architectthrough TRS (LQE).
4 Click File > Save Configuration to save your data and exit the tool.
5 Click Tools > Start Service.
Result
System Architect repositories are available for other products to consume.
See also
Linking System Architect and non-IBM products
Configuring the REST Server using the Configuration tool