AMAG Symmetry SMS (legacy architecture)
AMAG Technology·AE_HSc_AMAGConnectorGuide (Old Version)
Overview
The legacy AMAG connector integrates AlertEnterprise Guardian with AMAG Symmetry SMS via the older mediated architecture that predates the current direct-SOAP connector. It is preserved for customers still running this topology and should not be used for new deployments — point new integrations at amag instead.
What's different from the current [[amag]] connector: the legacy connector does not call the AMAG SMS XML API directly. Instead, it talks to the Alert SMS Web Service Client (Alert SMS Client/Agent) — a SOAP client / agent service built in .NET that runs on an IIS server, either co-located with the AMAG SMS XML API host or on a separate IIS server. The AE connector → Alert SMS Client → AMAG SMS XML API hop adds an intermediary that the current connector eliminated.
As with amag, cardholder reconciliation falls back to read-only JDBC directly against AMAG's SQL Server (the SMS XML API doesn't expose this operation). Provisioning/reconciliation capability coverage is the same as the current connector except SMS 9.6 is not listed as supported.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
2 methods supported
Basic auth credentials are configured in the AE connector and forwarded by the Alert SMS Client to the AMAG SMS XML API.
Same JDBC reconciliation path as the current connector — read-only SQL Server user with SELECT on multiMAX + multiMaxExport schemas.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
Alert SMS Web Service Client deployed on IIS
aeThe .NET-based Alert SMS Web Service Client (a.k.a. Alert SMS Client / Alert SMS Agent) must be deployed on either the AMAG SMS XML API host's IIS or a separate IIS server with network access to it. This intermediary is unique to the legacy architecture — the current amag connector does not require it.
AMAG SMS deployed and reachable
customerAn AMAG Symmetry SMS deployment (8.0 through 9.4) with the XML Open Integration Module installed and configured. The Alert SMS Client must be able to reach the SMS XML API.
Read-only JDBC user on AMAG SQL Server
customerSame JDBC reconciliation requirement as the current amag connector — a read-only user with SELECT on multiMAX.dbo and multiMaxExport.dbo schemas.
Known limitations
Documented constraints to set customer expectations before deployment.
Legacy — superseded by the current [[amag]] connector
importantThis connector is preserved for customers still running the .NET-mediated topology. New deployments should use the current amag connector, which eliminates the Alert SMS Client intermediary and adds support for SMS 9.6. AE Engineering should plan to migrate any new customer off this path.
Additional failure surface from the .NET intermediary
informationalThe Alert SMS Client adds an extra service hop with its own deployment, patching, and monitoring requirements. Network-partition scenarios between AE → IIS or IIS → SMS XML API surface as connector errors with less helpful messages than the direct-SOAP path provides.
PACS specifics
Identical to the current amag connector — AMAG's cardholder model is product-side, not connector-side.
Identical to the current amag connector — AMAG Access Groups composed of Readers, Reader Groups, Floor Groups, and Intrusion Areas, gated by TimeCodes.
Identical to the current amag connector — single SMS instance = single tenant; one connector per instance.
- Topology
- on-prem
- Event model
- polling
- Anti-passback
- unknown
- Holiday schedules
- unknown
- src/connectors/amag-legacy/source.pdf — Full connector guide (Old Version) — 26 pages, updated 2025-07-28
- src/connectors/amag-legacy/source.pdf — p5 — Supported Version
- src/connectors/amag-legacy/source.pdf — p7 — Connector Architecture