Demo system setup
The demo system consists of the minimum necessary components to demonstrate functionality and operation.
All required components run on one server in the cloud.
These are primarily the orchestration engine services, the workflow platform, database and various HTTP servers.
A more complex integration was deliberately omitted. The necessary services are running as Docker containers on a cloud server.
Test case design
The test case is kept simple, but demonstrates the main functionality and provides a first insight into how the deletion orchestration works.
-
To illustrate multi-tenant capability, the case consists of two clients with five configured applications each.
-
An orchestration sequence for each tenant contains three or four steps.
-
Three batches per tenant for the same sequence with a random number of generated records (1 to 20'000) per batch are delivered to the engine via orchestration API.
-
A full demo case is processed at least once per hour, resulting in a total of more than one million records per day.
-
The full completion of a demo case including the participation of all applications with parallel execution of each tenant takes less than half a minute.
Business configuration
The test case consists of two tenants with four or five configured applications each and a minimal orchestration sequence based on one business object type.
Tenant 3WX
-
Application: PMS - Master (MST), Policy Master Application
-
Application: PVE - Veto (VET), Policy Veto Application
-
Application: PD1 - Dependent (DEP), Policy Delete Application 1
-
Application: PD2 - Dependent (DEP), Policy Delete Application 2
-
Business Object Type: PBO - Policy Business Object Type
-
Sequence: PMS-PBO-PVE-NVE - Step 1: Non-Veto Check (NVE) at application PVE for "Master Application - Business Object Type" combination PMS-PBO
-
Sequence: PMS-PBO-PD1-DEL - Step 2: Deletion (DEL) at application PD1 for "Master Application - Business Object Type" combination PMS-PBO
-
Sequence: PMS-PBO-PD2-DEL - Step 3: Deletion (DEL) at application PD2 for "Master Application - Business Object Type" combination PMS-PBO
Tenant YOA
-
Application: PMS - Master (MST), Policy Master Application
-
Application: PVE - Veto (VET), Policy Veto Application
-
Application: PD1 - Dependent (DEP), Policy Delete Application 1
-
Application: PD2 - Dependent (DEP), Policy Delete Application 2
-
Application: PD3 - Dependent (DEP), Policy Delete Application 3
-
Business Object Type: PBO - Policy Business Object Type
-
Sequence: PMS-PBO-PVE-NVE - Step 1: Non-Veto Check (NVE) at application PVE for "Master Application - Business Object Type" combination PMS-PBO
-
Sequence: PMS-PBO-PD1-DEL - Step 2: Deletion (DEL) at application PD1 for "Master Application - Business Object Type" combination PMS-PBO
-
Sequence: PMS-PBO-PD2-DEL - Step 3: Deletion (DEL) at application PD2 for "Master Application - Business Object Type" combination PMS-PBO
-
Sequence: PMS-PBO-PD3-DEL - Step 4: Deletion (DEL) at application PD3 for "Master Application - Business Object Type" combination PMS-PBO
Resources
The live demo system runs permanently unnoticed in the background with very low configuration, maintenance and resource requirements.
-
Six CPUs fully utilized for a short period of time when the test case is running and at zero percent load otherwise.
-
The cloud server has a total of 32 GB of memory, of which the orchestration engine and all required components (including databases, etc.) consume 16 GB.
EN