1. Introduction#

Welcome to the architecture documentation of UCS.

This document doesn’t cover installation, the usage of UCS or parts of the product. For instructions about how to install and use UCS, see Univention Corporate Server - Manual for users and administrators [1].

The document is released step by step after each part is finished. The beginning is at the first, high level.

Your feedback is welcome and highly appreciated. If you have comments, suggestions, or criticism, please send your feedback for document improvement.

For feedback on single sections, use the feedback link next to the section title.

1.1. Audience#

This document is for consultants, administrators, solution architects, software developers and system engineers. It describes the technical architecture of UCS on three different detail levels.

The first, high level, positions UCS in the known IT world and describes the concepts. This view helps readers to understand the principles of UCS. Chapters 2 and 3 assume you are familiar with information technology in general and that you have heard of computer network building blocks and software.

The second, medium level, is for administrators and solution architects. It covers the product components and the numerous services UCS offers to IT infrastructures. You read about the user facing product components and what services UCS runs. You learn what open source software contributes to the capability of UCS and how it interoperates together.

Software developers and system engineers get an overview of the technical parts.

A general understanding of Linux operating systems for servers and IT administration are beneficial for understanding.

For notation, the document uses the C4 model notation and the ArchiMate notation. For more information, refer to Architecture notation.

The third, low level is about the libraries, internal systems and storage. It describes the pieces a software developer and system engineer needs to know to contribute to UCS. General knowledge of software architecture and software engineering are helpful at this level.

1.2. Learning objectives#

After reading this document you have a broad understanding of the UCS architecture. It equips consultants, administrators, and solution architects to better plan their IT environment with UCS. It enables software developers and system engineers to get familiar with software development for UCS.

1.3. How to use the document#

This document contains numerous figures. As far as possible, they use SVG format. If you need a larger view of the image, open it in a dedicated tab in your web browser:

To open the figure in the same tab:

  1. Click the figure.

Alternatively, to open the figure in a new tab:

  1. Right click the figure.

  2. Click Open Image in New Tab from the context menu.

To open the figure in a new tab:

  1. Right click the figure.

  2. Click Open Image in New Tab from the context menu.