Troubleshooting OSLC
These topics contain information about issues that can
occur when you use OSLC to integrate with remote applications.
- OSLC implementation details
IBM Engineering Requirements Management DOORS - Web Access (DWA) provides the following OSLC interfaces: OSLC RM v1 and OSLC RM v2. - DWA OSLC URLs
The rootservices URL at /dwa/public/rootservices is the only static URL that IBM Engineering Requirements Management DOORS - Web Access (DWA) publishes. All other URLs are dynamically derived from this URL using the standard OSLC RM v1 and OSLC RM v2 specifications, and are subject to change. - Invalid DOORS configuration
The IBM Engineering Requirements Management DOORS (DOORS) client must be started with the dbadmin command and the –dwaHost, –dwaProtocol, and –dwaPort parameters for the OSLC RM v1 or OSLC RM v2 functionality to work. It is also needed for internal and external link rendering to work. - Making programmatic requests using OSLC RM V1 or OSLC RM V2
All OSLC RM V1 and OSLC RM V2 programmatic requests are protected through OAuth 1.0a, and all user interface requests use the standard IBM Engineering Requirements Management DOORS - Web Access (DWA) username / password security framework. - Accessing protected resources
All OSLC RM v1 and OSLC RM v2 programmatic requests are protected through OAuth 1.0a, and all user interface requests use the standard IBM Engineering Requirements Management DOORS - Web Access (DWA) username/password security framework. - DWA and link rendering
This topic contains useful information about setting up the festival.xml file for link rendering. - Link rendering failures
IBM Engineering Requirements Management DOORS - Web Access (DWA) supports the application/x-oslc-compact+xml accept mime type for OSLC RM v2 and application/x-jazz-compact-rendering accept mime type for OSLC RM v1. - SSL not configured
When you connect to IBM Engineering Requirements Management DOORS - Web Access (DWA) using SSL, and a browser server not found message is displayed, connect without using SSL to confirm that DWA is running. If the non-SSL connection works, it usually indicates that the Tomcat server.xml file has not been configured for SSL support.
Feedback