Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Configure"
From Genesys Documentation
| Line 8: | Line 8: | ||
|alignment=Vertical | |alignment=Vertical | ||
|structuredtext=Before you begin, download samples of the files used in this section: {{Repository|RAAConfigurationFiles.zip|| RAA configuration files}}. | |structuredtext=Before you begin, download samples of the files used in this section: {{Repository|RAAConfigurationFiles.zip|| RAA configuration files}}. | ||
| + | |||
*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. | ||
*Helm values are described in '''values.yaml'''. See the comments accompanying each Helm value. | *Helm values are described in '''values.yaml'''. See the comments accompanying each Helm value. | ||
| Line 52: | Line 53: | ||
}}{{Section | }}{{Section | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |structuredtext= | + | |structuredtext=RAA is configured through files — '''conf.xml''' and '''custom *.ss''' -— which you must place on a mounted config volume. Download examples of these files: {{Repository|RP-RAAconfigurationinAzure-140621-0816-281.pdf||RAAconfigurationinAzure|}} |
| + | |||
| + | Configure thresholds using Agent Setup (CM?). | ||
|Status=No | |Status=No | ||
}} | }} | ||
|PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97 | |PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97 | ||
}} | }} | ||
Revision as of 12:20, 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.
- 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 is configured through files — conf.xml and custom *.ss -— which you must place on a mounted config volume. Download examples of these files: RAAconfigurationinAzure
Configure thresholds using Agent Setup (CM?).