Module

CDMS, CIAS and CRMS together

How CDMS, CIAS and CRMS work together, as a single unit in one process or as separate services. With flows walked through from login to the database and to the finished report. A good starting point for newcomers.

You can run CDMS and CIAS in two ways. In the subject area, both ways behave the same. Technically, they differ in who calls whom and how:

A single unit

CIAS embedded

one process, one application
CDMS asks CIAS through a method call
shared system database

Separate services

CIAS standalone

two processes
CDMS asks CIAS through HTTP
CIAS has its own database

CRMS joins in

CRMS produces reports from an application’s data. It follows the same pattern: embedded in the CDMS application or as a service of its own that the application calls over HTTP. In both cases CIAS says who requests the report and for which tenant. How it fits together:

Subject areas

The platform at a glance

The modules, the parties in a request and the key terms in pictures, before we get into the flows.

The CodamAI modulesThe parties in a requestThe key terms in picturesWho decides what?

A single unit or separate services

The two topologies of CIAS next to CDMS: embedded in one process or as a separate service. What runs in each, who calls whom, why both must behave the same in the subject area — and how that relates to the operating mode of the data storage, SINGLE or MULTI.

CIAS embedded (a single unit)CIAS as a separate serviceEmbedded and standalone comparedConfiguration decides what runsSINGLE and MULTI across both modulesWhy both modes must behave the same in the subject areaCRMS in the modes of operation

The path of a request, end to end

Flows walked through across all parties: from login to the row in the database, the path of the token, the tenant check in both operating modes, and what happens when something fails.

From login to the dataThe path of the tokenThe tenant check in both operating modesWhen CIAS is not reachableA write across all layersFrom the click to the report

Startup, provisioning, reconciliation

What happens before the first request arrives: cold start, registering the modules' roles and attributes with CIAS, a new tenant from start to finish, and the database schemas.

Cold start of an installationModules register roles and attributesA new tenant, end to endDatabases and schemasCRMS at start-up

Scenarios walked through

Typical business cases from start to finish, across CIAS and CDMS. Every scenario links to the individual pages.

A new customer is set upA colleague is invitedOne person in two tenantsSupport looks into a tenantA person leaves the companyA customer cancelsAn inspection report over the years