Infrastructure (auto-generated)

Context: ESB

Name	Hostname	IP	Status	Role	OS	Location	Hosting	Hypervisor	CPUs	Memory	Disks	Stack	Tags
UN-API-R-CL-001.edc.un.org	NYVM2519	10.130.131.102	active	API server	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-R-CL-002.edc.un.org	NYVM2520	10.130.131.103	active	API server	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-R-DB-001.edc.un.org	NYVM2531	10.130.132.67	active	MySQL cluster node	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-R-DB-002.edc.un.org	NYVM2532	10.130.132.68	active	MySQL cluster node	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-R-DB-003.edc.un.org	NYVM2533	10.130.132.69	active	MySQL cluster node	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-R-GW-001.edc.un.org	NYVM2517	10.130.131.100	active	WSO2 API Gateway	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-R-GW-002.edc.un.org	NYVM2518	10.130.131.101	active	WSO2 API Gateway	RHEL 7.9	—	—	—	—	—	—	—	—

PROD

Name	Hostname	IP	Status	Role	OS	Location	Hosting	Hypervisor	CPUs	Memory	Disks	Stack	Tags
UN-API-P-CL-001.edcv.un.org	vavm0757	10.130.3.80	active	API server	RHEL 7.9	VLC	on-prem	VMWare	4	32	130 GB, 170 GB	JBoss Fuse	—
UN-API-P-CL-002.edcv.un.org	vavm0763.edcv.un.org	10.130.3.86	active	API server	RHEL 7.9	VLC	on-prem	VMWare	4	32	80 GB, 120 GB, 50 GB	JBoss Fuse	—
UN-API-P-CL-003.edcv.un.org	vavm0764.edcv.un.org	10.130.3.87	decommissioned	API server	RHEL 7.9	VLC	on-prem	VMWare	4	32	80 GB, 120 GB, 50 GB	JBoss Fuse	—
UN-API-P-DB-001.edcv.un.org	vavm0768	10.130.4.77	active	MySQL cluster node	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-P-DB-002.edcv.un.org	vavm0769	10.130.4.78	active	MySQL cluster node	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-P-DB-003.edcv.un.org	vavm0771	10.130.4.80	active	MySQL cluster node	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-P-GW-001.edcv.un.org	vavm0756	10.130.3.79	active	WSO2 API Gateway	RHEL 7.9	—	—	—	—	—	—	—	—
UN-API-P-GW-002.edcv.un.org	vavm0762	10.130.3.85	active	WSO2 API Gateway	RHEL 7.9	—	—	—	—	—	—	—	—

ESB — Enterprise Service Bus

Status

Handover planned: Before end of June 2026
Migration: Dev team migrating to Azure API Manager — they will take over the application
Current owner: DS team (Carlos)

Tech Stack

Container: JBoss Fuse
API management: WSO API Manager (API endpoints)
Database: MySQL — 3 nodes, clustered

Architecture

Java-based middleware
Sits between systems as integration layer
WSO handles external API endpoints

Servers

Located at: (TBD — on-prem RHEL, see ST items)
Environment: PROD + DR (alignment gap known issue)

Key Contacts

Dev team: handling Azure API Manager migration
DS team (Carlos): current operational owner

Known Issues

ESB DR alignment gap (PROD vs DR not in sync)
Log4j vulnerability — closed with justification (Azure migration planned)
SCOM alerts for REST API services unavailability (IM-1-12591273206)

Open Tasks

Alert mechanism in ESB (task-2746e915e7) — in sprint W13

Knowledge Gaps

[ ] List of PROD server hostnames
[ ] ESB DR gap — what exactly is out of sync?
[ ] Most common incidents and resolution steps
[ ] WSO API Manager version

Handover Status (updated 2026-03-26)

Zero DS involvement planned post-handover, but not fully decided yet
Azure API Manager migration ongoing — dev team leads

Upstream connections

Transparent to DS — not worth documenting fully given handover timeline

SCOM Monitoring (as of 2026-03-27)

Current active monitors

Server health (general)
CPU / disk
TCP check on api.un.org:443

Known gap

ESB API Services panel in SCOM is empty — old API monitors were removed and never replaced
Only app-level check is TCP port → does NOT confirm the application is actually working

Proposed fix (pending dev team response)

Option A: Dev team points to an existing meaningful API endpoint to monitor
Option B: Dev team creates a lightweight endpoint returning HTTP 200 OK
Next step: Saurav (dev team) to confirm which endpoint to use
Once confirmed: configure in SCOM, possibly open RFS

Related SCOM dashboards

Critical Applications dashboard
ESB dedicated dashboard

Azure API Manager (APIM) Rollout

Status: In progress — dev team migrating APIs one by one
Target completion: End of June 2026
Contact: Saurav Datta (ESB developer)

PMDS 2026 Objective (added 2026-04-01)

Objective:
Support the handover of the ESB platform to the development team and contribute to infrastructure cost optimization, ensuring a clear transition path by end of cycle.

Planned Outputs:

Support infrastructure cost optimization by assisting with resource consolidation, removal of unnecessary servers, and migration to Proxmox to reduce operational costs.
Collaborate with the development team to define and document the ESB handover process, covering infrastructure scope, responsibilities, and transition milestones.
Contribute to the migration of remaining API endpoints and post-migration infrastructure definition in coordination with the development team.
Ensure all prerequisites for removing ESB from the support catalog are identified, tracked, and progressed toward completion.

Notes:

PMDS cycle ends May 13, 2026 (mid-term review); full handover target is end of June 2026
API migration will not be complete by May 13 — outputs are framed as contributions/in-progress
Carlos's role: supporting (not leading) both handover and cost rationalization

Cost Rationalization & Proxmox Migration (added 2026-04-01)

Parallel effort running alongside the Azure API Manager migration
Goal: reduce operational costs — consolidating resources, removing unnecessary servers
VMware → Proxmox migration underway (cost-driven, not part of Azure migration track)
Some servers already decommissioned (Jan–Apr 2026)
Important distinction:
- Partial decommission = cost rationalization (remove unused infra now)
- Full decommission = end of migration (all on-prem ESB infra gone post-migration)
Carlos supports this effort; does not own cost targets or manage the rationalization project