Honeywell Pro-Watch DTU (SOAP)
Honeywell·AE_HSc_HoneywellProWatchDTUConnectorGuide
Overview
The Honeywell Pro-Watch DTU connector integrates AlertEnterprise Guardian with Honeywell Pro-Watch via the DTU (Data Transfer Utility) API — Honeywell's SOAP-based integration surface. This is the intermediate path between the older HSDK-based connector (honeywell-prowatch, for Pro-Watch 4.1-4.2) and the modern REST-based connector (pro-watch-dtu-rest, for Pro-Watch 6.x). The DTU path extends coverage to Pro-Watch 4.2, 4.5, 5.5, 6.0, and 6.5.
The connector architecture is straightforward: Alert Pro-Watch DTU Connector → Pro-Watch DTU API (SOAP) → Pro-Watch System. The connector talks SOAP over HTTPS to the DTU API; no intermediate database access is required (unlike the HSDK variant, which uses direct JDBC for reconciliation). Both provisioning and reconciliation flow through the same SOAP transport.
Like the HSDK variant, roles are assigned at the badge level in Pro-Watch, not at the user level — a quirk worth communicating to operators expecting standard user-centric role assignment.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
Authentication to the Pro-Watch DTU API uses a username + password configured in AE connector System Parameters. Credentials are sent in WSSE-style SOAP headers over HTTPS.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
Pro-Watch DTU API enabled
customerThe Pro-Watch DTU (Data Transfer Utility) API must be enabled on the Pro-Watch server and reachable from the AE application server over HTTPS.
Pro-Watch operator account with API privileges
customerA dedicated Pro-Watch operator account with sufficient privileges for the integration's required operations. The connector guide's "Minimum Permissions for Provisioning and Reconciliation Operations" section enumerates the minimum privilege grant set.
SSL certificate trust
aeThe Pro-Watch DTU API's SSL certificate must be imported into the AE host's JVM cacerts keystore. Without it, the SOAP client fails with javax.net.ssl.SSLHandshakeException.
Known limitations
Documented constraints to set customer expectations before deployment.
Roles assigned at badge level (not user level)
importantSame constraint as honeywell-prowatch — Pro-Watch assigns access levels to badges, not directly to users. Multi-badge cardholders may have different role sets per badge.
PACS specifics
Pro-Watch cardholder model identical to honeywell-prowatch — see that record for the BADGE_ALL / BADGE_CARD_ALL schema. The DTU API exposes the same data through SOAP operations.
Same as honeywell-prowatch: access assigned at badge level via permanent / timed / temporary clearance tables; CLEAR table holds master clearance definitions.
Single Pro-Watch instance per AE→Pro-Watch DTU connector.
- Topology
- on-prem
- Event model
- polling
- Anti-passback
- unknown
- Holiday schedules
- unknown
- src/connectors/honeywell-pro-watch-dtu/source.pdf — Full connector guide — 29 pages, updated 2025-05-23
- src/connectors/honeywell-pro-watch-dtu/source.pdf — p5 — Supported Version