Versions Compared

Old Version 2

changes.mady.by.user Jonas Thungren

Saved on

compared with

New Version Current

changes.mady.by.user Jenni Wallin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
Excerpt
namepe-persistent-volume-concept

Usage Engine Private Edition can be configured to use a persistent volume as illustrated in the following diagram:

pe-with-persistent-volume.drawio.svgImage Removedpe-with-persistent-volume.drawio.svgImage Added

As can be seen in the diagram above, the same persistent volume (pv) is shared across the desktop-online, platform and EC pod(s). This is achieved by referencing a single persistent volume claim (pvc).

Tip

Hint!

If you are unfamiliar with how persistent volumes work in Kubernetes, please refer to the official documentation on https://kubernetes.io/docs/concepts/storage/persistent-volumes/.

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

.

/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 preparations

https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/161481567/Common+Preparations#TLS-%5BinlineExtension%5D for information about how to do this in the preferred way.

/opt/mz/persistent/storage

This is where the

mzdb storage for your deployment is

database file gets stored when

it is

using Derby as

platform database

system database.

You are free to create whatever additional files/directories under /opt/mz/persistent that your use case may require.
If you, for for example, need to share data between the platform and EC pod(s), you can create a directory /opt/mz/persistent/data and use that to exchange information. 

Configuration

Excerpt
namepe-persistent-volume-configuration

Usage Engine Private Edition can be configured to reference an arbitrary persistent volume claim by setting the following helm values:

Code Block
languageyaml
persistence:
  enabled: true
  existingClaim: my-pvc

In this example, my-pvc is an arbitrary persistent volume claim that you have created beforehand.