Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Configure"
Line 7: | Line 7: | ||
|sectionHeading=Override Helm chart values | |sectionHeading=Override Helm chart values | ||
|alignment=Vertical | |alignment=Vertical | ||
− | |structuredtext=Before you begin, download samples of the files used in this section:{{Repository|RAA_Configuration_Files.zip|| | + | |structuredtext=Before you begin, download samples of the files used in this section:{{Repository|RAA_Configuration_Files.zip|| yourtext }}. |
*Container environment variables are declared beginning at line 98 of '''Dockerfile.html'''. See the comments accompanying each variable. | *Container environment variables are declared beginning at line 98 of '''Dockerfile.html'''. See the comments accompanying each variable. |
Revision as of 12:10, June 14, 2021
Learn how to configure Reporting and Analytics Aggregates (RAA).
Override Helm chart values
Before you begin, download samples of the files used in this section:yourtext .
- 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
- ConfigMaps
- Secrets
Configure security
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.