Skip to content

Telematik ​

Use the Telematik service to manage Konnektors and card terminals, collect inventory, and verify SMC-B cards through jobs. Install it where it can reach the devices and the assigned Edge service.

Supported devices ​

DeviceSupported operations
Secunet KonnektorReachability, inventory, reboot, and SMC-B PIN status and verification.
Cherry ST-1506Reachability, system status, reboot, slot PIN mode, and remote SMC-B PIN entry.
Worldline ORGA 6141 onlineReachability, system status, and reboot.

Create a Telematik service client in Ordyn and copy its ID before installing. Prepare Docker and image verification on the host.

Installation ​

Checkout the Telematik deployment folder from the Ordyn compose repository:

bash
if [ ! -d /opt/ordyn-compose/.git ]; then
  git clone --filter=blob:none --sparse https://github.com/ordyn-project/compose.git /opt/ordyn-compose
fi
cd /opt/ordyn-compose
git sparse-checkout add telematik

Create the environment file:

bash
cd /opt/ordyn-compose/telematik
cp .env.example .env

Set these values in .env:

dotenv
ORDYN_TELEMATIK_EDGE_HOST=ordyn-edge.example.com
ORDYN_TELEMATIK_SERVICE_CLIENT_ID=<service-client-id>
ORDYN_LOG_LEVEL=info

Pull and verify the service image:

bash
docker compose pull
python3 /opt/cosign-docker-verify/verify.py

Continue only when the Telematik image verifies successfully and no failed verification message appears. Issue a service-client enrollment token for the Telematik service client in Ordyn, stop any running service container, and enroll the persistent service state:

bash
docker compose stop telematik
printf '%s' '<enrollment-token>' | docker compose run --rm -T --no-deps telematik npm run enroll -- --token-stdin

After enrollment succeeds, start the service:

bash
docker compose up -d telematik

To renew, recover, or replace its service-client certificate, issue a new token and run forced enrollment while the service is stopped:

bash
docker compose stop telematik
printf '%s' '<enrollment-token>' | docker compose run --rm -T --no-deps telematik npm run enroll -- --token-stdin --force

Run docker compose up -d telematik only after forced enrollment succeeds. Do not use docker compose exec for enrollment. See service-client certificate lifetime and renewal.

Telematik does not need public HTTPS ingress. It connects outbound to the assigned Edge service and must be able to reach the Konnektor and card terminal management addresses from its local network.

Credential profiles ​

Use Service Operator to manage the service and credential profiles under Services → Telematik. Create profiles in the devices' tenant with their management username, password, and TLS verification settings.

Card terminals and Konnektors use separate credential profiles. For Cherry ST-1506, use the Webadmin username configured on the device. Under Konnektor Credential Profiles, select Secunet and enter its administration credentials. Both profile types require a username and password.

Remove device assignments before deleting a profile.

Card terminal endpoints ​

Create an endpoint of kind Telematik card terminal with the terminal type, assigned service client, and credential profile. Set the management IP address on its primary network interface.

Konnektor endpoints ​

Create an endpoint of kind Telematik Konnektor in the device's tenant. Select Secunet, assign its Telematik service client and Konnektor credential profile, and set the management IP address on its primary network interface. Management runs through the Telematik service; the Konnektor does not need an Ordyn Agent.

Connected and active state ​

Connected, Active, and Online describe recent successful device reachability checks. The Telematik service's connection is shown separately. If the service disconnects, device status becomes inactive after its freshness window expires.

Reachability checks default to every minute and remain fresh for five minutes. Administrators can adjust the separate card terminal and Konnektor reachability settings.

Konnektor reachability checks use its management credentials. A green online indicator confirms management reachability; it does not confirm a working TI connection or a verified SMC-B. Check the reported probe error when a device stays offline.

System status collection ​

Use system status to inspect the terminal's operational facts. Ordyn collects status automatically; use Collect card terminal system status in a job for an on-demand collection. Review the collection time and error when results appear out of date.

Konnektor inventory ​

Run Collect Konnektor inventory in a job targeting the Konnektor. Reachability checks do not collect inventory; schedule an inventory job if it should refresh regularly.

The overview shows device identity, firmware, network interfaces, licences, and the last collection result. Its SMC-B cards table lists card identity, holder, expiry, and the terminal and slot reported by the Konnektor. This inventory does not verify a card's PIN.

Open Card Terminals to inspect the Konnektor's terminals and inserted SMC-B cards. Filter Connected and State to investigate unavailable terminals. State describes the terminal's relationship to the Konnektor; Active means connection is permitted. Connected shows whether it was connected when inventory was collected.

Ordyn links terminals to registered card terminal endpoints in the same tenant, matching MAC address first and IP address second. If a row is Not registered or Ambiguous, create the appropriate endpoint or correct its network interfaces so it can be identified uniquely. Collecting inventory does not create terminal endpoints.

Network interfaces and switch matching ​

Terminal IP and MAC addresses support IPAM, Net-node reachability probes, and switch-port matching. Assign a Net node through Service routing or inherit the folder or tenant route.

Reboot ​

Reboot a terminal from its endpoint actions or with the Reboot endpoint job task. This restarts the terminal without requesting a factory reset.

The same actions restart a Konnektor. Its reboot job step waits for the device to come back up, with a 15-minute limit. Reboot is blocked while an SMC-B PIN session is active. Follow the reboot with Collect Konnektor inventory when the job should refresh its device facts afterward.

Job steps ​

Use Telematik job tasks for status, inventory, and PIN operations. Follow SMC-B verification to build a job that coordinates the Konnektor and card terminal.

Logging ​

Review the failed job step's message and the Telematik service logs when investigating a device operation. Include a support bundle when requesting help.