This page describes the overall architecture of the Acta Nova Dialog Portal (ANDP): which components exist, what each one is responsible for, and how they communicate. It completes the architecture chapter of the RUBICON guideline document Richtlinien und Empfehlungen für den Einsatz von Konfigurationselementen, which describes the back office and refers to Gentics for the front-office part.

Big picture

ANDP has two halves that run in separate environments and talk to each other over HTTPS:

  • The back office is an Acta Nova installation with the Dialog Portal plug-in. It is the system of record: forms are defined here, submitted data is stored here as records, and workflows run here.

  • The front office is a Gentics CMP installation with the ANDP modules. It is what front-office users see and use: login, service catalog, forms, messages, tasks, business cases, profile – in the browser or in a native app.

The two halves are coupled only through REST calls between Gentics Mesh (with the Acta Nova Mesh plugin) and Acta Nova. No other front-office component talks to the back office directly, and the back office never talks to the browser.

Architecture of the Acta Nova Dialog Portal

Components

Front office (Gentics CMP)

Component Responsibility in ANDP

Gentics Portal | java
with the ANDP portal module (mesh-portal-andp)

The web application the front-office user interacts with. Renders pages and templates from Mesh content, handles the Keycloak login, enforces the first-login flow (terms of use, onboarding, wizard), serves the FormGen/MicroApp web builds and their static assets, and exposes the portal API under /api/andp/…​ (services, business cases, documents, favourites, translations, app configuration). All requests from the browser to the Acta Nova Mesh plugin are proxied through the portal under /api/acta-nova/…​, so the browser never reaches Mesh directly and the user’s access token is added server-side.

FormGen and the MicroApps
(React Native / Expo)

The user interface for the dynamic parts of the portal: FormGen renders the forms (controls, pages, form flow, summary, uploads); the Messages, Business Cases and Tasks MicroApps render the respective lists and details. The same packages are built for the web (served by the portal) and for the native app. Projects customise them by overriding element renderers, styling and translations.

Gentics CMS

Editorial content: pages, navigation, service descriptions, legal pages, the terms of use, and – since ANDP 8.5 – the ANDP forms themselves as external forms of form type andp. Editors place a form on a page with the form tag type. The CMS also hosts the ANDP custom tools (ANDP translations, terms-of-use reset) which are served by the Acta Nova Mesh plugin. Content is published to Gentics Mesh.

Gentics Mesh
with the Acta Nova Mesh plugin (acta-nova-plugin)

The content repository for the portal and the integration hub between front office and back office. The plugin owns a dedicated Mesh project (default eGov, configurable) with schemas for published forms, form drafts, uploaded binaries, notifications (messages), tasks, reports, transactions, published content and user references. It exposes the plugin REST API that the portal proxies, and it is the only component that calls Acta Nova. It also sends notification e-mails and push notifications.

Mesh Keycloak plugin (andp-keycloak-plugin)

Maps Keycloak users and tokens to Mesh users and roles (standard roles such as weak, strong, anonymous, guest, normal). With the dynamic roles feature it additionally fetches the user’s application-specific roles from Acta Nova through the Acta Nova Mesh plugin, so CMS pages can be protected by back-office roles.

Keycloak

Identity provider for front-office users (OpenID Connect). Holds local accounts and/or brokers external identity providers (for example ID Austria or Swiss AGOV). Issues the access tokens that the portal and Mesh use. Not part of the Gentics products, but part of every ANDP installation.

Reverse proxy / load balancer (for example Nginx)

TLS termination and routing in front of portal, CMS, Mesh and Keycloak. Must be configured for large uploads and long-running requests (see File upload configuration).

SMTP server, Firebase Cloud Messaging (optional)

Used by the Acta Nova Mesh plugin to notify users about new messages by e-mail and – for the native app – by push notification.

Back office (Acta Nova)

Component Responsibility in ANDP

Acta Nova with the Dialog Portal plug-in

Records management (records, incomings, dispatches, documents, workflows), master data (persons, organisations as business partners), Fachdaten (subject-specific data model), and the Dialog Portal extensions: front-office form definitions, form publishing, form initialisation/validation/submission endpoints, business partner services, the Dialog Portal workflow activities (dispatch, wait), user metadata and dynamic roles.

Acta Nova database, background server, Acta Nova Client (optional)

Standard Acta Nova infrastructure; see the RUBICON installation manual.

Communication paths

All back-office/front-office traffic is JSON over HTTPS between the Acta Nova Mesh plugin and Acta Nova. There are two directions, secured differently:

Direction Used for Security

Acta Nova → Mesh plugin

Publishing forms, creating notifications (messages), publishing content (documents/binaries), publishing report results

Optionally, a signed JWT in a configurable header (back-office authentication).

Mesh plugin → Acta Nova

Initialising, refreshing, validating and submitting forms; search, lazy catalogs, autocomplete; business cases, case contents and pending tasks; business partner existence; user metadata and roles; reports; file pre-upload; payment transactions

Optional signed JWT (RSA key pair generated by the plugin on first start) in a configurable header. The acting front-office user is passed in the X-User-Context header (JSON: user ID and whitelisted token claims, culture, form ID).

The portal never calls Acta Nova. It calls the plugin through Mesh (/api/v2/{project}/plugins/acta-nova/…​) with the user’s access token and the X-User-Context header; the plugin resolves the user from the token and forwards the request to Acta Nova with the back-office credentials described above.

Deployment

Separate networks

In practice the back office runs inside the organisation’s IT infrastructure (Windows servers, often with single sign-on for case workers), while the front office is exposed to the internet and runs as Linux containers – either on the organisation’s own Kubernetes/Docker infrastructure or operated by Gentics. Between the two there is usually a firewall; only the two HTTPS paths above need to be opened, in both directions. The Acta Nova base URL is configured in the plugin (actaNovaBaseUrl); the front-office base URL is configured in Acta Nova (DialogPortal_FrontOfficeConnectionBaseURL).

Instances

A typical ANDP installation runs these front-office instances:

  • one Gentics CMS,

  • one Gentics Mesh with the Acta Nova and Keycloak plugins,

  • one or more Gentics Portal \| java instances (the Dialog Portal; projects may run additional portal instances, for example a separate case-worker-facing portal),

  • one Keycloak,

  • the reverse proxy.

The ANDP reference project (andp-project) provides the Docker Compose / Helm setup, portal templates, queries and configuration for a customer project, and is updated with every ANDP release.

Single and multi-tenant back office

Acta Nova can be split into several tenants ("Mandanten"). ANDP supports a single front office in front of several tenants: business partner services and master data live in a master data tenant, business services live in business tenants, and persons and organisations are synchronised from the master data tenant into the business tenants. See the RUBICON guideline document, chapter Single- vs. Multimandanten-Installation. Most installations use a single tenant.

Native app

The portal can also be delivered as a native app for Android and iOS. The app contains the same MicroApps as the web portal, authenticates against Keycloak (optionally with biometrics), loads its configuration from the portal (/api/andp/appconfig), and uses the same portal and plugin APIs. Branding and store publishing are done per project. See Native apps and App biometric and Keycloak configuration.