Merge pull request #7 from HCL-TECH-SOFTWARE/sync/cf226

Sync/cf226

Author: biancaluna

docs/deploy_dx/install/.pages

@@ -1,3 +1,4 @@
 nav:
   - index.md
   - Kubernetes Deployment: kubernetes_deployment
+  - Docker Compose: docker_compose.md

docs/deploy_dx/install/docker_compose.md

@@ -0,0 +1,14 @@
+
+# Docker Compose for HCL DX Compose
+
+Developers with entitlements to HCL Digital Experience (DX) Compose 9.5 can additionally deploy for non-production purposes using [Docker Compose](https://docs.docker.com/compose/){target="_blank"}. This approach streamlines deployment and configuration of HCL DX Compose 9.5 components. For more information about Docker Compose, see the [Docker Compose documentation](https://docs.docker.com/compose/){target="_blank"}.  
+
+## Deploying using Docker Compose
+
+To deploy HCL DX Compose 9.5 using Docker Compose, refer to the following steps:
+
+1. Download the Docker images for the HCL DX Compose 9.5 version you want to deploy. See [Download software](../../getting_started/download/index.md) for more information.
+
+2. Find the HCL DX Compose 9.5 Docker Compose scripts, along with installation and configuration instructions for non-production use, which are published as-is in Github.com in the [DX Compose Docker Compose](https://github.com/HCL-TECH-SOFTWARE/dx-compose-docker-compose){target="_blank"} repository.
+
+    You can find further instructions about how to use the DX Docker Compose scripts in the same repository.

docs/deploy_dx/install/kubernetes_deployment/image_list.md

@@ -13,6 +13,44 @@ In future continuous delivery updates, entitled customers can obtain the HCL DX
 
 Video: [How to upload HCL Digital Experience 9.5 container images to a private repository](https://youtu.be/XJONRdpgCuo)
 
+## HCL DX 9.5 Compose CF226
+
+If you are deploying the HCL DX 9.5 Compose CF226 release, the following software packages are available in your [HCL Software License Portal (Flexnet)](https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0073344){target="blank"} HCL Digital Experience Compose v9.5 entitlements:
+
+- HCL Digital Experience Compose v9.5
+- HCL DXClient
+- HCL Leap 9.3.x for use with DX Compose
+- HCL Volt Foundry 9.5.x for use with DX Compose
+
+## hcl-compose-kubernetes-CF226.zip
+
+```shell
+HCL DX Compose notices CF226.txt
+hcl-dx-content-composer-image-v1.39.0_20250314-1444.tar.gz
+hcl-dx-dam-plugin-google-vision-image-v1.0.0_20250314-1450.tar.gz
+hcl-dx-dam-plugin-kaltura-image-v1.0.0_20250314-1454.tar.gz
+hcl-dx-deployment-v2.35.0_20250317-1617.tgz
+hcl-dx-digital-asset-manager-image-v1.38.0_20250314-1509.tar.gz
+hcl-dx-file-processor-image-v2.0.0_20250314-1508.tar.gz
+hcl-dx-haproxy-image-v1.22.0_20250314-1521.tar.gz
+hcl-dx-image-processor-image-v1.39.0_20250314-1520.tar.gz
+hcl-dx-license-manager-image-v95_CF226_20250317-1342.tar.gz
+hcl-dx-logging-sidecar-image-v1.0.0_20250314-1500.tar.gz
+hcl-dx-openldap-image-v2.6.8_20250314-1500.tar.gz
+hcl-dx-opensearch-image-v2.0.0_20250314-1501.tar.gz
+hcl-dx-people-service-image-v1.0.0_20250314-1504.tar.gz
+hcl-dx-persistence-connection-pool-image-v1.36.0_20250314-1519.tar.gz
+hcl-dx-persistence-metrics-exporter-image-v1.34.0_20250314-1519.tar.gz
+hcl-dx-persistence-node-image-v1.26_20250314-1528.tar.gz
+hcl-dx-prereqs-checker-image-v1.0.0_20250314-1502.tar.gz
+hcl-dx-ringapi-image-v1.39.0_20250314-1513.tar.gz
+hcl-dx-runtime-controller-image-v95_CF226_20250314-1505.tar.gz
+hcl-dx-search-middleware-image-v2.0.0_20250314-1455.tar.gz
+hcl-dx-search-v2.24.0_20250317-1645.tgz
+hcl-dx-webengine-image-CF226_20250314-1843.tar.gz
+```
+
+<!--
 ## HCL DX 9.5 Compose CF225
 
 If you are deploying the HCL DX 9.5 Compose CF225 release, the following software packages are available in your [HCL Software License Portal (Flexnet)](https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0073344){target="blank"} HCL Digital Experience Compose v9.5 entitlements:

docs/deploy_dx/install/kubernetes_deployment/kubernetes_runtime.md

@@ -37,6 +37,7 @@ Review your chosen Kubernetes platform and ensure that it supports the following
 
 |CF Level|Kubernetes versions|
 |--------------|-----------------|
+|CF226| Kubernetes 1.32<br/>Kubernetes 1.31<br/>Kubernetes 1.30<br/>Kubernetes 1.29<br/>Kubernetes 1.28<br/>Kubernetes 1.27<br/>Kubernetes 1.26<br/>|
 |CF225| Kubernetes 1.32<br/>Kubernetes 1.31<br/>Kubernetes 1.30<br/>Kubernetes 1.29<br/>Kubernetes 1.28<br/>Kubernetes 1.27<br/>Kubernetes 1.26<br/>|
 |CF224| Kubernetes 1.31<br/>Kubernetes 1.30<br/>Kubernetes 1.29<br/>Kubernetes 1.28<br/>Kubernetes 1.27<br/>Kubernetes 1.26<br/>|
 

docs/deploy_dx/install/kubernetes_deployment/preparation/optional_tasks/optional_imagepullsecrets.md

@@ -27,14 +27,13 @@ images:
 
 All pods created now have that secret configured for pulling DX Compose container images.
 
-<!--
 ## Configuring deployment to use the HCL Harbor container registry
 
-It is possible to pull images directly from the HCL Harbor container registry. This requires every cluster node to be able to access the HCL Harbor container registry.
+You can pull images directly from the HCL Harbor container registry. This requires every cluster node to be able to access the HCL Harbor container registry.
 
-If you want to leverage this feature, you will have to configure an ImagePullSecret with your HCL Harbor credentials.
+If you want to use this feature, you must configure an ImagePullSecret with your HCL Harbor credentials.
 
-To do so, use the following command targeting your the Kubernetes namespace for your deployment:
+Use the following command targeting your the Kubernetes namespace for your deployment:
 
 ```sh
 # E-Mail and username are your harbor login, the password is your harbor CLI secret
@@ -44,24 +43,23 @@ kubectl create secret -n <YOUR-NAMESPACE> docker-registry dx-harbor --docker-ser
 --docker-password='<YOUR_HARBOR_CLI_SECRET>'
 ```
 
-You can obtain the CLI secret from harbor by navigating to your `User Profile` in [HCL Harbor](https://hclcr.io){target="_blank"}. You can copy it from the field called `CLI secret`.
+You can obtain the CLI secret from Harbor by navigating to your `User Profile` in [HCL Harbor](https://hclcr.io){target="_blank"}. You can copy it from the field called `CLI secret`.
 
 After executing this command you should receive the following message:
 
 ```text
-secret/dx-harbor created
+secret/dx-compose-harbor created
 ```
 
-Inside your `custom-values.yaml` you can now adjust the ImagePullSecret to the secret that was just created and point to the HCL Harbor container registry.
+Inside your `custom-values.yaml` you can now adjust the `ImagePullSecret` to the secret that was just created and point to the HCL Harbor container registry.
 
 ```yaml
 # Image related configuration
 images:
   repository: "hclcr.io"  
   # Image pull secrets used for accessing the repository
   imagePullSecrets:
-    - name: "dx-harbor"
+    - name: "dx-compose-harbor"
 ```
 
-Your deployment can now directly pull the container images from the HCL Harbor container registry.
--->
+Your deployment can now directly pull the container images from the HCL Harbor container registry.

docs/deploy_dx/manage/cfg_dx_compose/enable_people_service.md

@@ -1,6 +1,6 @@
 # Enabling and disabling People Service
 
-This document outlines configurations to enable and disable People Service in HCL Digital Experience (DX) Compose using the `values.yaml` file. People Service provides a layer for social connectivity by helping team members to connect, especially in large projects. It enhances user profiles with additional data and interactive features, improving team collaboration and project execution.
+This document outlines configurations to enable and disable [People Service](https://help.hcl-software.com/digital-experience/9.5/latest/extend_dx/integration/people_service/){target="_blank"} in HCL Digital Experience (DX) Compose using the `values.yaml` file. People Service provides a layer for social connectivity by helping team members to connect, especially in large projects. It enhances user profiles with additional data and interactive features, improving team collaboration and project execution.
 
 !!!note
     In this release, instructions for using this feature is located in the [HCL Digital Experience Help Center](https://help.hcl-software.com/digital-experience/9.5/latest/extend_dx/integration/people_service/){target="_blank"}. These will be documented in the HCL Digital Experience Compose Help Center in future releases.
@@ -28,3 +28,11 @@ Access People Service by using the following sample URL:
 ```link
 https://your-portal.net/dx/ui/people
 ```
+
+## People Service with Search V2
+
+You can integrate People Service with [Search V2](https://help.hcl-software.com/digital-experience/9.5/latest/build_sites/search_v2/){target="_blank"} to enhance user discoverability and search performance. This integration provides efficient access to user profile data with real-time synchronization.
+
+You can enable the Search V2 integration through the parameter `configuration.search.middleware.enabled` in the People Service Helm chart.
+
+For more information on how to integrate People Service with Search V2, refer to the [People Service and Search V2 integration](https://help.hcl-software.com/digital-experience/9.5/latest/extend_dx/integration/people_service/integration/people_service_search_v2_integration/){target="_blank"} topic.

docs/deploy_dx/manage/cfg_dx_compose/enable_search.md

@@ -1,6 +1,6 @@
-# Enabling and disabling Search V2
+# Enabling Search V2
 
-This document outlines configurations to enable and disable Search V2 in HCL Digital Experience (DX) Compose using the `values.yaml` file. Search introduces a new user interface along with a new backend service that utilizes OpenSearch to provide a seamless search experience.
+[Search V2](https://help.hcl-software.com/digital-experience/9.5/latest/build_sites/search_v2/){target="_blank"} introduces a new user interface with a backend service that utilizes OpenSearch to provide a seamless search experience. Search V2 is enabled by default for HCL Digital Experience (DX) Compose when the parameter `configuration.searchMiddleware.enabled` is set to `true` in the HCL DX Deployment Helm chart.
 
 ## Search configuration
 
@@ -9,31 +9,33 @@ Refer to the following sample snippet for configuring the DX Compose server to e
 ```yaml
 # Application configuration
 configuration:
-  # Application specific configuration for Core
-  webEngine:
-    # Settings for SearchV2 UI configuration
-    search:
-      # Determines if search ui v2 is enabled or not
-      uiV2Enabled: true
-      # Determines to which search center any input box on DX redirects by default
-      inputRedirectVersion: "v2"
+  # Search Middleware configuration
+  searchMiddleware:
+    # Enable/Disable Search Middleware
+    enabled: true
 ```
 
-Set the value of the key `uiV2Enabled` to `true` to enable or `false` to disable Search V2.
-Set the value of the key `inputRedirectVersion` to `v2` to redirect all searches on DX to the new Search V2 UI.
-
-
 ## Validation
 
-After updating the `values.yaml` file, perform the following actions:
+After updating the `values.yaml file`, perform the following actions:
 
 - If running the server for the first time, refer to [Installing WebEngine](../../install/kubernetes_deployment/install.md).
 - If upgrading previous configurations, refer to [Upgrading the Helm deployment](../working_with_compose/helm_upgrade_values.md).
 
+## Access
+
 Access the HCL Search V2 by navigating to **Practitioner Studio > Web Content > Search**.
 
 You can also use the following sample URL: 
 
 ```
 https://your-portal.net/wps/myportal/Practitioner/SearchCenter
-```
+```
+
+## Search V2 integration
+
+You can enable the following application to use as additional data source for Search V2:
+
+- [People Service](https://help.hcl-software.com/digital-experience/9.5/latest/extend_dx/integration/people_service/){target="_blank"}
+
+    For more information on how to integrate People Service with Search V2, refer to the [People Service and Search V2 integration](https://help.hcl-software.com/digital-experience/9.5/latest/extend_dx/integration/people_service/integration/people_service_search_v2_integration/){target="_blank"} topic.

docs/deploy_dx/manage/cfg_dx_compose/index.md

@@ -12,7 +12,7 @@ Learn how to enable and disable artificial intelligence (AI) analysis for Web Co
 Learn how to integrate WAB with DX Compose.
 -   **[Enabling and disabling People Service](enable_people_service.md)**  
 Learn how to enable and disable People Service.
--   **[Enabling and disabling Search V2](enable_search.md)**  
+-   **[Enabling Search V2](enable_search.md)**  
 Learn how to enable and disable Search V2.
 -   **[Integrating Digital Data Connector (DDC) in DX Compose](./integrate_ddc/index.md)**  
 Learn how to integrate DDC in DX Compose.

docs/deploy_dx/manage/cfg_webengine/webengine_directory_structure.md

@@ -68,6 +68,7 @@ Database properties are stored in the following directory:
 ```
 
 ### Custom secrets
+
 Custom secrets are stored in subfolders under the following directory:
 
 ```
@@ -76,6 +77,16 @@ Custom secrets are stored in subfolders under the following directory:
 
 For more details, refer to [Using custom secrets in WebEngine](../working_with_compose/custom_secrets.md).
 
+### Custom certificates
+
+Custom certificates are stored in subfolders under the following directory:
+
+```
+/mnt/certs
+```
+
+For more details, refer to [Using custom Certificates in WebEngine](../working_with_compose/custom_certificates.md).
+
 ## Sidecar container for logs
 
 ### SystemOut log

docs/deploy_dx/manage/working_with_compose/.pages

@@ -10,4 +10,5 @@ nav:
  - Troubleshooting: troubleshooting
  - Upgrading the Helm deployment: helm_upgrade_values.md
  - Using custom secrets in WebEngine: custom_secrets.md
+ - Using custom certificates in WebEngine: custom_certificates.md
  - Viewing WebEngine server logs: logging_webengine.md