Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Planning"

Revision as of 17:45, 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).

@@ Line 12: / Line 12: @@
 JDBC driver can be overridden by copying driver file to '''lib\jdbc_driver_<RDBMS>''' (or by making link) in a work dir. See for [https://docs.genesys.com/Documentation/RAA/9.0.0/Dep/PostInstall#JDBCDriverForRAA JDBC driver for RAA] for details.
 |HelmText===Init containers==
-RAA helm chart includes couple of explicit init containers.
+The RAA Helm chart includes two explicit init containers:
-===configDelivery init container===
+* '''configDelivery init''' -- this container delivers required XML configuration and *.SS files in the RAA working directory. Those files must be available in a GZIP archive, encoded as base64, which must be passed using the Helm install/update option '''--set-file raa.deployment.configTar=config.tar.gz.b64'''. Default '''conf.xml''' and '''user-data-map.ss''' are supplied with the Helm chart. If a GZIP archive is not specified by the '''--set-file''' option, the init container copies them into the working directory (unless they are already present). <br/> The configDelivery init container is optional, and is disabled by default; when it is disabled, you can create RAA configuration files in the mounted config volume. The configDelivery init container makes sense when access to the mounted working directory is restricted for any reason -- often for security reasons, or due to use of ephemeral storage for the configuration volume.
-configDelivery init container delivers required xml configuration and *.ss files to RAA work dir. Those files should be specified as gzip archive encoded as base64. The archive should be passed via --set-file raa.deployment.configTar=config.tar.gz.b64 option of helm install/update.
-Default conf.xml and user-data-map.ss are supplied with chart. They are copied to work dir by init container when such files are absent and archive above is not specified. The container is optional and disabled by default since RAA configuration files can be created right in mounted config volume. configDelivery init container makes sense for cloud environments mostly because access to mounted work dir can be restricted here by security reason or due to usage of ephemeral storage for config volume or by other reasons.
 A container name value should be specified to enable configDelivery container.