sap-nw-java-pilisted

SAP NetWeaver AS Java and PI/PO operations — NWA, the J2EE sapcontrol functions, jcmon and the telnet admin shell on 5<nr>08 as out-of-band channels, the AS Java log set (defaultTrace, std_server*.out, dev_jcontrol), and on PI: PIMON, message monitoring, the EOIO stuck-message decision tree, CPA cache and adapter traces. Explains why JCo is the WRONG tool for AS Java and what the real programmatic surfaces are (SOAP web services, monitor servlets, sapcontrol SOAP, JMX/P4, telnet). Use for "AS Java", "NWA", "PIMON", "PI message stuck", "To be delivered", "EOIO HOLD", "CPA cache refresh", "ESR", "Integration Directory", "defaultTrace", "server0", "adapter trace".
adam0thman/sap-basis-ops · ★ 0 · DevOps & Infrastructure · score 72

Install: claude install-skill adam0thman/sap-basis-ops

# SAP NetWeaver AS Java & PI/PO operations **Sources.** **SAP Note 1514898 — *Troubleshooting SAP Process Orchestration / Integration***, version **112**, released **17.08.2026**, component BC-XI-CON-AFW **[V]** — fetched and read. URL surface, auth behaviour and monitor content **live-verified 2026-08-31 against a real PI 7.50 AS Java system** — marked **[LV]**. **[G]** = cited but not re-read in full. > ## The boundary that decides what can be automated > > AS Java splits into two very different surfaces: > > | Surface | Technology | Automatable? | > |---|---|---| > | **NWA, PIMON, monitor servlets, SLD, MDT** | HTTP / WebDynpro / JSP | ✅ Browser or `curl` | > | **ESR, Integration Directory, Config Tool, Visual Admin** | **Java Web Start / Swing** | 🚫 **No** — the browser only serves the `.jnlp` launcher; a local Java runtime runs the app | > > `/rep/start/index.jsp` and `/dir/start/index.jsp` returning HTTP 200 **[LV]** proves only that the > *launch pages* exist — the **UIs** cannot be driven by a browser or headlessly. > > **But the UI is not the only door.** Integration Directory *content* has a **SOAP API** — > `CommunicationChannelInService` exposes `Create`/`Read`/`Change`/`Delete`/`Query`/`OpenForEdit`/ > `Revert`, verified live **[LV]** (§2a). So "channel configuration is a desktop task" is **wrong for > the objects, right for the tool**. Mapping design and repository browsing remain human work; > channel and configuration objects are scriptable. --- ## 1. The