PEC-CAB/Current/CABPEGuide/Deploy - Revision history

WikiSysop at 10:31, February 23, 2023

2023-02-23T10:31:17Z

WikiSysop at 14:31, September 23, 2022

2022-09-23T14:31:17Z

WikiSysop at 17:45, May 12, 2022

2022-05-12T17:45:57Z

Corinneh: Published

2021-12-23T18:54:40Z

Published

Corinneh: Published

2021-12-22T17:10:30Z

Published

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

2021-11-09T21:15:29Z

Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

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

2021-11-09T21:12:56Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Corinne.hicks@genesys.com: Published

2021-09-21T16:44:10Z

Published

Corinne.hicks@genesys.com: Published

2021-09-10T15:51:34Z

Published

Corinne.hicks@genesys.com: Published

2021-09-09T17:27:16Z

Published

@@ Line 37: / Line 37: @@
 #*DB-USER
 #*DB-PASSWORD
-#Create the GES project/namespace.
+#Create the GES project.
 #Provision a set of GWS client credentials for GES.
 #:&nbsp;
@@ Line 316: / Line 315: @@
 |alignment=Vertical
 |structuredtext=Once GES has been installed and provisioned following the processes outlined above, the best way to validate your deployment is to check that callbacks and other provisioned services work as intended. Logging in to the UI is a good way to check that privileges are working. Also, monitor callbacks, call-ins, and other requests to ensure that they complete successfully.
 |Status=No
 }}{{Section

@@ Line 1: / Line 1: @@
-{{Article
+{{ArticlePEServiceDeploy
-|Standalone=No
+|ServiceId=58e238b9-a7f6-4af9-8050-0fe1b7cb1c39
-|DisplayName=Deploy Genesys Engagement Service
+|IncludedServiceId=ccf022d5-17e5-49dc-a6e7-e5acd1dab6fa
-|Context=Learn how to deploy Genesys Engagement Service.
+|IncludeAssumptions=Yes
 |Section={{Section
 |alignment=Vertical
-|structuredtext={{NoteFormat|Make sure to review {{Link-SomewhereInThisVersion|topic=Planning}} for the full list of prerequisites required to deploy Genesys Engagement Service.|}}
+|structuredtext=For information about downloading containers, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ManageServices|display text=Downloading your Genesys Multicloud CX containers}}.
 <!--For solution-level deployment information, see {{SuiteLevelLink|openshift}}.-->
 |Status=No
@@ Line 36: / Line 37: @@
 #*DB-USER
 #*DB-PASSWORD
-#Create the GES project/namespace:
+#Create the GES project/namespace.
 #:This will differ between environments. Be sure to check the instructions specific to the environment in {{Link-SomewhereInThisVersion|manual=CABPEGuide|topic=Deploy|anchor=DeployInOpenshift|display text=Deploy in OpenShift}}.
-#Provision a set of GWS client credentials for GES. You can do this with the following <tt>curl</tt> command.
+#Provision a set of GWS client credentials for GES.
-#:
+#:&nbsp;
 #:Create the GWS key:
 #:<source lang="yml">
@@ Line 51: / Line 59: @@
      ],
      "contactCenterIds": [
-       "<YOUR CCID>"
+       "<Tenant ID>"
      ],
      "redirectURIs": [
-       "https://ges-external-ges.apps.<DOMAIN_NAME>/ges/ui/login.html",
+       "https://ges-external-ges.apps.<DOMAIN>/ges/ui/login.html",
-       "http://ges-internal-ges.apps.<DOMAIN_NAME>/ges/ui/login.html"
+       "http://ges-internal-ges.apps.<DOMAIN>/ges/ui/login.html"
      ],
      "scope": [
@@ Line 71: / Line 79: @@
      "clientType": "CONFIDENTIAL",
      "client_secret": "<YOUR CLIENT SECRET>",  # NOTE: This is your unencrypted GWS client secret.Encrypted it will be your AUTHENTICATION-CLIENT-SECRET
-     "name": "ges_client",                       # It is possible to change this name
+     "name": "ges_client",                       # It is possible to change this name.
      "client_id": "ges_client"                   # It is possible to change this name. This is what is stored in AUTHENTICATION-CLIENT-ID
+   }
@@ Line 90: / Line 98: @@
 kubectl create secret generic ges-secrets-infra --from-literal=DB-USER=<db_username> --from-literal=DB-PASSWORD=<db_password> -- from-literal=REDIS_CACHEKEY=<redis_ges_password>
 </source>
-#*Create an ORS Redis secret. This secret contains connection details for the Redis ORS stream. This has the servername (Redis Voice Cluster Hostname - redis-ors-stream), port (Redis Voice Cluster Port), and password (Redis Voice Cluster Password – if used). Execute the following command:
+#*Create an ORS Redis secret. This secret contains connection details for the Redis ORS stream. This has the servername (Redis Voice Cluster Hostname – redis-ors-stream), port (Redis Voice Cluster Port), and password (Redis Voice Cluster Password – if used). Execute the following command:
 #*:<source lang="yml">
 kubectl create secret generic voice-redis-ors-stream --from-literal=voice-redis-ors-stream='{"password":"<Redis_Cluster_Password>", "port":"<Redis_Cluster_Port>", "rejectUnauthorized":"true", "servername":"<Redis_Hostname>"}'
@@ Line 105: / Line 113: @@
 </source>
 #Using information in the {{Link-SomewhereInThisVersion|manual=CABPEGuide|topic=Configure|anchor=OverrideHelmValues|display text=Override Helm chart values}} section, create a Helm values file that describes the details of your GES deployment, secrets, and environment. A base Helm '''values.yaml''' file is included with the GES Helm charts that you receive from Genesys. The GES base file uses the filename, '''ges-base-values.yaml'''.
-#:Be sure to specify the following values in your '''ges-values.yaml''' file for your GES deployment:
+#:Be sure to specify the following values in the '''ges-values.yaml''' overrides file for your GES deployment:
 #*<tt><Region DataCenter ID></tt>: Specify the data center region (Consul).
-#*<tt><GES Redis URL></tt>: Specify the address for the GES Redis server (non-cluster).
+#*<tt><GES Redis URL></tt>: Specify the address for the GES Redis server.<!--({{Editgrn_open}}the same value sets the location for both clustered and non-clustered Redis{{Editgrn_close}}). <font color="#B24DE7">'''Corinne's Note:''' This used to say only "non-cluster". I asked Rocky if it would change for clustered Redis and he said 'no'. Is my new text ok? I'm hiding this text for now because Rocky discovered that the new environment variable to enable clustered Redis is missing in the Helm chart. Waiting for a new release so the Helm chart can be updated.</font>-->
 #*<tt><GES Redis Port></tt>: Specify the port for the GES Redis server.
 #*<tt><postgres server address></tt>: Specify the address for the GES Postgres server.
 #*<tt><GES DB Name></tt>: Specify the database name for GES Redis.
-#*<tt><Internal gauth Auth URL></tt>: Specify the internal cluster address for the gauth authentication server.
+#*<tt><Internal gauth Authentication URL></tt>: Specify the internal cluster address for the gauth Authentication server.
-#*<tt><Internal gauth Environment URL></tt>: Specify the internal cluster address for the gauth environment server.
+#*<tt><Internal gauth Environment URL></tt>: Specify the internal cluster address for the gauth Environment server.
 #*<tt><Internal GWS URL></tt>: Specify the internal address for the GWS Service.
 #*<tt><External gauth Auth URL></tt>: Specify the external gauth address.
@@ Line 352: / Line 360: @@
 |Status=No
 }}
 |PEPageType=45d1441f-dc69-4a17-bd47-af5d811ce167
 }}

@@ Line 99: / Line 99: @@
 </source>
 #:For more information about how GES leverages secrets and how they can be provisioned, see {{Link-SomewhereInThisVersion|manual=CABPEGuide|topic=Configure|anchor=secrets|display text=secrets}} and {{Link-SomewhereInThisVersion|manual=CABPEGuide|topic=Configure|anchor=UsingSecretsForIntegration|display text=Using secrets to integrate with other software}}.
-#Download the required Helm chart release from the JFrog repository. For information about how to download the Helm charts, see [[Draft:PrivateEdition/Current/PEGuide/ManageServices|Downloading your Genesys Multicloud CX containers]]. See [[Draft:ReleaseNotes/Current/GenesysEngage-cloud/CallbackHelm|Helm charts and containers for Callback]] for the Helm chart version you must download for your release.
+#Download the required Helm chart release from the JFrog repository. For information about how to download the Helm charts, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ManageServices}}. See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=CallbackHelm}} for the Helm chart version you must download for your release.
 #Install the GES Helm charts:
 #:<source lang="yml">

@@ Line 7: / Line 7: @@
 |alignment=Vertical
 |structuredtext={{NoteFormat|Make sure to review {{Link-SomewhereInThisVersion|topic=Planning}} for the full list of prerequisites required to deploy Genesys Engagement Service.|}}
+<!--For solution-level deployment information, see {{SuiteLevelLink|openshift}}.-->
 |Status=No
 }}{{Section

@@ Line 1: / Line 1: @@
 {{Article
 |Standalone=No
-|DisplayName=Deploy Genesys Multicloud CXment Service
+|DisplayName=Deploy Genesys Engagement Service
-|Context=Learn how to deploy Genesys Multicloud CXment Service.
+|Context=Learn how to deploy Genesys Engagement Service.
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
-|structuredtext={{NoteFormat|Make sure to review {{Link-SomewhereInThisVersion|topic=Planning}} for the full list of prerequisites required to deploy Genesys Multicloud CXment Service.|}}
+|structuredtext={{NoteFormat|Make sure to review {{Link-SomewhereInThisVersion|topic=Planning}} for the full list of prerequisites required to deploy Genesys Engagement Service.|}}
 For solution-level deployment information, see {{SuiteLevelLink|openshift}}.
@@ Line 14: / Line 14: @@
 |anchor=DeployService
 |alignment=Vertical
-|structuredtext=#Because Genesys Multicloud CXment Service (GES) relies on other services, you must ensure that the following have been deployed and configured successfully before you deploy GES:
+|structuredtext=#Because Genesys Engagement Service (GES) relies on other services, you must ensure that the following have been deployed and configured successfully before you deploy GES:
 #*Voice Microservices
 #*Designer

@@ Line 45: / Line 45: @@
 |structuredtext=#Create the GES Namespace/Project:
 #:[[File:ges_pe_deploy_in_openshift_create_namespace.png]]
 #Switch to the GES project:
 #:[[File:ges_pe_deploy_in_openshift_switch_to_gesproject.png]]