Usage Engine Private Edition can be configured to use a persistent volume as illustrated in the following diagram:  Image Removed Image AddedAs can be seen in the diagram above, the same persistent volume is shared across the desktop-online, platform and EC pod(s). The following table describes what gets stored where on the persistent volume: Path within pod | Description |
|---|
/opt/mz/persistent/3pp | This is where additional 3pp jar files needed for Usage Engine are stored. | /opt/mz/persistent/jni | This is where jni files are stored. Example: SAP RFC native library will be stored here. | /opt/mz/persistent/log | This is where the desktop-online, platform and EC pod logs are stored. | Note |
|---|
Note!You will need to periodically archive EC logs manually as the log4j mechanism to help automatically archive the files does not work for these two particular logs. |
| /opt/mz/persistent/backup | This is where the backup of your configurations will be stored in zip format. | /opt/mz/persistent/keys | Disk based keystore is a deprecated feature. Please refer to the TLS preparationsfor information about how to do this in the preferred way. | /opt/mz/persistent/storage | This is where the mzdb storage for your deployment is stored when it is using Derby as platform database. |
|