25.4 25.2 25.1 24.4 24.3 24.2 24.1 23.4 23.3 23.2 23.1 22.4 22.3 22.2 22.1
25.4 25.2 25.1 24.4 24.3 24.2 24.1 23.4 23.3 23.2 23.1 22.4 22.3 22.2 22.1

Use-Case Packages

Use-case packages bundle a certain functionality or a functional context. The package may provide all aspects for connecting to a third-party system (e.g. an editing system). Or it may provide interfaces on top on an on-prem/hybrid/BYOC MAM system for make specific interfaces available. Or or may add some other type of functionality to the on-prem/hybrid/BYOC MAM solution. The crucial point is that each use-package stands for a certain block of functionality which extend the core features of an on-prem/hybrid/BYOC MAM solution.

Each use-case package may contain none, one, or more of the following components:

  • Agents,

  • backend modules providing API endpoints,

  • backend modules performing background jobs,

  • ConfigPortal configuration pages.

Each use-case package is deployed as a whole to an on-prem/hybrid/BYOC MAM solution.