|
|
| (31 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {{Article
| + | # REDIRECT <a href="https:// all.docs.genesys.com/ Draft: PEC-REP/ Current/ GCXIPEGuide/ ConfigureRAA">go</ a> |
| − | |Standalone=No
| |
| − | |DisplayName=Configure RAA
| |
| − | |Context=Learn how to configure Reporting and Analytics Aggregates (RAA).
| |
| − | |ComingSoon=No
| |
| − | |Section={{Section
| |
| − | |sectionHeading=Override Helm chart values
| |
| − | |alignment=Vertical
| |
| − | |structuredtext=Before you begin, download samples of the files used in this section:{{Repository|RAA_Configuration_Files.zip||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:
| |
| − | <source lang="source">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==
| |
| − | </source>
| |
| − | {{{!}} class="wikitable"
| |
| − | {{!}}+
| |
| − | !Parameter
| |
| − | !Description
| |
| − | !Default
| |
| − | !Valid values
| |
| − | {{!}}-
| |
| − | {{!}}service.port
| |
| − | {{!}}Designer service to be exposed.
| |
| − | {{!}}8888
| |
| − | {{!}}A valid port.
| |
| − | {{!}}-
| |
| − | {{!}}...
| |
| − | {{!}}
| |
| − | {{!}}
| |
| − | {{!}}
| |
| − | {{!}}}
| |
| − | |Status=No
| |
| − | }}{{Section
| |
| − | |sectionHeading=Configure Kubernetes
| |
| − | |alignment=Vertical
| |
| − | |structuredtext=<div style="background-color: aliceblue; font-style: italic;">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
| |
| − | </div>
| |
| − | |Status=No
| |
| − | }}{{Section
| |
| − | |sectionHeading=Configure security
| |
| − | |alignment=Vertical
| |
| − | |structuredtext=<div style="background-color: aliceblue; font-style: italic;">List security-related settings, such as how to set up credentials and certificates for third-party services.</div>
| |
| − | |Status=No
| |
| − | }}{{Section
| |
| − | |alignment=Vertical
| |
| − | |structuredtext=[https://intranet.genesys.com/display/RP/RAA+configuration+in+Azure 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.
| |
| − | |Status=No
| |
| − | }}
| |
| − | |PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97
| |
| − | }}
| |
This is a draft page; it has not yet been published.
