---
type: concept
title: Alternativer Webserver
tags: [web-hosting, cms, infrastructure]
related: [typo3-backend, ums, groupware, ressource-beantragen, webdav]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_typo3_webseiten_alternativer_webserver.md"]
---

# Alternativer Webserver

The **Alternativer Webserver** is a specialized hosting service provided by the [[universitatsrechenzentrum-urz]] (URZ) for websites that cannot be technically or content-wise realized or implemented within the university's central [[typo3-backend]] CMS.

## Service Characteristics
- **Non-Priority Service**: Unlike core/central services, this hosting has no assigned priority level, meaning high availability is not guaranteed.
- **Self-Managed**: The URZ provides the server infrastructure, but the resource owner is entirely responsible for:
    - The website content.
    - The installation and maintenance (updating) of any CMS used.
    - Technical troubleshooting of the site.
- **Support Limitations**: The URZ explicitly provides **no technical support** for the website's content or the CMS used.
- **Maintenance Obligation**: The resource owner is strictly required to keep the used CMS updated to ensure security.
- **Administrative Control**: The URZ reserves the right to take sites offline or migrate them without notice for valid reasons.

## Prerequisites and Approval Process
Before a resource can be provisioned, the following approvals and guidelines are mandatory:
- **Pressestelle (Press Office)**: Approval of the website concept and adherence to Corporate Identity/Design.
- **Datenschutzbüro (Data Protection Office)**: Approval of the privacy policy and data protection measures.
- **General Guidelines**: Compliance with university website guidelines, including the legal notice (Impressum) and accessibility requirements.

## Provisioning Workflow
The request process follows a strict sequence:
1. **Concept Approval/Coordination**: Coordinate the site concept (including legal notice, data protection, CI, and accessibility) with the [[pressestelle]] and [[datenschutzburo]].
2. **Ticket Initiation**: Create a ticket in [[groupware]] under the "Alternativer Webserver" category.
3. **Approval**: Wait for confirmation from both the Press Office and the Data Protection Office.
4. **UMS Application**: Use the [[ums]] to formally request the resource:
    - Path: `Meine Ressourcen` $\rightarrow$ `Ressource beantragen`.
    - Type: `Alternativer Webserver` (Category: `Websysteme`).
    - **Critical**: The Groupware ticket number must be entered in the description field, or the request may be rejected.

## Technical Implementation
- **Protocol**: Data exchange and file uploads are handled via [[webdav]].
- **URL Structure**: The upload path follows the format: `https://web.rz.uni-greifswald.de/[ressourcenname]/`.