Digital Asset Management persistence architecture | HCL Digital Experience
This topic describes the components of the Digital Asset Management persistence. The updated DAM persistence feature is available from HCL Digital Experience 9.5 Container Update CF198 and later.
,


persistence-node
persistence-node
provides the database functionality for HCL Digital Asset
Management. The persistence-node
is a DX Red Hat Universal Base Image (UBI)
container image installed with PostgreSQL and the Replication Manager Service.
repmgr
is an open-source tool suite for managing
replication and failover in a cluster of PostgreSQL servers. repmgr
enhances the built-in hot-standby capabilities of PostgreSQL with tools to set up
standby servers, monitor replication, and perform administrative tasks, such as
failover or manual switchover operations.
In case of PostgreSQL master server failure, the repmgr
service
switches the server role from master to standby.
The persistence-node
configurations are available in the Helm Chart
values.yaml file as
persistenceNode
.
persistence-node
under
scaling
configuration.# Scaling settings for deployed applications
scaling:
# The default amount of replicas per application
replicas:
contentComposer: 1
core: 1
designStudio: 1
digitalAssetManagement: 1
imageProcessor: 1
ringApi: 1
persistenceConnectionPool: 1
persistenceNode: 3
ambassadorIngress: 3
ambassadorRedis: 3
persistence-node
is a stateful application and it requires a
volume. The configuration must have a dynamic volume class to start the container.
The storageClassName
and storage
must be updated
according to the cloud service provider and project
requirement. # Persistent Volumes for Persistence Node
persistenceNode:
# Database PVC, one per Persistence Node
database:
storageClassName: "manual"
requests:
storage: "2Gi"
# Optional volume name to specifically map to.
volumeName:
persistence-connection-pool
The persistence-connection-pool
container runs the Pg-pool service. Pg-pool is a middleware that works
between persistence-node
and HCL Digital Asset
Management.
The service provides:
- Connection pooling
- Load balancing
persistence-connection-pool
to more than one pod. The
persistence-connection-pool
configurations are available in
Helm Chart values.yaml file as
persistenceConnectionPool
.# Scaling settings for deployed applications
scaling:
# The default amount of replicas per application
replicas:
contentComposer: 1
core: 1
designStudio: 1
digitalAssetManagement: 1
imageProcessor: 1
ringApi: 1
persistenceConnectionPool: 1
persistenceNode: 3
ambassadorIngress: 3
ambassadorRedis: 3

.