Merge pull request #8 from HCL-TECH-SOFTWARE/sync/cf227

Sync/cf227

Author: marcvincentvista

docs/.pages

@@ -3,3 +3,4 @@ nav:
   - whats_new
   - getting_started
   - deploy_dx
+  - guide_me

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 CF227
+
+If you are deploying the HCL DX 9.5 Compose CF227 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-CF227.zip
+
+```shell
+HCL DX Compose notices CF227.txt
+hcl-dx-content-composer-image-v1.40.0_20250425-1905.tar.gz
+hcl-dx-dam-plugin-google-vision-image-v1.0.0_20250425-1907.tar.gz
+hcl-dx-dam-plugin-kaltura-image-v1.0.0_20250425-1908.tar.gz
+hcl-dx-deployment-v2.36.0_20250428-1459.tgz
+hcl-dx-digital-asset-manager-image-v1.39.0_20250425-1945.tar.gz
+hcl-dx-file-processor-image-v2.0.0_20250425-1932.tar.gz
+hcl-dx-haproxy-image-v1.23.0_20250425-1932.tar.gz
+hcl-dx-image-processor-image-v1.40.0_20250425-1933.tar.gz
+hcl-dx-license-manager-image-v95_CF227_20250425-1914.tar.gz
+hcl-dx-logging-sidecar-image-v1.0.0_20250425-1915.tar.gz
+hcl-dx-openldap-image-v2.6.8_20250425-1911.tar.gz
+hcl-dx-opensearch-image-v2.0.0_20250425-1916.tar.gz
+hcl-dx-people-service-image-v1.0.0_20250425-1910.tar.gz
+hcl-dx-persistence-connection-pool-image-v1.37.0_20250425-1931.tar.gz
+hcl-dx-persistence-metrics-exporter-image-v1.35.0_20250425-1930.tar.gz
+hcl-dx-persistence-node-image-v1.27_20250425-1926.tar.gz
+hcl-dx-prereqs-checker-image-v1.0.0_20250425-1933.tar.gz
+hcl-dx-ringapi-image-v1.40.0_20250425-1924.tar.gz
+hcl-dx-runtime-controller-image-v95_CF227_20250425-1917.tar.gz
+hcl-dx-search-middleware-image-v2.0.0_20250425-1929.tar.gz
+hcl-dx-search-v2.25.0_20250428-1459.tgz
+hcl-dx-webengine-image-CF227_20250425-2144.tar.gz
+```
+
+<!--
 ## 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:

docs/deploy_dx/install/kubernetes_deployment/preparation/mandatory_tasks/prepare_configure_networking.md

@@ -92,6 +92,16 @@ networking:
 
 This configuration is helpful for those who want to use a custom `Ingress Controller` to expose the service in a compatible way. Even then, HAProxy will still be active. The `Ingress Controller` will handle the incoming traffic and then route them to the HAProxy service.
 
+## Using annotations to control the HAProxy service behavior for different cloud providers
+
+The Helm chart allows you to add annotations to the HAProxy service to control the behavior of the service for different cloud providers. You can use this to configure the service to use a specific type of load balancer or to configure other settings specific to the cloud provider. You can add annotations in your `custom-values.yaml` as described [in the Annotations documentation](../optional_tasks/optional_labels_annotations.md#annotations).
+
+Examples for such annotations are in an non-exhaustive list. Refer to the documentation provided by your cloud provider for more information:
+
+- [Amazon Elastic Kubernetes Service - Use Service Annotations to configure Network Load Balancers](https://docs.aws.amazon.com/eks/latest/userguide/auto-configure-nlb.html){target="_blank"}
+- [Google Kubernetes Engine - LoadBalancer Service parameters](https://cloud.google.com/kubernetes-engine/docs/concepts/service-load-balancer-parameters){target="_blank"}
+- [Azure Kubernetes Service - LoadBalancer annotations](https://cloud-provider-azure.sigs.k8s.io/topics/loadbalancer/#loadbalancer-annotations){target="_blank"}
+
 ## Generate self-signed certificate
 
 **It is recommended that you use a properly signed certificate for HAProxy**. However, it is also possible to create and use a self-signed certificate, for example, for staging or testing environment.
@@ -148,10 +158,10 @@ A `Route` resource must be created manually when required as part of a deploymen
 
 #### Create the route resource manually
 
-If you want to deploy OpenShift manually using `Routes`, you need to create a .yaml file like below and any changes required can be made in that. To apply those changes in the OpenShift cluster, you can run `kubectl apply` and specify its namespace and location.
+If you want to deploy OpenShift manually using `Routes`, you need to create a `.yaml` file like below and any changes required can be made in that. To apply those changes in the OpenShift cluster, you can run `kubectl apply` and specify its namespace and location.
 For more information, refer to the [OpenShift Route Configuration](https://docs.openshift.com/container-platform/latest/networking/routes/route-configuration.html){target="blank"} documentation.
 
-In some versions of OpenShift, by default, sticky sessions for passthrough `Routes` are enabled in OpenShift using the source (IP) as identifier. To make sure traffic gets forwarded to all DX Compose HAProxy Pods even when another proxy is used in front of it, the `Route` should be annotated as shown in the example below. Please refer to the [OpenShift documentation](https://docs.openshift.com/container-platform/latest/networking/routes/route-configuration.html){target="blank"} to select the appropriate value for your deployment. 
+In some versions of OpenShift, by default, sticky sessions for passthrough `Routes` are enabled in OpenShift using the source (IP) as identifier. To make sure traffic gets forwarded to all DX Compose HAProxy Pods even when another proxy is used in front of it, the `Route` should be annotated as shown in the example below. Refer to the [OpenShift documentation](https://docs.openshift.com/container-platform/latest/networking/routes/route-configuration.html){target="blank"} to select the appropriate value for your deployment. 
 
 ```yaml
 apiVersion: "route.openshift.io/v1"

docs/deploy_dx/manage/cfg_dx_compose/.pages

@@ -7,3 +7,4 @@ nav:
   - enable_people_service.md
   - enable_search.md
   - integrate_ddc
+  - setup_cntnt_serv_pgs.md

docs/deploy_dx/manage/cfg_dx_compose/index.md

@@ -1,18 +1,20 @@
 # Configuring DX Compose
 
-<!-- add short description-->
+In this topic, you will learn how to configuring the different features and services available in HCL Digital Experience (DX) Compose.
 
--   **[Enabling and disabling Content Composer](enable_cc.md)**  
+-   **[Enabling and disabling Content Composer](./enable_cc.md)**  
 Learn how to enable and disable Content Composer.
--   **[Enabling and disabling Digital Asset Management](enable_dam.md)**  
+-   **[Enabling and disabling Digital Asset Management](./enable_dam.md)**  
 Learn how to enable and disable Digital Asset Management.
--   **[Enabling and disabling WCM Content AI Analysis](enable_content_ai.md)**  
+-   **[Enabling and disabling WCM Content AI Analysis](./enable_content_ai.md)**  
 Learn how to enable and disable artificial intelligence (AI) analysis for Web Content Management (WCM) content.
--   **[Integrating WAB with DX Compose](wab_integration.md)**  
+-   **[Integrating WAB with DX Compose](./wab_integration.md)**  
 Learn how to integrate WAB with DX Compose.
--   **[Enabling and disabling People Service](enable_people_service.md)**  
+-   **[Enabling and disabling People Service](./enable_people_service.md)**  
 Learn how to enable and disable People Service.
--   **[Enabling 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.
+-   **[Integrating Digital Data Connector in DX Compose](./integrate_ddc/index.md)**  
+Learn how to integrate DDC in DX Compose.
+-   **[Installing Content as a Service](./setup_cntnt_serv_pgs.md)**  
+Learn how to install Content as a Service (CaaS).

docs/deploy_dx/manage/cfg_dx_compose/setup_cntnt_serv_pgs.md

@@ -0,0 +1,39 @@
+# Setting up Content as a Service
+
+To be able to work with Content as a Service (CaaS) pages in HCL Digital Experience (DX) Compose, you must enable it using the steps listed in this topic. The setup for CaaS is comprised of resources that are shared across virtual portals and virtual portal scoped resources.
+
+Refer to the following steps to install and configure CaaS:
+
+1. On a Kubernetes deployment, change the directory to `/home/centos/native-kube` on the main Kubernetes node.
+
+2. Run the following command to make the CaaS theme available to DX Compose.
+
+    ```
+    helm upgrade -n dxns -f install-deploy-values.yaml -f ./install-hcl-dx-deployment/caas/install-caas.yaml dx-deployment ./install-hcl-dx-deployment
+    ```
+
+3. Run the following command to enter a bash shell on the DX Compose WebEngine pod.
+
+    ```
+    kubectl exec -it dx-deployment-web-engine-0 bash -n dxns
+    ```
+
+4. Run the following command to register the CaaS theme to all the virtual portals in DX Compose.
+
+    ```
+    /opt/openliberty/wlp/usr/svrcfg/scripts/xmlaccess/xmlaccess.sh -d /opt/openliberty/wlp/usr/servers/defaultServer -url http://localhost:9080/wps/config -in /opt/openliberty/wlp/usr/svrcfg/templates/caas/deployCaaSTheme.xml -out /tmp/deployCaaSTheme.xml.out -user "your Portal Admin userid" -password "your password"
+    ```
+
+5. Run the following command to register the CaaS Page and Portlet in each virtual portal, including the main virtual portal.
+
+    ```
+    /opt/openliberty/wlp/usr/svrcfg/scripts/xmlaccess/xmlaccess.sh -d /opt/openliberty/wlp/usr/servers/defaultServer -url http://localhost:9080/wps/config -in /opt/openliberty/wlp/usr/svrcfg/templates/caas/deployCaaSPages.xml -out /tmp/deployCaaSPages.xml.out -user "your Portal Admin userid" -password "your password"
+    ```
+
+    If you are installing the CaaS pages into a virtual portal apart from the main virtual portal, run the following command. This command includes the `VP Context` in the `url` parameter.
+
+    ```
+    /opt/openliberty/wlp/usr/svrcfg/scripts/xmlaccess/xmlaccess.sh -d /opt/openliberty/wlp/usr/servers/defaultServer -url http://localhost:9080/wps/config/"VP Context" -in /opt/openliberty/wlp/usr/svrcfg/templates/caas/deployCaaSPages.xml -out /tmp/deployCaaSPages.xml.out -user "your Portal Admin userid" -password "your password"
+    ```
+
+6. Restart your HCL DX Compose server.

docs/deploy_dx/manage/cfg_webengine/SetupDb2DatabasesManually.sql

@@ -0,0 +1,89 @@
+/****************************************************************************************************
+ * ★★★★★ IMPORTANT WARNING ★★★★★
+ * PLEASE REVIEW AND UPDATE ALL USERS, ROLES, AND PATHS ACCORDING TO YOUR ENVIRONMENT.
+ * This sample script is provided as a template. BEFORE EXECUTION, ensure that you modify the
+ * user names, role definitions, and file paths to match your specific requirements and
+ * security policies.
+ ****************************************************************************************************/
+
+-- NOTE: create a database name WPSDB & user. And update below query with your database connect user (<replace-with-user>) and password (<replace-with-user-password>)
+-- NOTE: make sure replace the <replace-with-user> and <replace-with-user-password> with your database connect user and password
+CONNECT TO WPSDB USER <replace-with-user> USING <replace-with-user-password>;
+CREATE SCHEMA release AUTHORIZATION <replace-with-user>;
+COMMIT;
+
+GRANT CONNECT, CREATETAB ON DATABASE TO GROUP WP_BASE_CONFIG_USERS;
+GRANT EXECUTE ON PACKAGE NULLID.SYSSH200 TO GROUP WP_BASE_CONFIG_USERS;
+GRANT ALTERIN, CREATEIN, DROPIN ON SCHEMA release TO GROUP WP_BASE_CONFIG_USERS;
+GRANT USE OF TABLESPACE USERSPACE1 TO GROUP WP_BASE_CONFIG_USERS;
+GRANT USAGE ON WORKLOAD SYSDEFAULTUSERWORKLOAD TO GROUP WP_BASE_CONFIG_USERS;
+
+CONNECT RESET;
+
+CONNECT TO WPSDB USER <replace-with-user> USING <replace-with-user-password>;
+CREATE SCHEMA community AUTHORIZATION <replace-with-user>;
+COMMIT;
+
+GRANT CONNECT, CREATETAB ON DATABASE TO GROUP WP_BASE_CONFIG_USERS;
+GRANT EXECUTE ON PACKAGE NULLID.SYSSH200 TO GROUP WP_BASE_CONFIG_USERS;
+GRANT ALTERIN, CREATEIN, DROPIN ON SCHEMA community TO GROUP WP_BASE_CONFIG_USERS;
+GRANT USE OF TABLESPACE USERSPACE1 TO GROUP WP_BASE_CONFIG_USERS;
+GRANT USAGE ON WORKLOAD SYSDEFAULTUSERWORKLOAD TO GROUP WP_BASE_CONFIG_USERS;
+
+CONNECT RESET;
+
+CONNECT TO WPSDB USER <replace-with-user> USING <replace-with-user-password>;
+CREATE SCHEMA customization AUTHORIZATION <replace-with-user>;
+COMMIT;
+
+GRANT CONNECT, CREATETAB ON DATABASE TO GROUP WP_BASE_CONFIG_USERS;
+GRANT EXECUTE ON PACKAGE NULLID.SYSSH200 TO GROUP WP_BASE_CONFIG_USERS;
+GRANT ALTERIN, CREATEIN, DROPIN ON SCHEMA customization TO GROUP WP_BASE_CONFIG_USERS;
+GRANT USE OF TABLESPACE USERSPACE1 TO GROUP WP_BASE_CONFIG_USERS;
+GRANT USAGE ON WORKLOAD SYSDEFAULTUSERWORKLOAD TO GROUP WP_BASE_CONFIG_USERS;
+
+CONNECT RESET;
+
+CONNECT TO WPSDB USER <replace-with-user> USING <replace-with-user-password>;
+CREATE SCHEMA jcr AUTHORIZATION <replace-with-user>;
+COMMIT;
+
+GRANT CONNECT, CREATETAB ON DATABASE TO GROUP WP_JCR_CONFIG_USERS;
+GRANT EXECUTE ON PACKAGE NULLID.SYSSH200 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT ALTERIN, CREATEIN, DROPIN ON SCHEMA jcr TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USE OF TABLESPACE USERSPACE1 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USAGE ON WORKLOAD SYSDEFAULTUSERWORKLOAD TO GROUP WP_JCR_CONFIG_USERS;
+
+
+GRANT USE OF TABLESPACE ICMLFQ32 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USE OF TABLESPACE ICMLNF32 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USE OF TABLESPACE ICMVFQ04 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USE OF TABLESPACE ICMSFQ04 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USE OF TABLESPACE CMBINV04 TO GROUP WP_JCR_CONFIG_USERS;
+GRANT USE OF TABLESPACE ICMLSUSRTSPACE4 TO GROUP WP_JCR_CONFIG_USERS;
+
+CONNECT RESET;
+
+CONNECT TO WPSDB USER <replace-with-user> USING <replace-with-user-password>;
+CREATE SCHEMA feedback AUTHORIZATION <replace-with-user>;
+COMMIT;
+
+GRANT CONNECT, CREATETAB ON DATABASE TO GROUP WP_PZN_CONFIG_USERS;
+GRANT EXECUTE ON PACKAGE NULLID.SYSSH200 TO GROUP WP_PZN_CONFIG_USERS;
+GRANT ALTERIN, CREATEIN, DROPIN ON SCHEMA feedback TO GROUP WP_PZN_CONFIG_USERS;
+GRANT USE OF TABLESPACE USERSPACE1 TO GROUP WP_PZN_CONFIG_USERS;
+GRANT USAGE ON WORKLOAD SYSDEFAULTUSERWORKLOAD TO GROUP WP_PZN_CONFIG_USERS;
+
+CONNECT RESET;
+
+CONNECT TO WPSDB USER <replace-with-user> USING <replace-with-user-password>;
+CREATE SCHEMA likeminds AUTHORIZATION <replace-with-user>;
+COMMIT;
+
+GRANT CONNECT, CREATETAB ON DATABASE TO GROUP WP_PZN_CONFIG_USERS;
+GRANT EXECUTE ON PACKAGE NULLID.SYSSH200 TO GROUP WP_PZN_CONFIG_USERS;
+GRANT ALTERIN, CREATEIN, DROPIN ON SCHEMA likeminds TO GROUP WP_PZN_CONFIG_USERS;
+GRANT USE OF TABLESPACE USERSPACE1 TO GROUP WP_PZN_CONFIG_USERS;
+GRANT USAGE ON WORKLOAD SYSDEFAULTUSERWORKLOAD TO GROUP WP_PZN_CONFIG_USERS;
+
+CONNECT RESET;