OSLC DXL services for Rational DOORS 9.4

The DOORS® implementation of the OSLC Requirements Management (RM) specification version 2 includes a service that enables you to execute DOORS DXL scripts using HTTP protocol.

One of the primary strategies of the Rational® division is to improve the integration of Rational and non-Rational tools. The technology for this strategy is based on Open Services for Lifecycle Collaboration (OSLC).

Because the OSLC service discovery is extensible, it is possible for Rational and third party developers to add services which are not currently available in the implemented standard or which are considered too specialized for inclusion in the standard, and therefore not planned for future versions of the standard.

To support the ongoing Rational DOORS commitment to extensibility, version 9.4 introduces the concept of OSLC DXL Services to help bridge these gaps. The OSLC RM V2 interface exposes a service that enables users to execute DOORS DXL scripts across HTTP. This service is based on the concept of a DXL script library:
  1. The user looks up the required OSLC DXL script.
  2. The user calls this script to package the required parameters in the OSLC call.
  3. The script is run on an Interop Server.
  4. The results are posted back.

The scripts that are made available are completely under the control and customization of the Rational DOORS administrator, who can decide which DXL scripts are exposed across the service interface. The administrator can lock out the ability to call certain functions that could be regarded as a potential security risk, such as "runDXL".

Note that certain DXL, such as user interface widgets, will never be supported.

Because service discovery is protected by OAuth, users of this functionality are also required to first authenticate using their user name and password.

The typical steps for using this feature are:
  1. Create a DXL script.
  2. Install this DXL script as a service.
  3. Locate this service via service discovery.
  4. Call the service.
  5. Extract the return value from the response.

Feedback