SAIF.Services.WCF.UC4.Host — SOAP service documentation¶
SAIF.Services.WCF.UC4.Host is a WCF SOAP service host that publishes a single UC4 route backed by SAIF.Services.WCF.UC4.Host.Services.UC4Service, forwarding caller-supplied job-execution requests to a downstream UC4 job-scheduling service after evaluating an environment-scoped allow/deny rule list.
| Field | Value |
|---|---|
| Host project | SAIF.Services.WCF.UC4.Host |
| Framework | WCF (System.ServiceModel, .NET Framework 4.6.2) |
| Host | IIS — Global.asax + a code-behind class inherited from System.Web.HttpApplication |
| Activation | Route-based (ServiceRoute + ServiceHostFactory in Application_Start) |
| Activation source | src/WCF/SAIF.Services.WCF.UC4.Host/Global.asax.cs:16 |
| Service classes | 1 (SAIF.Services.WCF.UC4.Host.Services.UC4Service) |
| Contract assembly | SAIF.Services.WCF.Contracts (namespace; assembly identity not resolvable) — external, arrives transitively via SAIF.Framework.Core 2.0.23079.1* |
| ASP.NET compatibility | [AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)] |
| Service behaviors | [LogErrorBehavior] applied — the type is external (SAIF.Services.WCF.Common.Extensions, package identity unresolved) and is not the in-repository SAIF.Services.WCF.Extensions.LogErrorBehaviorAttribute used by the sibling WCF host** |
| Metadata publication | <serviceMetadata httpGetEnabled="true"/> |
| Deployment variants | Single deployed artifact app via Stages/v2/deploy-stages-api-iis.yml@templates; the build pipeline runs the web build template twice (internal/external triples) but this host defines no ReleaseExternal configuration and ships no configuration transform — see Operational runbook |
One document set per host project. Framework.CoreServices.WCF has four SOAP-typed projects (WCF, SAIF.Services.WCF32.Host, SAIF.Services.WCF.UC4.Host, SAIF.Services.WCF.PDF.Host), but only two — WCF and this host — have deployment evidence (a scanned pipeline names them). The other two lack both a pipeline reference and a .nuspec reference and are not documented; see docgen-manifest.md → Libraries not documented. This section documents SAIF.Services.WCF.UC4.Host only; WCF is documented in its own section, linked from the shared services catalog.
Documentation sections¶
| Section | Description |
|---|---|
| Overview | Purpose, business context, and capability summary |
| Architecture | Layering, dispatch path, composition root, and integration points |
| Activation and hosting | Route registrations, host inventory, and deployment variants |
| Operations | Operation catalog with per-contract detail pages |
| Faults and error pipeline | Fault contracts, error handlers, and what a caller receives |
| Authentication and authorization | Identity, authorization enforcement, and role requirements |
| Dependencies | Libraries, packages, services, and database connections |
| Configuration | Runtime-resolved configuration and the Web.config surface |
| Operations and processes | End-to-end processing workflows behind the operations |
| Business rules | Rules enforced during message processing |
| Operational runbook | Deployment, health checks, logs, faults, error recovery |
| Tech debt | CRITICAL and HIGH severity findings |
Service classes¶
| Service class | Route | Operations | Also hosted in | Documentation |
|---|---|---|---|---|
SAIF.Services.WCF.UC4.Host.Services.UC4Service |
UC4 |
8 | — (registered by exactly one host, on exactly one route name, in exactly one solution — see Activation and hosting) | Docs |
Consumed SOAP proxies¶
This host consumes no SOAP service. There is no Service References or Web References folder under src/WCF/SAIF.Services.WCF.UC4.Host/, no generated Reference.cs/Reference.vb, no ClientBase<-derived type, no new ChannelFactory< construction, and no <client> element in Web.config. The host does make one outbound call — UC4Client to a downstream UC4 scheduling service through the SAIF.Services.UC4 / SAIF.Web.API.Clients packages — but this is a packaged framework client, not a consumed SOAP proxy, and its protocol is not visible from this repository.**
Related documentation¶
- Overview
- Architecture
- Activation and hosting
- Operations
- Faults and error pipeline
- Authentication and authorization
- Dependencies
- Configuration
- Operations and processes
- Business rules
- Operational runbook
- Tech debt
Note: Statements marked with
*were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts. Statements marked with**could not be confirmed; treat as unknown until verified.
Sources¶
src/WCF/SAIF.Services.WCF.UC4.Host/Global.asax.cssrc/WCF/SAIF.Services.WCF.UC4.Host/Web.configsrc/WCF/SAIF.Services.WCF.UC4.Host/SAIF.Services.WCF.UC4.Host.csprojsrc/WCF/SAIF.Services.WCF.UC4.Host/UC4Service.cs