These topics contain information about issues that can
occur when you use OSLC to integrate with remote applications.
OSLC implementation details
Rational DOORS Web Access provides the
following OSLC interfaces: OSLC RM v1 and OSLC RM v2.
Rational DOORS Web Access OSLC URLs
The rootservices URL at /dwa/public/rootservices is
the only static URL that Rational DOORS Web Access publishes. All
other URLs are dynamically derived from this URL using the standard
OSLC v1 and CALM 2009 specifications, and are subject to change.
Invalid Rational DOORS configuration
The Rational 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 Rational DOORS Web Access 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 Rational DOORS Web Access username/password security framework.
Link rendering failures
Rational DOORS Web Access supports the application/x-jazz-compact-rendering
accept mime type, and all link rendering level 1 requests
should use this accept mime type. Rational DOORS Web
Access does not support the application/x-oslc-compact+xml mime
type defined in OSLC v2.
SSL not configured
When you connect to Rational DOORS Web Access using SSL, and
a browser server not found message is displayed, connect
without using SSL to confirm that Rational DOORS Web Access is running. If
the non-SSL connection works, it usually indicates that the Tomcat server.xml file
has not been configured for SSL support.