Integrating data by using the OSLC REST API

Your product applications and some external applications can link and share data by using Open Services for Lifecycle Collaboration (OSLC) integration. OSLC specifications define how lifecycle applications represent, link to, and access resources based on established internet and linked-data standards including representational state transfer (REST) API architecture, resource description framework (RDF) specifications, and hyper-text transfer protocol (HTTP) methods. OSLC makes it easier for tools to work together and share data. By following the rules and methods that are defined by the specifications, applications can perform create, request, update, delete operations on the resources of another application.

The OSLC community is a group of software developers and organizations who are working to standardize how software lifecycle tools share data such as requirements, defects, test cases, and change history. Version 2.0 of the OSLC specification is supported for OSLC integration of applications. The specifications and other OSLC resources are available on the web.

IBM® TRIRIGA® provides an OSLC REST API as part of the on-premises IBM TRIRIGA Connector for Business Applications (CBA) license and the IBM Facilities and Real Estate Management on Cloud (TRIRIGA) Enterprise User license.

OSLC integration with IBM TRIRIGA is accomplished between a consumer application and TRIRIGA, the provider application. As the OSLC provider application, TRIRIGA makes its resource data available to the consumer application through containers, which are known as service providers. With the resource data made available, the consumer application can create links between its data and the resource data of TRIRIGA. You can configure and enable any part of TRIRIGA to act as an OSLC provider application.

Consumer applications can find the URIs that identify the resources in the provider application and use those URIs to request query results, for example. For IBM TRIRIGA, service providers are available at http://yourserver/oslc/sp.

The URIs used in OSLC requests must be URL encoded.