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

Revision as of 18:30, 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 155: / Line 155: @@
 *    custom '''*.ss''' files (see [https://docs.genesys.com/Documentation/RAA/9.0.0/UG/CustomAgg How Do I Customize Queries and Hierarchies?] for details).
 *    JDBC driver from lib/jdbc_driver_<RDBMS> (see [https://docs.genesys.com/Documentation/RAA/9.0.0/Dep/PostInstall#JDBCDriverForRAA Procedure: Configuring the JDBC Driver for RAA] for details).
-*    '''conf.xml''' contains configuration of application level config settings, as follows
+*    '''conf.xml''' contains configuration of application level config settings, as follows:
+*:<source lang="bash"><CfgOptions>
+ <Application>
+  <i id="agg">
+   <i k="sub-hour-interval" v="30min"/>
+  </i>
+  <i id="agg-feature">
+   <i k="materialize-subhour-in-db" v="true"/>
+   <i k="enable-available-features" v="true"/>
+  </i>
+  <i id="cfgApplication">
+   <i k="CFGAPP_NAME" v="RAA" />
+  </i>
+ </Application>
+</CfgOptions></source>
- <CfgOptions>
+Usually RAA does not create any files here at runtime, so the volume does not requires a superfast storage class.
+Size limit is set to 50M by default. The storage class and size limit can be specified in values, as follows:
-  <Application>
-   <nowiki><i id="agg"></nowiki>
-    <nowiki><i k="sub-hour-interval" v="30min"/></nowiki>
-   <nowiki></i></nowiki>
-   <nowiki><i id="agg-feature"></nowiki>
-    <nowiki><i k="materialize-subhour-in-db" v="true"/></nowiki>
-    <nowiki><i k="enable-available-features" v="true"/></nowiki>
-   <nowiki></i></nowiki>
-   <nowiki><i id="cfgApplication"></nowiki>
-    <nowiki><i k="CFGAPP_NAME" v="RAA" /></nowiki>
-   <nowiki></i></nowiki>
-  </Application>
- </CfgOptions>
-Usually RAA does not create any files here at runtime so the volume does not requires a superfast storage class.
-Size limit is set to 50M by default. The storage class and size limit can be specified in values:
 '''myvalues.yaml'''
@@ Line 197: / Line 183: @@
        storageClassName: "<vendor storage class>"
      ...</source>
-RAA helm chart creates Persistent Volume Claim. It can also optionally create a Persistent Volume (when <code class="yml variable">raa.volumes.config.pv</code> is specified). See how Persistent Volume declared in helm chart:
+RAA Helm chart creates Persistent Volume Claim. It can also optionally create a Persistent Volume (when <code class="yml variable">raa.volumes.config.pv</code> is specified). The following example illustrates how Persistent Volume is declared in the Helm chart:
 '''raa-config-volume.yaml'''
@@ Line 263: / Line 249: @@
              path: "/usr/local/genesys/RAA/config/"
        ...</source>
-Alternatively Persistent Volume can be defined separately. Its name should be specified in values.yaml via <code class="yml variable">raa.volumes.config.pvc.volumeName</code> for binding to Persistent Volume Claim:
+Alternatively, you can define Persistent Volume separately. Its name must be specified in values.yaml, using the <code class="yml variable">raa.volumes.config.pvc.volumeName</code> for binding to Persistent Volume Claim:
 '''myvalues.yaml'''
@@ Line 275: / Line 261: @@
          volumeName: "my_raa_config_volume"
      ...</source>
-An ephemeral storage could be also mapped.
+Optionally, you can also map ephemeral storage.
 ===Health volume===
@@ Line 361: / Line 348: @@
              path: "/usr/local/genesys/RAA/health/"
        ...</source>
-Alternatively Persistent Volume can be defined separately. Its name should be specified in values.yaml via <code class="yml variable">raa.volumes.health.pvc.volumeName</code> for binding to Persistent Volume Claim:
+Alternatively Persistent Volume can be defined separately. Its name should be specified in values.yaml, bu the <code class="yml variable">raa.volumes.health.pvc.volumeName</code> for binding to Persistent Volume Claim:
 '''myvalues.yaml'''