This data object represents cloud-based applications and their configurations in the company. It manages essential information such as database mappings, email settings, security requirements and backup strategies for each application. The object supports key cloud management processes, including application provisioning, data backup and recovery, and the configuration of security parameters. It is closely related to databases and release versions and enables efficient management and monitoring of the cloud infrastructure.
identification
In this info area you will find information that can be used to identify the data record. This is usually the code and the name, together with other important information.
| Property | Description |
| Started | Switching the client on and off. Switching the client off saves the environment and resources. After saving, it can take up to one hour before the client is actually switched on or off. |
| Designation | Long, detailed description of the application |
| URL | Url in the format http:// or https:// for the application that is operated in the cloud |
| Application type | Type of client, in the context of staging environments, e.g. DEV, QA, production |
Operational responsibility
These characteristics describe the organizational responsibility for the operation of an application. They include information on the responsible area, contact persons and operational assignments.
| Property | Description |
| account | Data on the customer using the application |
| Responsible | Person responsible for the client's operations |
Details
This group contains detailed information and technical specifications for the application. Here you will find information that is relevant for the precise characterization and management of the software.
| Property | Description |
| Admin Access Portal | Access data of the client's administrator account |
| Description | Description of the application, e.g. specification of the business processes and specialist tasks supported by this application |
| Superordinate | Higher-level client within a client hierarchy. The data can only be transported from this client to the higher-level client. The subordinate client has no access to the data in the superordinate client. |
| Certificate | The TLS certificate with which the application is secured |
| Database | Specification of the database that stores the client's data |
| server | Virtual or physical server on which the client is operated |
Protection requirements
The protection requirement summarizes the security-relevant properties of an application. This includes classifications for the confidentiality, integrity and availability of the processed data and systems.
| Property | Description |
| Confidentiality | Classification of the confidentiality of the application in accordance with BSI IT-Grundschutz or ISO 27001 to ensure that confidential information cannot be accessed or passed on without authorization (breach of confidentiality). |
| Availability | Classification of the availability of the application according to BSI IT-Grundschutz or ISO 27001 to ensure that unauthorized users are prevented from accessing information and systems (breach of confidentiality). |
| Integrity | Classification of the integrity of the application according to BSI IT-Grundschutz or ISO 27001 to ensure that the correctness of the information and the functioning of systems is given (breach of integrity). |
cloud management
This feature group includes properties for managing and controlling cloud resources for an application. It contains information on cloud services, deployment models and configurations for operation in the cloud environment.
| Property | Description |
| Specific version (must exist in the channel, otherwise error!) | If empty, the latest release with download release and automatic update from date is used as before. If not empty, the specified release is used without further checks (and no check, i.e. "user risk"). |
| Branch | Specification of the branch from GIT which is to be used for updating the client. |
| Code | Abbreviation for the application that is being operated. This code is used when logging into an app to determine the correct URL for the user. Only the URLs of certain application types are used |
| update procedure | Procedure for importing an update for the client |
| Channel | Indication of the status of the source code on the basis of which the client is running, e.g. development, beta, release |
| Installed version | Displays the currently installed version of the cloud application. The version number follows the principle of semantic versioning and enables precise tracking of the installation status as well as the planning of updates and maintenance work. |
Time window for updates
This feature group defines the time periods in which maintenance work and updates can be carried out for the application. It helps to plan system updates with minimal disruption to operation.
| Property | Description |
| From | Start of the time window in which the client administration may import an update of the client. The time window must not extend beyond midnight. |
| Until | End of the time window in which the client administration can import an update for the client. The time window must not extend beyond midnight. |
System configuration for the application
See also: System configurations for applications
Backup / Archiving
This group includes features for data backup and archiving of the application. It contains information on backup strategies, retention periods and archiving processes.
| Property | Description |
| Available from | Specification of the date on which the data backup can be restored |
| Full backup requested | If active, a full backup of the database is created with the next CloudManager run. |
| Available until | Specification of the date on which the data backup can be restored |
| Notes | Notes on the requirements for archiving data from the application |
| Data backup provided? | Specify whether this application should be saved or not. |
| Backup storage [days] | Minimum number of days for which a full backup must be kept. |
| Can the fuse be used? | Indicates whether the currently saved backup copies are valid for the application data. If this field is active, the data backups are valid and can be restored. If this field is inactive, the data backups are NOT valid and can be deleted. Normally, a new database backup is then automatically created at the next point in time and saved externally. |
Documents
In this section you can upload, download and manage files.
SMTP configuration
This group contains configuration settings for the SMTP e-mail dispatch of the application. Parameters such as server, port, authentication and encryption for sending emails are defined here.
| Property | Description |
| SMTP server | Setting the "SMTPSERVER" configuration parameter via the CloudManager |
| SMTP Port | Set the configuration parameter "SMTPPORT" via the CloudManager. |
| Mail from Name (Display Name) | Set the configuration parameter "MAILFROMNAME" via the CloudManager. |
| Mail from address (e-mail) | Setting the "MAILFROMADDRESS" configuration parameter via the CloudManager |
| SMTP access data | Set the configuration parameter "SMTPUSER" + "SMTPPASSWORD" via the CloudManager using the stored access data. |
| SMTP SSL/TLS enabled | Set the configuration parameter "SMTPENABLESSL" via the CloudManager. |
| Exception Mails? (EXNOTIFYEMAILFLAG) | Set the configuration parameter "EXNOTIFYEMAILFLAG" via the CloudManager. |
Test position
Test position
See also: Request new client
Deregister portal (backups are removed)
Deregister portal (backups are removed)
Request full backup on next run
Request full backup on next run
