PEC-REP/Current/GIMPEGuide/ConfigureGIM - Revision history

WikiSysop at 13:31, March 10, 2023

2023-03-10T13:31:31Z

WikiSysop at 03:15, September 30, 2022

2022-09-30T03:15:42Z

WikiSysop at 17:01, September 29, 2022

2022-09-29T17:01:45Z

Show changes

WikiSysop at 19:31, September 28, 2022

2022-09-28T19:31:11Z

WikiSysop at 16:46, September 2, 2022

2022-09-02T16:46:11Z

Show changes

WikiSysop at 16:16, September 2, 2022

2022-09-02T16:16:11Z

Show changes

WikiSysop at 13:00, March 31, 2022

2022-03-31T13:00:45Z

WikiSysop at 19:53, March 30, 2022

2022-03-30T19:53:07Z

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:28:57Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Jose.druker@genesys.com: Published

2021-09-15T22:30:21Z

Published

@@ Line 98: / Line 98: @@
 The <code>s3_storage</code> parameters are used to construct the '''s3_storage_secrets''' secret.
 ====GKE example====
@@ Line 127: / Line 113: @@
      entrypoint: "storage.googleapis.com"
 </source>
 |Status=No
 }}{{Section

@@ Line 12: / Line 12: @@
 Download the '''gim''' and '''gim-monitoring''' Helm charts from your image repository, using the appropriate credentials.
-To learn how to download the Helm charts, see [[Draft:PrivateEdition/Current/PEGuide/ManageServices|Downloading your Genesys Multicloud CX containers]]. To find the correct Helm chart version for your release, see [[Draft:ReleaseNotes/Current/GenesysEngage-cloud/GIMHelm|Helm charts and containers for Genesys Info Mart]] for the Helm chart version you must download for your release. For general information about Helm chart overrides, see [[Draft:PrivateEdition/Current/PEGuide/HelmOverrides|Overriding Helm chart values]] in the ''[[Draft:PrivateEdition/Current/PEGuide|Genesys Multicloud CX Private Edition Guide]]''.
+To learn how to download the Helm charts, see [[Draft:PrivateEdition/Current/PEGuide/ManageServices|Downloading your Genesys Multicloud CX containers]]. To find the correct Helm chart version for your release, see [[Draft:ReleaseNotes/Current/GenesysEngage-cloud/GIMHelm|Helm charts and containers for Genesys Info Mart]]. For general information about Helm chart overrides, see [[Draft:PrivateEdition/Current/PEGuide/HelmOverrides|Overriding Helm chart values]] in the ''[[Draft:PrivateEdition/Current/PEGuide|Genesys Multicloud CX Private Edition Guide]]''.
 At minimum, you must create entries in the '''values.yaml''' file to specify system information, as described in the following sections.
@@ Line 241: / Line 241: @@
 However, changing any of the other '''date-time''' options during runtime can introduce inconsistencies into the calendar data and affect reporting results adversely. For example, if you change the timezone option ('''date-time-tz''') after Genesys Info Mart has been initialized, your reports can mix the results for different time zones within the same reporting interval.
 <!--Writer: Update the following link or remove it:
 If you want to change calendar options during runtime, see [[Documentation:GIM:Ops:CalendarDim|Changing Calendar Dimensions]] in the ''Genesys Info Mart Operations Guide,'' which provides information about additional steps that are required to maintain reporting consistency.

@@ Line 130: / Line 130: @@
 </source>
 |Status=No
-}}<!--{{Section
+}}{{Section
 |sectionHeading=Configure GIM behavior
 |anchor=Options
 |alignment=Vertical
-|structuredtext={{Editgrn_open}}<font color=red>'''Writer's note:''' Placeholder pending Q&A. This section will be suppressed for GKE Q1 publication.</font>{{Editgrn_close}}
+|structuredtext=You can specify values in the '''values.yaml''' file to control options that override aspects of the default configuration, thereby modifying GIM behavior and customizing the way data is stored in the Info Mart database.
 |Status=No
-}}-->
+}}{{Section
 |PEPageType=9c3ae89b-4f75-495b-85f8-d8c4afcb3f97
 }}

@@ Line 52: / Line 52: @@
 {{AnchorDiv|ConfigMaps}}
 ===Config Maps===
-Helm creates a number of Config Maps based on option values you specify in the '''values.yaml''' file (see [[{{FULLPAGENAME}}#Options|Configure GIM behavior]]). There are no Config Maps you can configure directly.
+Helm creates a number of Config Maps based on option values you specify in the '''values.yaml''' file<!-- (see [[{{FULLPAGENAME}}#Options|Configure GIM behavior]])-->. There are no Config Maps you can configure directly.
 |Status=No
 }}{{Section

@@ Line 9: / Line 9: @@
 |structuredtext=Download the gim and gim-monitor Helm charts from JFrog using your credentials. You must override certain parameters in the '''values.yaml''' file to provide deployment-specific values for certain parameters.
-For general information about overriding Helm chart values, see {{SuiteLevelLink|helmoverride}} in the ''{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|display text=Genesys Engage Cloud Private Edition Guide}}''.
+For general information about overriding Helm chart values, see {{SuiteLevelLink|helmoverride}} in the ''{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|display text=Genesys Multicloud CX Private Edition Guide}}''.
 If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the GIM '''values.yaml''' file, so that no user or group IDs are specified. For details, see [[{{FULLPAGENAME}}#Security|Configure security]], below.

@@ Line 7: / Line 7: @@
 |sectionHeading=Override Helm chart values
 |alignment=Vertical
-|structuredtext=Download the gim and gim-monitor Helm charts from JFrog using your credentials. You must override certain parameters in the '''values.yaml''' file (referred to on this page as the '''gim-values.yaml''' file) to provide deployment-specific values for certain parameters.
+|structuredtext=Download the gim and gim-monitor Helm charts from JFrog using your credentials. You must override certain parameters in the '''values.yaml''' file to provide deployment-specific values for certain parameters.
 For general information about overriding Helm chart values, see {{SuiteLevelLink|helmoverride}} in the ''{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|display text=Genesys Engage Cloud Private Edition Guide}}''.
-If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the '''gim-values.yaml''' file, so that no user or group IDs are specified. For details, see [[{{FULLPAGENAME}}#Security|Configure security]], below.
+If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the GIM '''values.yaml''' file, so that no user or group IDs are specified. For details, see [[{{FULLPAGENAME}}#Security|Configure security]], below.
-At a minimum, you must override the following key entries in the '''gim-values.yaml''' file:
+At a minimum, you must override the following key entries in the GIM '''values.yaml''' file:
 *<tt>tag</tt> - the container image version
@@ Line 21: / Line 21: @@
 * <tt>bootstrap</tt> - the Kafka address to align with the infrastructure Kafka
-====The gim-values.yaml file====
+====The GIM '''values.yaml''' file====
-The following sample gim-values.yaml file, which may not be completely up to date, shows the key parameter values you must override.
+The following sample GIM '''values.yaml''' file, which may not be completely up to date, shows the key parameter values you must override.
 <source lang="bash">replicaCount: 1
 # Add tenant_id and tenant_uuid
@@ Line 88: / Line 88: @@
 |structuredtext=The security context settings define the privilege and access control settings for pods and containers.
-By default, the user and group IDs are set in the '''gim-values.yaml''' file as <tt>500:500:500</tt>, meaning the '''genesys''' user.
+By default, the user and group IDs are set in the GIM '''values.yaml''' file as <tt>500:500:500</tt>, meaning the '''genesys''' user.
 <source lang="bash">
 securityContext:
@@ Line 99: / Line 99: @@
 </source>
 ===Arbitrary UIDs in OpenShift===
-If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the '''gim-values.yaml''' file, so that you do not define any specific IDs.
+If you want to use arbitrary UIDs in your OpenShift deployment, you must override the '''securityContext''' settings in the GIM '''values.yaml''' file, so that you do not define any specific IDs.
 <source lang="bash">