LMS Gateway and ESS Routing
Summary
Source-backed Draft reference for LMS Gateway and ESS Routing across the implemented Training Service and, where applicable, Gateway surface.
Audience
API consumers, engineering, QA, support, architecture, security, product, and implementation reviewers.
Reference Content
Route ownership
Gateway owns two LMS-related reads: the ESS training proxy and the ESS dashboard composition. Training Service owns the downstream enrollment collection. Gateway does not map a compatibility alias or shadow/cutover LMS family.
The shared Gateway sender forwards inbound request headers and correlation and applies configured timeout/retry behavior. Exact values and internal routing configuration are intentionally excluded. The single-module route returns a Gateway module envelope and can signal partial content on degradation. The dashboard returns a composed response with per-module status and a partial indicator.
Gateway Program registers platform authentication/authorization behavior, but the Training Service itself does not register or execute those controls. Trust between Gateway and Training and endpoint ownership enforcement therefore require confirmation. Native Training routes can be invoked independently wherever network exposure permits; no compatibility layer is documented because none was found.
Source References
microservices/src/gateway-api/Program.csmicroservices/src/gateway-api/EssEndpoints.csmicroservices/src/training-service/Program.csUI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
Related Articles
See Also
Keywords
- LMS API
- Training Service
- Source-backed contract
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly