Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Provision"
From Genesys Documentation
| Line 13: | Line 13: | ||
* place them on a mounted config volume | * place them on a mounted config volume | ||
* configTar variable+configDelivery container — used to supply custom configs (set in configTar) | * configTar variable+configDelivery container — used to supply custom configs (set in configTar) | ||
| − | * configDelivery container without configTar variable — used to supply default config (shipped with | + | * 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}} | ||
Revision as of 19:11, 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