Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Configure"

From Genesys Documentation
Jump to: navigation, search
Line 7: Line 7:
 
|sectionHeading=Override Helm chart values
 
|sectionHeading=Override Helm chart values
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=Container environment variables are declared in [https://git.scm.genesys.com/Genesys/raa/blob/GCXI-4695/docker/Dockerfile#L98 docker file]. Comment above each variable discovers its purpose. Please request a copy of variables fragment if you have no access.
+
|structuredtext=Before you begin, download samples of the files used in this section:{{Repository|RAA_Configuration_Files.zip||RAA_Configuration_Files.zip}}.
  
−
RAA helm chart supplied with default [https://git.scm.genesys.com/Genesys/raa/blob/GCXI-4695/helm/gcxi-raa/values.yaml values.yaml]. Each helm value supported by gcxi/raa helm chart have description in comments.  
+
*Container environment variables are declared beginning at line 98 of '''Dockerfile.html'''. See the comments accompanying each variable.
 +
*Helm values are described in '''values.yaml'''. See the comments accompanying each Helm value.
  
 
You can override values in the Helm charts to configure Private Edition for their deployment environment. For example GIM database connection parameters can be specified in own yaml file as a json line base64 encoded:
 
You can override values in the Helm charts to configure Private Edition for their deployment environment. For example GIM database connection parameters can be specified in own yaml file as a json line base64 encoded:

Revision as of 12:09, June 14, 2021

This is a draft page; it has not yet been published.

Learn how to configure Reporting and Analytics Aggregates (RAA).

Related documentation:

Override Helm chart values

Before you begin, download samples of the files used in this section:RAA_Configuration_Files.zip.

  • Container environment variables are declared beginning at line 98 of Dockerfile.html. See the comments accompanying each variable.
  • Helm values are described in values.yaml. See the comments accompanying each Helm value.

You can override values in the Helm charts to configure Private Edition for their deployment environment. For example GIM database connection parameters can be specified in own yaml file as a json line base64 encoded: 

raa:
  env:
    # echo '{"jdbc_url":"jdbc:postgresql://<host>:5432/<gim_database>", "db_username":"<user>", "db_password":"<password>"}' | base64
    GCXI_GIM_DB__JSON:|-
      eyJqZGJjX3VybCI6ImpkYmM6cG9zdGdyZXNxbDovLzxob3N0Pjo1NDMyLzxnaW1fZGF0YWJhc2U+IiwgImRiX3VzZXJuYW1lIjoiPHVzZXI+IiwgImRiX3Bhc3N3b3JkIjoiPHBhc3N3b3JkPiJ9Cg==
Parameter Description Default Valid values
service.port Designer service to be exposed. 8888 A valid port.
...

Configure Kubernetes

Document the layouts for the following so customers can create them if their Helm chart doesn't include a way to do this:
  • ConfigMaps
  • Secrets

Configure security

List security-related settings, such as how to set up credentials and certificates for third-party services.

RAA configuration in Azure discovers RAA specific configuration for Azure. Private edition expects that similar configuration files (conf.xml and custom *.ss) will be placed on a mounted config volume. Configuration of thresholds will be available via Agent Setup after https://genesys.aha.io/features/ENOPLA-2967 is done. At the moment CM could be used to add object specific thresholds.

Retrieved from "https://all.docs.genesys.com/Draft:PEC-REP/Current/RAAPEGuide/Configure (2025-06-20 09:09:35)"