IBM DOORS / DOORS Next integration

Topology

Version & protocol support

Feature matrix

Prerequisites

DOORS Next

1. Rational server root (often /rm)
2. JTS base URL (/jts)
3. Service credential or OAuth Consumer with RM scope
4. Target Project Area name

DOORS 9 classic

1. DOORS Web Access URL + TCP port — or
2. Periodic ReqIF handoffs for offline ingestion
3. Admin assistance unlocking DWA/REST gateways

Configuration (DOORS Next)

Create credential record

Console → Integrations → ALM → Add:

• oauth2 (preferred) or basic
• Base URL https://dng.customer.com/rm
• Jazz https://dng.customer.com/jts
• Project Area slug from /oslc_rm/catalog
• Registered Consumer keys

Bind agents

skills:
  - name: alm-integration
    config:
      adapter: doors_next
      credential_id: <credential_id>
      default_project: "ABZ_Platform"

Smoke test

combo-cli integration test --credential <credential_id>
# expect Discovery OK: folders/modules enumerated

Initial KB ingestion

combo-cli import requirements \
  --credential <credential_id> \
  --module "ABZ/Requirements/Functional" \
  --kb <kb_id>

Agents can likewise accept natural-language commands (“Sync Functional module into this session’s KB …”).

DOORS 9 ReqIF pathway

Many customers block DWA. Workflow:

1. Export .reqifz bundles from DOORS 9 GUI
2. Console → Integrations → ALM → ReqIF ingestion
3. Platform unpacks artefacts + linkage graph into KB

Day‑2 workflows

Common pitfalls

References

• Automotive AI requirements overview
• ALM solution brief
• Skill catalogue entry: alm-integration