← Back to EBS Deep Mode

# EBS Live Status — How Each Card Is Sourced

Each service card in the Monitor tab probes a different signal source. Understanding the source tells you what a status means — and what it cannot tell you.

DB only — Oracle metadata query; valid even when app tier is down
TCP probe — TCP port reachability to the EBS host
DB + TCP — DB metadata cross-checked with TCP probe (composite signal)
Shell (Phase 3) — Requires SSH execution; not yet implemented

Card | Source | What it detects | Phase 3 upgrade path
--- | --- | --- | ---
OPMN Legacy Oracle AS / Forms 10g/11g process manager. Not present on EBS 12.2+ WebLogic stacks — shows N/A if port 6200 is closed. | TCP probe | TCP reachability on port 6200. Absent on 12.2+ = not_applicable, not DOWN. | No upgrade planned — `opmnctl status` is only relevant on legacy stacks.
NodeManager WebLogic 12c Node Manager daemon. Distinct from OPMN — different port (5556), different binary, different lifecycle. | TCP probe | TCP reachability on port 5556. UP = NM is accepting connections. | Phase 3: parse `nodemanager.log` last heartbeat timestamp via SSH.
WebLogic Admin Server WLS Admin Server hosts the WebLogic console and coordinates managed servers. We do not shell out to `adadminsrvctl.sh` — it requires APPS + WLS passwords which we have no vault for yet. | DB + TCP | DB: `fnd_oam_managed_types` target_status. TCP: probe admin port (default 7001 or `s_wls_adminport` profile). Composite: both UP = running; either down = DOWN. | Phase 3: `adadminsrvctl.sh status` once secrets vault ships for APPS+WLS password storage.
Apps Listener Oracle TNS Listener for EBS application tier. Port read from `fnd_oam_metval.APPS_JDBC_URL`. | DB only | Listener port presence in APPS metadata. Does not TCP-probe the listener directly. | Phase 3: TCP probe on the extracted port to confirm listener is actually accepting connections.
Apache (OHS) Oracle HTTP Server — the web front-end for EBS self-service pages. | DB only | `fnd_svc_components` component_status for HTTP-type component. | Phase 3: `adapcctl.sh status` via SSH.
OACore OA Framework managed server — required for all OAF-based self-service pages. | DB only | `fnd_svc_components` component_status for oacore-type component. | Phase 3: `admanagedsrvctl.sh status oacore_server1` via SSH.
Forms Oracle Forms managed server — required for all Forms-based EBS screens. | DB only | `fnd_svc_components` component_status for forms-type component. | Phase 3: `admanagedsrvctl.sh status forms_server1` via SSH.
OAFM OA Framework Mobile managed server. | DB only | `fnd_svc_components` component_status for oafm-type component. | Phase 3: `admanagedsrvctl.sh status oafm_server1` via SSH.
Concurrent Managers Internal Concurrent Manager (FNDICM) + running/target process counts. Background job processing for EBS. | DB only | `fnd_concurrent_queues_vl` running_processes, target_processes. Pending + 24h error counts from `fnd_concurrent_requests`. | N/A — CM status is authoritative in the DB.
Workflow Mailer EBS only WF Notification Mailer — only shown on EBS-detected connections. DB-resident service; valid even when app tier is down. | DB only | `fnd_svc_components` for WF_MAILER% type. Stuck/error counts from `wf_notifications` and `wf_error`. | N/A — WF Mailer status is authoritative in the DB.
OPP EBS only Output Post Processor — only shown on EBS-detected connections. Handles concurrent request output delivery. | DB only | `fnd_svc_components` for Output Post Processor. Queue depth from `fnd_concurrent_requests` FNDCPOPP. | N/A — OPP status is authoritative in the DB.

## Frequently Asked Questions

Why does OPMN show N/A on my EBS 12.2 instance?
OPMN (`opmnctl`) is the Oracle AS process manager used in EBS 11i and 12.0/12.1 app tiers. EBS 12.2 moved to a WebLogic 12c application tier — OPMN is not installed. If port 6200 is not reachable, TuneVault reports not_applicable rather than DOWN, since absence is expected on 12.2+ stacks.
Why doesn't TuneVault run `adadminsrvctl.sh status` for WebLogic Admin Server?
`adadminsrvctl.sh status` requires both the APPS schema password and the WebLogic admin password passed as arguments. TuneVault does not store those credentials — and shipping password-in-argument SSH calls without a secrets vault is a security regression we've explicitly blocked. Until Phase 3 ships with proper secrets management, the WLS Admin card uses a composite DB metadata + TCP probe instead. The card tooltip says exactly this.
What does "DB only" mean for Apache / managed servers?
TuneVault reads `fnd_svc_components` for the component's registered status in the Oracle DB. This is usually accurate — EBS updates this table when services start/stop through the admin console. However, it cannot detect cases where the process crashed without updating the DB record. Phase 3 SSH commands will give a ground-truth shell-level status.
Why are Workflow Mailer and OPP only shown on EBS connections?
These services only exist in Oracle E-Business Suite — they're meaningless on a plain Oracle DB connection. When TuneVault detects no EBS tier (via the APPS.DUAL probe during health check), these cards are hidden entirely to avoid confusion.
What is Phase 3?
Phase 3 is the planned SSH execution layer. Commands will be routed through the TuneVault proxy agent already installed on your EBS server, with a secrets vault for storing APPS/WLS passwords encrypted. Phase 3 upgrades several "DB only" cards to shell-verified status checks. The Control tab already shows the Phase 3 command whitelist in dry-run mode.