A modern maintenance tool for the central SAP UI Landscape
Maintain the centrally managed Services, Workspaces, Message Servers, Routers and Web Dispatchers in one place — then publish the SAP UI Landscape configuration to every front-end computer over HTTPS.
Why we built it
SAP's built-in tooling covers the basics for a single administrator. Once a team shares the configuration, things break down fast.
Concurrent edits clash
Editing the central Landscape file from several admins in parallel silently overwrites the Services and Workspaces repositories. There is no record of who changed what, or when.
Passwords circulate between admins
Router strings embed passwords. With shared config editing, every collaborator needs to know every password — credentials get passed around informally just to set up a connection.
Single point of distribution
The central Landscape file quietly becomes the most critical piece of infrastructure for every SAP GUI for Windows, SAP GUI for Java and SAP Business Client front end — with no redundancy, no monitoring and no versioning.
Everything the SAP UI Landscape format describes — operated as a product
The repositories from the SAP UI Landscape specification — Services, Workspaces, Message Servers, Routers, Web Dispatchers, Includes — maintained through a typed UI instead of raw XML.
Services & Workspaces
Maintain the Services Repository (SAP GUI, NWBC, SAP Business Client, shortcuts) and group them into Workspaces with typed fields. No more hand-editing UUIDs.
Multi-user maintenance
An explicit edit lock per landscape prevents silent overwrites when several admins work in parallel. Power users edit, readers explore, admins govern.
Full version history
Every save persists a new version of the Landscape file with author, timestamp and note. Restore any prior version in two clicks.
Reusable repositories
Message Servers, Routers and Web Dispatchers live as first-class objects with stable UUIDs. Reference them by msid / routerid from any service — no duplicated configuration.
Define once, reuse without sharing credentials
One admin enters the router password once. Every other user picks that router from the Routers Repository by name — they reuse the connection without ever seeing the password.
Highly available HTTP delivery
The central Landscape file is served from an active/standby cluster over HTTPS. Front-end computers point to a single origin URL — no file share required.
Single sign-on via Active Directory
OIDC + PKCE through Keycloak. Role claims (Admin / Power / Reader) come straight from your existing Active-Directory groups.
Includes & bulk import
Import existing SAP UI Landscape XML files or CMDB exports through the Includes Repository. The diff view shows every change before you save.
Audit-ready change log
Every change is logged with actor, before/after value and origin. Hand auditors a ready-made trail instead of a screenshot dump.
A closer look
Real screens from our demo deployment — not a mock-up.
One view of the central Landscape
Counts for every repository, the most recently changed Landscape files, the highly available delivery cluster and continuous system-health checks — on a single screen.
Landscape files you can browse
Each entry is a centrally managed SAP UI Landscape configuration with its own Services and Workspaces repositories. Filter by region or environment in one click.
Routers Repository without exposed secrets
Router strings are stored centrally and rendered with masked segments. Reference a router from any service without ever pasting the password.
Every change, recorded
A per-landscape changelog with version number, author, note and timestamp — across the whole Services Repository.
The rendered SAP UI Landscape XML
Every save publishes a new central Landscape file. The bundle URL is what SAP GUI for Windows, SAP GUI for Java and SAP Business Client subscribe to — serving the Routers, Messageservers, Webdispatchers and Services repositories in the exact format the SAP UI Landscape specification expects.
Roles that match how you actually work
Three roles map directly to your existing Keycloak / Active-Directory groups — no custom permission model to maintain.
Landscape Admin
Full control. Bypasses the per-landscape edit lock. The only role allowed to delete landscapes or maintain the Routers Repository.
Power User
Day-to-day editor. Creates and updates landscapes, services and workspaces — must hold the edit lock to mutate a landscape's repositories.
Reader
Read-only browse and export. Audit and compliance teams can answer questions without risking any mutations.
Stop maintaining the central Landscape file by hand.
We'll show you the product running against your own SAP UI Landscape configuration.