dohertj2/lmxopcua
1
0
Fork 0
Code Issues 3 Pull Requests 2 Actions Packages Projects Releases Wiki Activity
Files
60695179ee5c80b0525a4478ec29edc2911ba291
lmxopcua/docs/drivers/Historian.Wonderware.md
T
Joseph Doherty 2124f21ab6
v2-ci / build (pull_request) Failing after 38s
Details
v2-ci / unit-tests (tests/Core/ZB.MOM.WW.OtOpcUa.Cluster.Tests) (pull_request) Has been skipped
Details
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.ControlPlane.Tests) (pull_request) Has been skipped
Details
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.Tests) (pull_request) Has been skipped
Details
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests) (pull_request) Has been skipped
Details
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Security.Tests) (pull_request) Has been skipped
Details
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests) (pull_request) Has been skipped
Details
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.IntegrationTests) (pull_request) Has been skipped
Details
docs(historian-gateway): document gateway backend, config keys, EnsureTags hook, known gates; retire Wonderware from docs 
HistorianGateway is now the sole historian backend (read + alarm SendEvent +
continuous WriteLiveValues). Document the final state and retire the Wonderware
sidecar from the docs/config/labels:

- CLAUDE.md: rewrite the Historian section — ServerHistorian /
  ContinuousHistorization / AlarmHistorian config keys, the IHistorianProvisioning
  EnsureTags hook, the GatewayAlarmHistorianWriter SendEvent path + ReadEvents
  dependency on gateway RuntimeDb:EventReadsEnabled=true, gateway-side
  prerequisites (RuntimeDb flags + historian:read/write/tags:write scopes),
  migration note, and two KNOWN-LIMITATION callouts (live-validation gate +
  empty historized-ref-set recorder follow-on).
- appsettings.json: fix the stale ServerHistorian block (Host/Port/SharedSecret/
  ServerCertThumbprint -> Endpoint/ApiKey/UseTls/AllowUntrustedServerCertificate/
  CaCertificatePath/CallTimeout, keep MaxTieClusterOverfetch); add a disabled
  ContinuousHistorization block; prune the orphaned Wonderware keys from
  AlarmHistorian (keep the SQLite knobs). ApiKey env-supplied via
  ServerHistorian__ApiKey (commented; valid strict JSON via _comment keys).
- README.md + docs (Historian.md, AlarmHistorian.md, Configuration.md,
  ServiceHosting.md, DriverLifecycle.md, drivers/README.md, Uns.md, VirtualTags.md,
  AlarmTracking.md, Client.UI.md, README.md, TestConnectProbes.md): retire the
  Wonderware historian backend from current-backend descriptions; fix the stale
  ServerHistorian/AlarmHistorian config tables (now gateway shape); convert
  drivers/Historian.Wonderware.md to a retired stub pointing at the gateway.
- Source/UI labels (descriptive text only, no behavior change):
  OtOpcUaServerHostedService.cs, HistoryPaging.cs, OtOpcUaSdkServer.cs,
  HistorianAdapterActor.cs, VirtualTagModal.razor, ScriptedAlarmModal.razor,
  AlarmsHistorian.razor now name the HistorianGateway backend.

Build clean (0 errors); AdminUI.Tests green (514 passed).

Claude-Session: https://claude.ai/code/session_012SDSQ3AcaXqPcBtDESBRii
2026-06-26 19:46:27 -04:00

2.6 KiB
Raw Blame History

Wonderware Historian Backend — RETIRED

This backend has been retired. The bespoke Wonderware TCP/ArchestrA historian sidecar (OtOpcUaWonderwareHistorian) and its Driver.Historian.Wonderware* projects — plus the vestigial Historian.Wonderware driver type — were removed. HistorianGateway is now the sole historian backend for OtOpcUa (read, alarm-write, and continuous historization).

What replaced it

OtOpcUa now consumes the ZB.MOM.WW.HistorianGateway sidecar through the Gitea-feed ZB.MOM.WW.HistorianGateway.Client gRPC package (historian_gateway.v1), behind the IHistorianGatewayClient seam in ZB.MOM.WW.OtOpcUa.Driver.Historian.Gateway:

  • HistoryRead → GatewayHistorianDataSource over the ServerHistorian appsettings section.
  • Alarm history → GatewayAlarmHistorianWriter (the gateway SendEvent path) behind the durable SqliteStoreAndForwardSink; alarm-history ReadEvents needs the gateway running RuntimeDb:EventReadsEnabled=true.
  • Continuous historization → a crash-safe FasterLog outbox + ContinuousHistorizationRecorder draining to the gateway's WriteLiveValues (ContinuousHistorization section); needs the gateway running RuntimeDb:Enabled=true.
  • Tag provisioning → AddressSpaceApplier fires a non-blocking IHistorianProvisioning EnsureTags hook for added historized tags.

The gateway API key must carry the scopes historian:read, historian:write, historian:tags:write.

Where to read now

  • ../Historian.md — the full historian guide (read path, alarm path, continuous historization, config keys, migration note).
  • README.md — driver / back-end overview.
  • ../ServiceHosting.md — deployment (the historian backend is the external HistorianGateway, not an installed sidecar).

Migration

Deployments that carried the old ServerHistorian Wonderware keys must rename them:

Old (Wonderware) key New (gateway) key
ServerHistorian:Host + :Port ServerHistorian:Endpoint (https://host:5222)
ServerHistorian:SharedSecret ServerHistorian:ApiKey (supply via env ServerHistorian__ApiKey)
ServerHistorian:ServerCertThumbprint ServerHistorian:CaCertificatePath (+ UseTls / AllowUntrustedServerCertificate)

The AlarmHistorian section's old Wonderware connection keys (Host/Port/UseTls/ServerCertThumbprint/SharedSecret) were pruned — remove them; the SQLite store-and-forward knobs are retained and the downstream connection is now sourced from ServerHistorian.

Reference in New Issue View Git Blame Copy Permalink