5. Services

This section covers numerous services that UCS offers to IT infrastructures. It’s for administrators and solution architects.

Hint

For architecture notation, this part of the document uses ArchiMate® 3.2, a visual language with a set of default iconography for describing, analyzing, and communicating many concerns of enterprise architectures. For more information about how the document uses the notation, refer to ArchiMate.

• 5.1. Univention Configuration Registry (UCR)
  • 5.1.1. UCR architecture
  • 5.1.2. UCR persistence layer
  • 5.1.3. UCR variable priorities
  • 5.1.4. UCR limitations
• 5.2. Univention Directory Manager (UDM)
  • 5.2.1. UDM architecture
  • 5.2.2. Dependencies for UDM
  • 5.2.3. UDM modules
  • 5.2.4. UDM data
• 5.3. UDM HTTP REST API
  • 5.3.1. Architecture
  • 5.3.2. Technology
  • 5.3.3. Request flow
  • 5.3.4. Capabilities
  • 5.3.5. RESTful architecture
  • 5.3.6. Dependencies
• 5.4. UMC - Univention Management Console
  • 5.4.1. UMC communication
  • 5.4.2. Authentication
  • 5.4.3. UMC backend
  • 5.4.4. UMC web frontend
  • 5.4.5. UMC modules
• 5.5. UCS portal service
  • 5.5.1. Portal frontend
  • 5.5.2. Portal backend
  • 5.5.3. Dependencies for UCS portal
• 5.6. App Center service
  • 5.6.1. App Center interfaces
  • 5.6.2. App Center actions
  • 5.6.3. App Center apps cache
  • 5.6.4. App integration
  • 5.6.5. Dependencies for the App Center