Source: projects/identity-management/oim-kb-update/sandbox-host/2026-04-27-api-server-backend-artifacts.md

> Source: projects/identity-management/oim-kb-update/sandbox-host/2026-04-27-api-server-backend-artifacts.md

API Server Backend Deployment Artifacts

Scope

Read-only sandbox host inspection to locate the deployed API Server backend that serves the Web Portal generated client endpoints.

Evidence

The Web Portal frontend source tree at C:\Dev\IdentityManager.Imx\imxweb is not the API Server implementation. It is the Angular/Nx frontend plus generated TypeScript client packages.

The live IIS deployment maps the portal to:

Important deployed API Server files:

• C:\inetpub\wwwroot\ApiServer\appsettings.json
• C:\inetpub\wwwroot\ApiServer\web.config
• C:\inetpub\wwwroot\ApiServer\InstallState.config
• C:\inetpub\wwwroot\ApiServer\bin
• C:\inetpub\wwwroot\ApiServer\App_Data\Cache\AssemblyCache
• C:\inetpub\wwwroot\ApiServer\App_Data\WebCache\html\qer-app-portal\appconfig.json

The deployed portal appconfig.json sets:

• WebAppIdentifier: portal
• WebAppIndex: portal
• start route: dashboard

Backend Assemblies

The endpoint implementation lives in deployed backend assemblies and cached generated assemblies, not in the Angular source tree.

Relevant API composition assemblies under C:\inetpub\wwwroot\ApiServer\bin include:

• QBM.CompositionApi.dll
• QBM.CompositionApi.Server.dll
• QBM.CompositionApi.Server.Host.dll
• QBM.CompositionApi.Dialog.Base.dll
• QER.CompositionApi.dll
• QER.CompositionApi.Server.PlugIn.dll
• CompositionApiToSwagger.dll
• CompositionApiToSwagger.Settings.dll
• Module composition assemblies such as ADS.CompositionApi.dll, ATT.CompositionApi.dll, and related module DLLs.

Relevant generated/cached assemblies under C:\inetpub\wwwroot\ApiServer\App_Data\Cache\AssemblyCache include:

• TypedWrappers_*.dll
• Jobs_*.dll
• DlgObj_*.dll
• ProductScripts_*.dll
• Scripts_*.dll
• Tables_*.dll
• Tmpl_*.dll
• Tree_*.dll
• WebServices_*.dll

The installed service binary folder C:\Program Files\One Identity\One Identity Manager Service\bin also contains composition/customizer assemblies, including QER.CompositionApi.*, QBM.CompositionApi.*, and QER.Customizer.*.

Interpretation

The generated Web Portal client methods map to API Server composition endpoints. API Server then crosses into schema/object-layer behavior through composition API handlers and typed wrappers. The HTML decompile index should therefore show the frontend route as:

Angular service/component -> generated API client method -> API Server composition endpoint -> customizer/object-layer method or event -> DB table/trigger/process evidence

This also explains why DialogMethod alone is insufficient. Several observed portal actions correlate with decompiled customizer methods but are absent from the DialogMethod catalog.