Configuring Rational DOORS data for external applications
You can use the working set, attribute and link type mapping, and the reportable shape to configure IBM® Rational® DOORS® data for integration with external applications. These applications include Rational Engineering Lifecycle Management, Jazz® Reporting Service, and applications that are integrated with Rational DOORS by using OSLC.
About this task
The working set determines which Rational DOORS projects, folders, and modules are available for the following external applications:
- TRS provides data to consumer applications that use the Lifecycle Query Engine (LQE) to build an index to visualize, analyze, and organize engineering data. The data can be collected from many tools. Rational Engineering Lifecycle Management uses LQE to consume Rational DOORS data.
- The link discovery capability enables external applications that are integrated with Rational DOORS to discover OSLC links in Rational DOORS and make them visible in the external applications.
- Jazz Reporting Service uses data that is extracted from Rational DOORS by the Data Collection Component and imported into a report data warehouse.
The working set is helpful for focusing on relevant data during analysis and reporting. Rational DOORS repositories can contain massive amounts of data. The working set eliminates processing of irrelevant projects, folders, and modules so that you can efficiently capture accurate business analytics. In addition, when irrelevant information is eliminated, the system performance improves.
Attribute and link type mapping
You can use Uniform Resource Identifiers (URIs) to create a consistent OSLC representation for attributes and link types with the same name and type across all modules that are available for integration with external applications. Attributes and link types that are used in multiple modules have unique identifiers in those modules, even if they have the same name and type. External applications treat these attributes and links as different types. This treatment prevents consistent querying and reporting across modules. Attribute and link type mapping assigns a single URI to attributes and link types that have the same name and type but that are in different modules. This mapping provides a consistent OSLC representation that enables external applications to recognize equivalent attributes and links across modules.
- The attribute names and types must be the same in each module.
- A working set and reportable shape must be configured to make the modules, attributes, and link types available for integration with external applications.
You can use the reportable shape to specify which attributes and link types are available for reporting in Jazz Reporting Service.