Alert EnterpriseWiki

Siemens SiPort (Personnel Data Import / JDBC)

Siemens·AE_HSc_SiemensSIPORTConnectorGuide

PACSactiveSiemens SiPort MP 2.2, 3.0
Transports
jdbc
Direction
bidirectional
Authentication
SiPort database credentials
Topology
on-prem

Overview

The Siemens SiPort connector integrates AlertEnterprise Guardian with Siemens SiPort — the smaller / midmarket Siemens PACS line (distinct from si-pass, Siemens' enterprise PACS). This connector uses the legacy Personnel Data Import (ODBC/JDBC) integration path; for the modern REST-based SiPort integration, see siport-rest.

The architecture is unusual: rather than calling an API, the connector writes user records directly into a SQL database that SiPort's SIPORT Personnel ODBC Import Windows service polls and imports into the live SiPort system. There is no real-time API surface — provisioning latency is bounded by how often the Personnel ODBC Import job runs. This is a customer of Siemens' older integration pattern, which limits two-way visibility (AE writes; SiPort imports; AE reconciles by reading the same DB).

The connector ships as ALNTSiportConnector-5.0-SNAPSHOT.jar. Capabilities include Lock User / Unlock User as first-class verbs (uncommon), and explicit Add Badge with 14-digit badge ID as a distinct operation (Modify/Activate/Deactivate work with 6 or 14-digit badge IDs).

Architecture

Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.

Composing diagram — running ELK layout6 actors · 5 edges

Authentication

1 method supported

SiPort database credentials
basic

Authentication is to the SiPort database via JDBC — database user with INSERT / UPDATE / DELETE privileges on the Personnel Data Import staging tables, and SELECT for reconciliation queries. Credentials configured as System Parameters.

Credential storage
Encrypted in AE connector configuration.

Prerequisites

Everything that must be in place for this connector to work, with the owner who's responsible.

SiPort Personnel Data Import pre-configured

customer

The "SIPORT Personnel Data Import" feature must be pre-configured on the SiPort side. The customer must select the Database, Import Table, and Key-Field values, and move the necessary fields from the "No Imported fields" list to the "Imported fields" list — only those fields will be provisioned via this path.

SIPORT Personnel ODBC Import Windows service running

customer

The SIPORT Personnel ODBC Import job (a Windows service on the SiPort host) must be running. Without it, AE writes staging records but they are never imported into SiPort. The Windows service runs on a configurable interval — operators must align Guardian's provisioning latency expectations with this interval.

SiPort license for Data Import process

customer

The SiPort system must hold an appropriate license to process user records through the Data Import process. This is a Siemens-side license module, not an AE-side license.

Known limitations

Documented constraints to set customer expectations before deployment.

Indirect provisioning via batch import — no real-time API

important

Provisioning operations are asynchronous: AE writes to the SiPort staging database, and the Personnel ODBC Import job (a Windows service) periodically imports staging records into the live SiPort system. Provisioning latency = max(write-to-DB time, ODBC Import job interval). Customers expecting real-time provisioning should either tighten the ODBC Import schedule or migrate to siport-rest for a true API.

14-digit Add Badge limitation

informational

The Add Badge capability only supports 14-digit badge IDs. Modify Badge, Activate Badge, Deactivate Badge, and Remove Badge work with 6 or 14-digit badge IDs, but initial Add must use 14-digit. Operators using 6-digit cards must seed the badge by some other means (manual entry on SiPort side) before AE can modify it.

PACS specifics

Cardholder model

SiPort cardholders modeled with Profile assignments and badges (6 or 14-digit). Last-used date/time on badges is optionally reconciled (see Chapter 4 of the connector guide for the additional configuration).

Access rights model

Roles in SiPort are called Profiles. The connector supports Modify User Roles/Profiles + Remove User Roles/Profiles. Full + incremental reconciliation of Profiles is supported.

Multi-tenancy

Single SiPort instance per AE→SiPort connector.

Topology + Events
Topology
on-prem
Event model
polling
Anti-passback
unknown
Holiday schedules
unknown
Source materials
  • src/connectors/siemens-siport/source.pdf Full connector guide — 41 pages, updated 2024-08-23
  • src/connectors/siemens-siport/source.pdf p5 — Supported Version
  • src/connectors/siemens-siport/source.pdf p7 — Connector Architecture
Verifying access
Desktop only

The AE Mobile Wiki needs a bigger screen.

The diagrams, comparisons, and animated flows aren't built for phones. Open this link on your laptop or desktop browser and you'll see the full reference.

wiki.alertenterprise.app

Same Google sign-in as the AE App Hub — you'll be in once you open it on a larger screen.