Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Provision"
From Genesys Documentation
| Line 9: | Line 9: | ||
|structuredtext=An installed Genesys Info Mart database is required for RAA. | |structuredtext=An installed Genesys Info Mart database is required for RAA. | ||
| − | RAA is configured through files — '''conf.xml''' and '''custom *.ss''' -— which you | + | RAA is configured through files — '''conf.xml''' and '''custom *.ss''' -— which you can provide using any of the following methods: |
| + | |||
| + | * place them on a mounted config volume | ||
| + | * configTar variable+configDelivery container — used to supply custom configs (set in configTar) | ||
| + | * configDelivery container without configTar variable — used to supply default config (shipped with raa helm chart) | ||
Download examples of these files: {{Repository|RAAconfigurationinAzure.pdf|| RAA Provisioning}} | Download examples of these files: {{Repository|RAAconfigurationinAzure.pdf|| RAA Provisioning}} | ||
| − | Configure thresholds using Agent Setup | + | Configure thresholds using Agent Setup. |
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
Revision as of 18:53, June 23, 2021
This is a draft page; it has not yet been published.
Contents
Learn how to provision Reporting and Analytics Aggregates (RAA).
Related documentation:
An installed Genesys Info Mart database is required for RAA.
RAA is configured through files — conf.xml and custom *.ss -— which you can provide using any of the following methods:
- place them on a mounted config volume
- configTar variable+configDelivery container — used to supply custom configs (set in configTar)
- configDelivery container without configTar variable — used to supply default config (shipped with raa helm chart)
Download examples of these files: RAA Provisioning
Configure thresholds using Agent Setup.
Tenant provisioning