DX applications
Review a list of all DX applications and resource definitions that constitute the application runtime and are deployed to containers by using Helm on OpenShift or Kubernetes platforms. As outlined in the overview, applications can also include ConfigMaps, Secrets, and Ingress.
For more information about Helm applications, consult the Helm documentation. Refer to the DX 9.5 Container component image listing in the DX 9.5 Docker Image file listing topic.
Note that each application definition lists its next direct dependencies only. Sub-dependencies are not explicitly listed.
DX 9.5 core
Depends on: No dependencies
Type: Stateful
HCL DX 9.5 CF196 and later core contains the primary portal and Web Content Manager HCL Digital Experience functionality. The standard deployment deploys at least one pod of the core. If you have an existing on-premises installation of DX 9.5 core, you can also use that installation for your deployment by using the hybrid deployment pattern as described in the DX 9.5 Hybrid deployment topic.
Note
Applying the hybrid deployment pattern is not supported with Helm in HCL DX 9.5 Container Update CF196.
Ring API
Depends on: Core (deployed to OpenShift, Kubernetes or Hybrid on-premise)
Type: Stateless
The Ring API, a component of the HCL DX Experience API HCL DX Experience API, is a REST API wrapping Core functionality. It provides API endpoints and requires that a DX Core 9.5 instance is deployed and started. That instance can either be running in the Kubernetes or OpenShift deployment or be an existing external on-premises DX-Core installation using the hybrid pattern.
Content Composer
Depends on: Ring API
Type: Stateless
Content Composer HCL Content Composer requires the Ring API to be deployed to provide content-authoring capabilities.
Digital Asset Management
Depends on: Ring API, Image Processor, Persistence
Type: Stateful
Digital Asset Management requires the Ring API be deployed and working to communicate with the DX Core, image processor components to perform image manipulation, and persistence to store its application data. See Digital Asset Management.
Persistence
Depends on: No dependencies
Type: Stateful
Persistence is used by the Digital Asset Management component to store application data. It consists of a read/write primary node and at least one standby read-only node.
The Runtime Controller automatically switches between the read/write primary and the read-only nodes.
Image Processor
Depends on: No dependencies
Type: Stateless
The Image Processor provides image manipulation capabilities that Digital Asset Management uses.
Runtime Controller
Depends on: No dependencies
Type: Stateless
The Runtime Controller incorporates runtime management functions for the entire hcl-dx-deployment HCL DX 9.5 Container. It enables automated rollout of configuration changes during runtime and monitors for the automated read/write to read-only fallback of Persistence.
Interdependency Matrix
This matrix shows which HCL DX applications have dependencies on other applications. The matrix also shows sub-dependencies. For example, if an application uses Ring API, it also depends on an operational DX 9.5 Core instance.
Application names are defined as follows:
| Short name | Full Name |
|---|---|
| Core | HCL DX 9.5 Core |
| Ring API | Ring API |
| CC | Content Composer |
| DAM | Digital Asset Management |
| PER | Persistence |
| IMG | Image Processor |