alexz/arena-plm-fiori
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ADR-004: back out of on-stack RAP; retarget to starter customizing tenant

Browse Source 
Both tenants belong to the same starter system: my429480 is its
customizing tenant (client 100, key-user extensibility only, no ABAP)
and my431353 is its development tenant (client 080). This package had
recorded my429480 as "productive" and ADR-002 had assumed it offered
developer extensibility; both were wrong.

- ADR-004 withdraws the on-stack RAP route and moves the application to
  a side-by-side runtime against released OData APIs. ADR-002 marked
  superseded.
- Development tenant my431353 parked: all 19 ZARENA_PLM objects left
  active, sources kept in docs/handover/rap/ as reference, so the route
  stays reversible.
- Replacement host left open as OQ-11 (key-user extensibility vs CAP
  side-by-side); recommendation recorded as CAP. No build starts until
  OQ-11 is closed.
- RAP-dependent items V-2, V-3, OQ-5, OQ-8, OQ-9, OQ-10 parked rather
  than closed.
- Tenant references corrected across CLAUDE.md, KNOWLEDGE.md,
  app/README.md, the RAP handover README, the rap-developer agent and
  the reentrance-login helper README.

No SAP tenant was modified.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
alexz
2026-09-29 10:33:29 -07:00
co-authored by Claude Opus 5
parent 468729eb4e
commit ffd33f4ec0
10 changed files with 332 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/adt-reentrance-login/README.md
+16 -2
View File
@@ -6,6 +6,15 @@ headless / SSH-only host — without a browser window on the server's desktop.
Node 24, standard library only, no dependencies, no install step.
> **Parked 2026-09-29.** `my431353` is the starter system's **development**
> tenant (client 080). I parked that tenant on 2026-09-29 together with the
> on-stack RAP route, leaving all of its objects active in place. I keep this
> helper only in case that route is revived — nothing in the current
> side-by-side architecture calls it. Every `my431353` reference below is the
> default this tool was built against, not a live target. The working target
> is the starter system's customizing tenant `my429480` (client 100), which
> supports key-user extensibility only and needs no ADT logon at all.
---
## Why this exists
@@ -37,7 +46,9 @@ on this host. This script is that listener.
## Run it
Three steps, three terminals-worth of context. Values below use the defaults
(tenant `my431353`, port `42010`, 300 s timeout).
(tenant `my431353`, port `42010`, 300 s timeout) — that tenant being the
development tenant parked on 2026-09-29, kept here as the default this tool
shipped with.
### 1. Start the helper on this host
@@ -69,6 +80,9 @@ redirects your browser to its own machine and nothing is captured.
https://my431353.s4hana.cloud.sap/sap/bc/adt/core/http/reentranceticket?redirect-url=http://localhost:42010/adt/redirect
```
That host is the parked development tenant (client 080, parked 2026-09-29);
point `--tenant` elsewhere if the revived route ever lands on another tenant.
(Or capture it programmatically: `node login.mjs --print-url-only`.)
After SSO the tab lands on "Ticket captured", the helper writes
@@ -88,7 +102,7 @@ fresh ticket, call the MCP `login` tool for the destination.
| Flag | Default | Meaning |
|---|---|---|
| `--tenant <url>` | `https://my431353.s4hana.cloud.sap` | Tenant base URL. The UI host, not the `-api` host. |
| `--tenant <url>` | `https://my431353.s4hana.cloud.sap` | Tenant base URL. The UI host, not the `-api` host. The default is the development tenant parked on 2026-09-29. |
| `--port <n>` | `42010` | Loopback port. Bound to `127.0.0.1` **only**; there is no flag to change the bind address. |
| `--timeout <seconds>` | `300` | Give up and write nothing. |
| `--out <path>` | `~/.abap-adt-mcp/ticket.json` | Output file, mode 0600 (directory created 0700). |