PEC-REP/Current/GCXIPEGuide/Deploy - Revision history

WikiSysop at 15:01, September 20, 2022

2022-09-20T15:01:35Z

WikiSysop at 18:31, September 7, 2022

2022-09-07T18:31:27Z

WikiSysop at 18:30, April 22, 2022

2022-04-22T18:30:40Z

Show changes

WikiSysop at 18:00, April 22, 2022

2022-04-22T18:00:28Z

Show changes

WikiSysop at 17:30, April 22, 2022

2022-04-22T17:30:29Z

WikiSysop at 17:15, April 8, 2022

2022-04-08T17:15:45Z

Show changes

WikiSysop at 19:52, March 30, 2022

2022-03-30T19:52:43Z

Show changes

Tony.gilchrist@genesys.com: Published

2021-12-01T13:47:45Z

Published

Tony.gilchrist@genesys.com: Published

2021-12-01T13:36:43Z

Published

Tony.gilchrist@genesys.com: Published

2021-09-01T18:29:59Z

Published

@@ Line 196: / Line 196: @@
 ===2. Deploy GCXI===
 This procedure provides steps you can use to deploy GCXI in environments without LDAP. For environments that include LDAP or other features not supported in '''values.yaml,''' you can pass container environment variables such MSTR_WEB_LDAP_ON=true using the '''gcxi.envvars''' file, for example: <tt>--set-file gcxi.envext=gcxi.envvars</tt>.
+{{AnchorDiv|DeployGCXI}}
 #Log in to the OpenShift, GKE, or AKS cluster from the host where you will run deployment.
 #For debug purposes, run the following command to render templates without installing:
@@ Line 204: / Line 204: @@
 #To deploy GCXI, execute the following command:
 #:<source lang="bash">helm install --debug --namespace gcxi --create-namespace -f values-test.yaml gcxi-oc gcxi/</source>
 #:This process takes several minutes.  Wait until the installation routine has created and allocated all of the objects, and the Kubernetes descriptors that are applied to the environment appear.
 #To check the installed Helm release, run the following command:

@@ Line 11: / Line 11: @@
 |structuredtext=Before you begin, ensure that:
-*You are logged in to your OpenShift or GKE cluster.
+*You are logged in to your OpenShift, GKE, or AKS cluster.
 *For HA deployments, at least two worker nodes are available for GCXI pods.
 *Each Worker machine meets the following minimum requirements:
@@ Line 130: / Line 130: @@
 |sectionHeading=Install GCXI
 |alignment=Vertical
-|structuredtext=The following procedures describe example steps to deploy GCXI with OpenShift or GKE. The exact steps required vary depending on your environment.
+|structuredtext=The following procedures describe example steps to deploy GCXI with OpenShift, GKE, or AKS. The exact steps required vary depending on your environment.
 {{AnchorDiv|Preconfigure}}
 {{AnchorDiv|Prepare}}
@@ Line 192: / Line 192: @@
 </source>
 {{AnchorDiv|Deploy}}
-{{NoteFormat|{{Editgrn_open}}You can configure GCXI_GIM_DB to point to an instance in Private Edition, or to a legacy deployment on-premises (mixed-mode deployment).{{Editgrn_close}}|2}}
+<!--{{NoteFormat|You can configure GCXI_GIM_DB to point to an instance in Private Edition, or to a legacy deployment on-premises (mixed-mode deployment).|2}}-->
 ===2. Deploy GCXI===
 This procedure provides steps you can use to deploy GCXI in environments without LDAP. For environments that include LDAP or other features not supported in '''values.yaml,''' you can pass container environment variables such MSTR_WEB_LDAP_ON=true using the '''gcxi.envvars''' file, for example: <tt>--set-file gcxi.envext=gcxi.envvars</tt>.
-#Log in to OpenShift or GKE cluster from the host where you will run deployment.
+#Log in to the OpenShift, GKE, or AKS cluster from the host where you will run deployment.
 #For debug purposes, run the following command to render templates without installing:
 #:<source lang="bash">helm template --debug -f values-test.yaml gcxi-helm gcxi/

@@ Line 1: / Line 1: @@
-{{Article
+{{ArticlePEServiceDeploy
-|Standalone=No
+|ServiceId=6f7f1a8d-4e60-4b8d-a6f0-8cafdbdf0a3e
-|DisplayName=Deploy GCXI
+|IncludeAssumptions=Yes
 |Section={{Section
 |alignment=Vertical
@@ Line 30: / Line 28: @@
 !Description
 !Access Type
-!Default Mount Point on the Host (you can change this using values; these directories MUST pre-exist on your host to accommodate the local provisioner)
+!Default Mount Point on the Host (you can change this using values; ensure that the indicated directory pre-exists on your host, to accommodate the local provisioner)
 !Shared across Nodes?
 !Required Node Label (applies to default Local PVs setup)
@@ Line 194: / Line 192: @@
 </source>
 {{AnchorDiv|Deploy}}
 ===2. Deploy GCXI===

@@ Line 196: / Line 196: @@
 Verify that an assortment of report folders are present (Agents, Business Results, Callback, and so on) and that each one contains one or more reports. Note that, before you can view a report, you must run the report in order to populate data. For more information, see {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=RPRT|topic=HRCXIGetStarted|display text=Generate historical reports}}.
 |Status=No
-}}
+}}{{Section
-|PEPageType=45d1441f-dc69-4a17-bd47-af5d811ce167
+|sectionHeading=Maintenance and troubleshooting
-}}
+|alignment=Vertical
-==Maintenance Procedures==
+|structuredtext=Use the instructions in this section only if you encounter errors or other difficulties. Problems with the deployment are most often associated with the following three kinds of objects:
 *PVs
 *PVCs
 *pods
 #To list the objects that might cause problems, execute the following commands:
 #:<source lang="bash">oc get pv -o wide</source>
@@ Line 216: / Line 214: @@
 #:<source lang="bash">oc describe po gcxi-0</source>
 #In the '''describe''' output, inspect the section '''Events'''.

@@ Line 156: / Line 156: @@
        volumeName: gcxi-postgres-pv
 </source>
 {{AnchorDiv|Deploy}}
 ===3. Deploy GCXI===
@@ Line 198: / Line 188: @@
 #Verify that you can now access GCXI at the following URL:
 #:<source lang="text">http://web-gcxi.<host>/MicroStrategy/servlet/mstrWeb</source>
 ==Maintenance Procedures==
 This section provides additional procedures, such as troubleshooting steps.{{AnchorDiv|Troubleshooting}}

@@ Line 99: / Line 99: @@
 #Ensure that the GCXI project has been created.
 #Ensure that four PersistentVolumes (PV) have been created. See the table {{Link-SomewhereInThisVersion|manual=GCXIPEGuide|topic=Deploy|anchor=PVCsrequiredbyGCXI|display text=PVCs required by GCXI}}
-#Ensure that security context constraints (SCC) in OpenShift are configured appropriately to allow OpenShift Container Platform to run containers using user ID = 500. For more information, see [https://docs.openshift.com/container-platform/4.5/authentication/managing-security-context-constraints.html#security-context-constraints-about_configuring-internal-oauth About security context constraints] in the Open Shift documentation.
+#For more information, see [https://docs.openshift.com/container-platform/4.5/authentication/managing-security-context-constraints.html#security-context-constraints-about_configuring-internal-oauth About security context constraints] in the Open Shift documentation.
 #:For test and development environments, execute the following command if you wish to run pods as any user:
 #:<source lang="LANGUAGE">oc adm policy add-scc-to-user anyuid -z default</source>