Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Planning"
From Genesys Documentation
m (undefined (Saved using "Save and continue" button in form) (Saved using "Save and continue" button in form)) |
m (undefined (Saved using "Save and continue" button in form) (Saved using "Save and continue" button in form)) |
||
| Line 127: | Line 127: | ||
|ThirdPartyText=<div style="background-color: aliceblue; font-style: italic;">List any third-party services that are required (both common across Genesys Engage cloud private edition and specific to <service_name>).</div> | |ThirdPartyText=<div style="background-color: aliceblue; font-style: italic;">List any third-party services that are required (both common across Genesys Engage cloud private edition and specific to <service_name>).</div> | ||
|StorageText====GIM secret volume=== | |StorageText====GIM secret volume=== | ||
| − | RAA mounts as volume secret with | + | RAA mounts as a volume secret with Genesys Info Mart connections details when <code class="yml variable">raa.env.GCXI_GIM_DB__JSON</code> is not specified. |
| + | |||
| + | You can declare Genesys Info Mart database connection details as a Kubernetes secret, as follows: | ||
'''gimsecret.yaml''' | '''gimsecret.yaml''' | ||
| Line 139: | Line 141: | ||
json_credentials: eyJqZGJjX3VybCI6ImpkYmM6cG9zdGdyZXNxbDovLzxob3N0Pjo1NDMyLzxnaW1fZGF0YWJhc2U+IiwgImRiX3VzZXJuYW1lIjoiPHVzZXI+IiwgImRiX3Bhc3N3b3JkIjoiPHBhc3N3b3JkPiJ9Cg== | json_credentials: eyJqZGJjX3VybCI6ImpkYmM6cG9zdGdyZXNxbDovLzxob3N0Pjo1NDMyLzxnaW1fZGF0YWJhc2U+IiwgImRiX3VzZXJuYW1lIjoiPHVzZXI+IiwgImRiX3Bhc3N3b3JkIjoiPHBhc3N3b3JkPiJ9Cg== | ||
</source> | </source> | ||
| − | + | And reference the secret in values.yaml, as follows: | |
'''myvalues.yaml''' | '''myvalues.yaml''' | ||
| Line 151: | Line 153: | ||
jsonFile: "json_credentials" | jsonFile: "json_credentials" | ||
...</source> | ...</source> | ||
| − | CSI secret | + | Alternatively, you can mount a CSI secret using secretProviderClass, as follows: |
'''myvalues.yaml''' | '''myvalues.yaml''' | ||
| Line 165: | Line 167: | ||
===Config volume=== | ===Config volume=== | ||
| − | RAA mounts a config volume as /genesys/raa_config | + | RAA mounts a config volume folder, inside the container, as /genesys/raa_config. The folder is the RAA working directory -- at startup, RAA attempts to read the following files from /genesys/raa_config: |
* '''conf.xml''' contains configuration of application level config settings (see [https://intranet.genesys.com/display/RP/RAA+configuration+in+Azure RAA configuration in Azure] discovers the details of conf.xml) | * '''conf.xml''' contains configuration of application level config settings (see [https://intranet.genesys.com/display/RP/RAA+configuration+in+Azure RAA configuration in Azure] discovers the details of conf.xml) | ||
Revision as of 17:57, June 16, 2021
This is a draft page; it has not yet been published.
Find out what to do before deploying Reporting and Analytics Aggregates (RAA).
Related documentation: