|
Hosting Option: Corporate Cloud |
|
Required Permissions: IT Admin |
|
For the empower® Backend installation, empower® usually uses three different directories on the application server’s file system. |
|
|
The following table provides an overview of those directories and what they are used for: |
|
Directory |
Description |
Default Path |
|---|---|---|
|
Installation Directory |
This directory contains the installation files and the environment configuration (empowerenv.json). |
Path before change of name:
|
|
Configuration Directory |
This directory contains all configuration files that can be edited by a user (administrator) and status information that must not be deleted (e.g. information about the Active Directory synchronization status). (Exception: Final deinstallation) |
Path before change of name:
|
|
Temporary Data Directory |
This directory contains data produced by the empower® Backend that does not need to be stored permanently (e.g. log files or binary data cache). |
Path before change of name:
|
Important
The binary data folder should not be deleted regularly. This could have a considerable negative impact on the backend performance.
The data in this folder does not necessarily have to be included in a backup because they can be regenerated if necessary (with temporary performance impacts).
Note
When changing the company’s name to empower GmbH, the paths have also been changed.
The paths mentioned in this table have been updated for new installations after the change of name. The table also contains the formerly used paths.
Comments
0 comments
Article is closed for comments.