PEC-OU/Current/CXCPEGuide/Provision - Revision history

WikiSysop at 08:00, February 21, 2023

2023-02-21T08:00:54Z

WikiSysop at 12:01, September 29, 2022

2022-09-29T12:01:12Z

Mary.hachey@genesys.com: Published

2021-10-29T18:04:11Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Provision CX Contact
|Context=Learn how to provision CX Contact.
|ComingSoon=No
|Role=Administrator
|Section={{Section
|sectionHeading=Prerequisites
|anchor=ProvPrereq
|alignment=Vertical
|structuredtext=Before you begin to provision tenants in CX Contact, ensure the following prerequisites are met:

*Ensure CX Contact is deployed. See {{Link-SomewhereInThisVersion|manual=CXCPEGuide|topic=Deploy|display text=Deploy CX Contact}}.
*Ensure the tenant exists in the GWS environment. For example, on the local machine, enter:
*;<code>$ curl -u <user> <pass> https://<gauth-url>/environment/v3/environments</code>
*;Here's a sample output<nowiki>:</nowiki>
*;[[File:Exmpl-output_tenant-exists.png]]
*Ensure the "cxc" Helm release is deployed (during installation of CX Contact). For example:
*;[[File: cxc_namespace_Helm.png]]
|Status=No
}}{{Section
|sectionHeading=Tenant provisioning
|alignment=Vertical
|structuredtext=To provision tenants, you'll use the same Helm Charts as you used when deploying CX Contact, adding one additional overriding values YAML file. You should still use the same base override values file ('''override_values.yaml''') that you used when deploying CX Contact.

{{NoteFormat|The '''primary_host''' parameter represents the primary Configuration Server's domain name within the cluster. It's important that this parameter is configured correctly, as it must match the '''configServers.primaryAddress''' parameter in the GWS environment (see Prerequisites) to ensure the Helm Chart uses the existing environment and environment ID.|}}

#Prepare the <tt>provisioning_values.yaml</tt> file, as follows:
#;[[File:Tenant_provisioning_values_yaml.png]]
#Validate the Helm Chart and values. Enter<nowiki>:</nowiki>
#;<tt>$ helm template cxc ./cxcontact-<chart_version>.tgz -f override_values.yaml -f provisioning_values.yaml</tt>
#Upgrade the existing CX Contact Helm deployment with provisioning using the values file that you've just prepared. Enter<nowiki>:</nowiki>
#;<tt>$ helm upgrade cxc ./cxcontact-<chart_version>.tgz -f override_values.yaml -f provisioning_values.yaml</tt>
#If you encounter errors, verify the input values, YAML files syntax, and your Kubernetes context.
{{NoteFormat|As long as there are no changes to the override values, you can rerun the provisioning multiple times for the same tenant. It will not affect the CX Contact deployment or corrupt tenant's configuration.|2}}

===Validate tenant provisioning===
At the end of the installation, be sure to check the Helm Chart output. It will provide the status and other information about where to log in to the CX Contact UI. In addition to the standard CX Contact installation output you will see the following provisioning information:

[[File: tenant-validation_output.png]]

====Recommendations====
Finally, note the following recommendations:

*In addition to the above validation, you can also use the OpenShift Management Console to view the provisioning pod logs.
*Use the OpenShift Administration Console to check the statuses of Events and Pods. The Pods should be up and running.
*Log in to the CX Contact UI using the URL from the Helm Chart output above and the provisioned tenant's Administrator credentials.
*Check the CX Contact '''About''' > '''Versions''' page, which contains the health statuses of the CX Contact components. They should all be green.
*Check CX Contact '''Analytics''' page, which should show your successful log in.
*Try to create a test Contact List. If you do it right, CX Contact will display a confirmation message that you were successful.
|Status=No
}}
|PEPageType=55cef4ff-9306-4313-8fd8-377282a38478
}}

@@ Line 130: / Line 130: @@
 Finally, note the following recommendations:
 *Log in to the CX Contact UI using the URL from the Helm Chart output above and the provisioned tenant's Administrator credentials.
 *Check the CX Contact '''About''' &gt; '''Versions''' page, which contains the health statuses of the CX Contact components. They should all be green.

@@ Line 15: / Line 15: @@
 *;<code>$ curl -u <user> <pass> https://<gauth-url>/environment/v3/environments</code>
 *;Here's a sample output<nowiki>:</nowiki>
-*;[[File:Exmpl-output_tenant-exists.png]]
+*;<source>
 *Ensure the "cxc" Helm release is deployed (during installation of CX Contact). For example:
 *;[[File: cxc_namespace_Helm.png]]
@@ Line 27: / Line 62: @@
 #Prepare the <tt>provisioning_values.yaml</tt> file, as follows:
-#;[[File:Tenant_provisioning_values_yaml.png]]
+#;<source>
 #Validate the Helm Chart and values. Enter<nowiki>:</nowiki>
 #;<tt>$ helm template cxc ./cxcontact-<chart_version>.tgz -f override_values.yaml -f provisioning_values.yaml</tt>
@@ Line 36: / Line 115: @@
 ===Validate tenant provisioning===
-At the end of the installation, be sure to check the Helm Chart output. It will provide the status and other information about where to log in to the CX Contact UI. In addition to the standard CX Contact installation output you will see the following provisioning information:
+At the end of the installation, be sure to check the Helm Chart output. It will provide the status and other information about where to log in to the CX Contact UI. In addition to the standard CX Contact installation output you will see the following provisioning information:<source>
+Following tenants were provisioned:
-[[File: tenant-validation_output.png]]
+) tenant-9350e2fc-a1dd-4c65-8d40-1f75a2e080dd.voice.svc.cluster.local
 ====Recommendations====
 Finally, note the following recommendations: