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

WikiSysop at 13:31, March 10, 2023

2023-03-10T13:31:49Z

WikiSysop at 16:46, September 2, 2022

2022-09-02T16:46:42Z

WikiSysop at 16:16, September 2, 2022

2022-09-02T16:16:49Z

WikiSysop at 19:53, March 30, 2022

2022-03-30T19:53:37Z

Jdruker: Published

2022-02-11T20:57:22Z

Published

Jdruker: Republishing to refresh third-party data

2022-02-07T16:14:09Z

Republishing to refresh third-party data

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

2021-11-09T21:12:55Z

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

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

2021-11-09T20:28:35Z

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

Jose.druker@genesys.com: Published

2021-07-01T03:02:18Z

Published

New page

{{PEPrerequisites
|DisplayName=Before you begin GIM deployment
|Context=Find out what to do before deploying GIM.
|LimitationsStatus=No
|HelmStatus=No
|HelmText=GIM and GIM monitoring are the only services that run in the GIM Docker container. The Helm charts included with the GIM release provision GIM and any Kubernetes infrastructure necessary for GIM to run.

See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart version you must download for your release.

For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
|ThirdPartyStatus=No
|ThirdPartyText=For information about setting up your Genesys Engage cloud private edition platform, see {{SuiteLevelLink|softwarereq}}.

The following table lists the third-party prerequisites for GIM.
|SectionThirdPartyItem={{SectionThirdPartyItem
|ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
|Notes=You must create the Info Mart ETL database (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateDB|display text=below}}).
}}{{SectionThirdPartyItem
|ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
}}{{SectionThirdPartyItem
|ThirdPartyItem=2afd763e-337c-47eb-8428-3bafcc89dbca
}}{{SectionThirdPartyItem
|ThirdPartyItem=0d238336-2626-4954-8be3-2f1e16fdd0ce
}}{{SectionThirdPartyItem
|ThirdPartyItem=3aee73ed-68e0-4c70-8693-2421c68b86cd
}}
|StorageStatus=No
|StorageText={{Notices|Notice=PEComingSoon}}
|NetworkStatus=No
|NetworkText={{Notices|Notice=PEComingSoon}}
|BrowserStatus=No
|DependenciesStatus=No
|DependenciesText=The following Genesys Engage microservices must be deployed before you deploy GCA:

*GIM Stream Processor (GSP)
*GIM Config Adapter (GCA)

For detailed information about the correct order of services deployment, see {{SuiteLevelLink|deployorder}}.
|GDPRStatus=No
|GDPRText={{Notices|Notice=PEComingSoon}}
|Section={{Section
|sectionHeading=Create the Info Mart database
|anchor=CreateDB
|alignment=Vertical
|structuredtext=Use any database management tool to create the Info Mart ETL database and user.

For example, using the pgadmin tool in postgres:
|Status=No
}}{{Section
|alignment=Horizontal
|Media=Image
|image=GIMPEPrereq_CreateDB.png
|AltText=The Create Database screen in the database management UI.
|structuredtext=Create the database.
|Status=No
}}{{Section
|alignment=Horizontal
|Media=Image
|image=GIMPEPrereq_CreateDBUser.png
|AltText=The Create User screen in the database management UI.
|structuredtext=Create a user and grant full permissions to the user for that database.
|Status=No
}}
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
}}

@@ Line 7: / Line 7: @@
 |LimitationsText=Instructions are provided for a single-tenant deployment.
 |HelmStatus=No
-|HelmText=GIM and GIM monitoring are the only services that run in the GIM Docker container. The Helm charts included with the GIM release provision GIM and any Kubernetes infrastructure necessary for GIM to run.
+|HelmText=To configure and deploy Genesys Info Mart, you must obtain the Helm charts included with the Info Mart release. These Helm charts provision Info Mart plus any Kubernetes infrastructure Info Mart requires to run.
-See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart version you must download for your release.
+Genesys Info Mart and GIM monitoring are the only services that run in the Info Mart container.
-For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
+For the correct Helm chart version for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}}. For information on downloading from the image repository, see {{SuiteLevelLink|helmchart}}.
 |ThirdPartyStatus=No
 |ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}.
@@ Line 18: / Line 18: @@
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
-|Notes=You must create the Info Mart database (see [[{{FULLPAGENAME}}#CreateDB|below]]).
+|Notes=You must create the Info Mart database (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateGIMDB}}).
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
-|Notes=The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=Kafka|display text=Kafka configuration}}.
+|Notes=The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_KafkaTopics|display text=GSP Kafka topics}}.
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=9ae24d71-5263-4a2e-8d1b-f65660f1cdc0
@@ Line 36: / Line 36: @@
 {{AnchorDiv|PostgreDB}}
 ===PostgreSQL — the Info Mart database===
-The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and other services usage in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
+The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and usage information about other services in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
 A sizing calculator for Genesys Multicloud CX private edition is under development. In the meantime, the interactive tool available for on-premises deployments might help you estimate the size of your Info Mart database, see ''{{Repository|GIMSize_85.xlsx|b00cf06a-61e6-4f01-82d3-c6fcbf15dee7|Genesys Info Mart 8.5 Database Size Estimator}}''.
@@ Line 42: / Line 42: @@
 Genesys recommends a minimum 3 IOPS per GB.
-For information about creating the Info Mart database, see [[{{FULLPAGENAME}}#CreateDB|Create the Info Mart database]].
+For information about creating the Info Mart database, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateGIMDB}}
-{{AnchorDiv|CreateDB}}
 ====Create the Info Mart database====
 Use any database management tool to create the Info Mart ETL database and user.
 #Create the database.
-#Create a user for the Genesys Info Mart services to use, and grant full permissions to the user for that database.
+#Create a user for all of the Genesys Info Mart services to use. Grant that user full permissions for the database.
-#:This user’s account is used by Genesys Info Mart jobs to access the Info Mart database schema.
+#:This user’s account is used by Info Mart jobs to access the Info Mart database schema.
-#:The Info Mart schema name is <tt>public</tt>.
+#:The name of the Info Mart schema name is <code>public</code>.
-#:{{NoteFormat|Make a note of the database and user details, which you use to populate database-related Helm chart override values for GIM and GCA.}}
+#:{{NoteFormat|Make a note of the database and user details. You need this information when you  configure GIM and GCA Helm chart override values.}}
 ===Object storage — Data Export packages===
-The GIM Data Export feature enables you to export data from your Info Mart database. Unless you elect to store your exported data in a local directory, your Info Mart data is exported to an object store. GIM supports export to Azure Blob Storage or S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP).
+The GIM Data Export feature enables you to export data from the GIM database so it is available for other purposes. Unless you elect to store your exported data in a local directory, GIM data is exported to an object store. GIM supports export to either Azure Blob Storage or the S3-compatible storage provided by Google Cloud Platform (GCP).
-If you want to use S3-compatible storage, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=S3|display text=Create object storage}} instructions for GSP to create the S3-compatible storage for GIM.
+If you want to use S3-compatible storage, follow the {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_Plan_CreateS3Storage}} instructions for GSP to create the S3-compatible storage for GIM.
-{{NoteFormat|GSP and GCA use object storage to store data during processing. For safety and security reasons, Genesys strongly recommends that you use a dedicated object storage account for the GIM persistent storage, and do not share the storage account created for GSP and GCA.}}
+{{NoteFormat|GSP and GCA use object storage to store data during processing. For safety and security reasons, Genesys strongly recommends that you use a dedicated object storage account for the GIM persistent storage, and do not share the storage account created for GSP and GCA. GSP and GCA can share an account, and this is the expected deployment.}}
-As another alternative, you can configure GIM to store your exported data in a local directory<!--{{Editgrn_open}} (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGIM|anchor=Options|display text=Configure GIM behavior}}){{Editgrn_close}}-->. In this case, you do not need to create the object storage.
+If you are not using obect storage, you can configure GIM to store exported data in a local directory. In this case, you do not need to create the object storage.
 |NetworkStatus=No
 |NetworkText=No special network requirements.
 |BrowserStatus=No
 |DependenciesStatus=No
-|DependenciesText=
+|DependenciesText=*You must have your Tenant ID information available.
-*You must have your Tenant ID information available.
+*There are no strict dependencies among the Genesys Info Mart services, but the logic of your particular pipeline might require them to be deployed in a particular order. Depending on the order of deployment, there might be temporary data inconsistencies until all the Genesys Info Mart services are operational. For example, GCA might try to access the Info Mart database to synchronize configuration data but if GIM has not yet been deployed, the Info Mart database will be empty.
 For detailed information about the correct order of services deployment, see {{SuiteLevelLink|deployorder}}.
 |GDPRStatus=No
-|GDPRText=GIM does not yet support GDPR compliance. For details about the Info Mart database tables and columns that potentially contain personally identifiable information (PII), see the description of the [https://docs.genesys.com/Documentation/GIM/latest/PDMPostgre/Table-CTL_GDPR_HISTORY CTL_GDPR_HISTORY table] in the Genesys Info Mart on-premises documentation.
+|GDPRText=GIM provides full support for you to comply with Right of Access ("export") or Right of Erasure ("forget") requests from consumers and employees with respect to personally identifiable information (PII) in the Info Mart database.
 |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 }}

@@ Line 7: / Line 7: @@
 |LimitationsText=Instructions are provided for a single-tenant deployment.
 |HelmStatus=No
-|HelmText=To configure and deploy Genesys Info Mart, you must obtain the Helm charts included with the Info Mart release. These Helm charts provision Info Mart plus any Kubernetes infrastructure Info Mart requires to run.
+|HelmText=GIM and GIM monitoring are the only services that run in the GIM Docker container. The Helm charts included with the GIM release provision GIM and any Kubernetes infrastructure necessary for GIM to run.
-Genesys Info Mart and GIM monitoring are the only services that run in the Info Mart container.
+See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart version you must download for your release.
-For the correct Helm chart version for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}}. For information on downloading from the Genesys JFrog image repository, see {{SuiteLevelLink|helmchart}}.
+For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
 |ThirdPartyStatus=No
 |ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}.
@@ Line 18: / Line 18: @@
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
-|Notes=You must create the Info Mart database (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateGIMDB}}).
+|Notes=You must create the Info Mart database (see [[{{FULLPAGENAME}}#CreateDB|below]]).
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
-|Notes=The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_KafkaTopics|display text=GSP Kafka topics}}.
+|Notes=The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=Kafka|display text=Kafka configuration}}.
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=9ae24d71-5263-4a2e-8d1b-f65660f1cdc0
@@ Line 36: / Line 36: @@
 {{AnchorDiv|PostgreDB}}
 ===PostgreSQL — the Info Mart database===
-The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and usage information about other services in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
+The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and other services usage in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
 A sizing calculator for Genesys Multicloud CX private edition is under development. In the meantime, the interactive tool available for on-premises deployments might help you estimate the size of your Info Mart database, see ''{{Repository|GIMSize_85.xlsx|b00cf06a-61e6-4f01-82d3-c6fcbf15dee7|Genesys Info Mart 8.5 Database Size Estimator}}''.
@@ Line 42: / Line 42: @@
 Genesys recommends a minimum 3 IOPS per GB.
-For information about creating the Info Mart database, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateGIMDB}}
+For information about creating the Info Mart database, see [[{{FULLPAGENAME}}#CreateDB|Create the Info Mart database]].
 <!--{{Editgrn_open}}<font color=red>'''Writer's note:''' Borys, if you have time now to review an additional database-related enhancement, please see the modified Dep Guide content on https://all.docs-qa.genesys.com/User:Jdruker/PE_GIMPrep_AboutGIMdatabase. Otherwise, I'll post that content for your review at a later time.</font>{{Editgrn_close}}-->
-{{AnchorDiv|CreateGIMDB}}
+{{AnchorDiv|CreateDB}}
 ====Create the Info Mart database====
 Use any database management tool to create the Info Mart ETL database and user.
 #Create the database.
-#Create a user for all of the Genesys Info Mart services to use. Grant that user full permissions for the database.
+#Create a user for the Genesys Info Mart services to use, and grant full permissions to the user for that database.
-#:This user’s account is used by Info Mart jobs to access the Info Mart database schema.
+#:This user’s account is used by Genesys Info Mart jobs to access the Info Mart database schema.
-#:The name of the Info Mart schema name is <code>public</code>.
+#:The Info Mart schema name is <tt>public</tt>.
-#:{{NoteFormat|Make a note of the database and user details. You need this information when you  configure GIM and GCA Helm chart override values.}}
+#:{{NoteFormat|Make a note of the database and user details, which you use to populate database-related Helm chart override values for GIM and GCA.}}
 ===Object storage — Data Export packages===
-The GIM Data Export feature enables you to export data from the GIM database so it is available for other purposes. Unless you elect to store your exported data in a local directory, GIM data is exported to an object store. GIM supports export to either Azure Blob Storage or the S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP).
+The GIM Data Export feature enables you to export data from your Info Mart database. Unless you elect to store your exported data in a local directory, your Info Mart data is exported to an object store. GIM supports export to Azure Blob Storage or S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP).
-If you want to use S3-compatible storage, follow the {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_Plan_CreateS3Storage}} instructions for GSP to create the S3-compatible storage for GIM.
+If you want to use S3-compatible storage, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=S3|display text=Create object storage}} instructions for GSP to create the S3-compatible storage for GIM.
-{{NoteFormat|GSP and GCA use object storage to store data during processing. For safety and security reasons, Genesys strongly recommends that you use a dedicated object storage account for the GIM persistent storage, and do not share the storage account created for GSP and GCA. GSP and GCA can share an account, and this is the expected deployment.}}
+{{NoteFormat|GSP and GCA use object storage to store data during processing. For safety and security reasons, Genesys strongly recommends that you use a dedicated object storage account for the GIM persistent storage, and do not share the storage account created for GSP and GCA.}}
-If you are not using obect storage, you can configure GIM to store exported data in a local directory. In this case, you do not need to create the object storage.
+As another alternative, you can configure GIM to store your exported data in a local directory<!--{{Editgrn_open}} (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGIM|anchor=Options|display text=Configure GIM behavior}}){{Editgrn_close}}-->. In this case, you do not need to create the object storage.
 |NetworkStatus=No
 |NetworkText=No special network requirements.
 |BrowserStatus=No
 |DependenciesStatus=No
-|DependenciesText=*You must have your Tenant ID information available.
+|DependenciesText=
-*There are no strict dependencies among the Genesys Info Mart services, but the logic of your particular pipeline might require them to be deployed in a particular order. Depending on the order of deployment, there might be temporary data inconsistencies until all the Genesys Info Mart services are operational. For example, GCA might try to access the Info Mart database to synchronize configuration data but if GIM has not yet been deployed, the Info Mart database will be empty.
+*You must have your Tenant ID information available.
 For detailed information about the correct order of services deployment, see {{SuiteLevelLink|deployorder}}.
 |GDPRStatus=No
-|GDPRText={{Editgrn_open}}GIM provides full support for you to comply with Right of Access ("export") or Right of Erasure ("forget") requests from consumers and employees with respect to personally identifiable information (PII) in the Info Mart database.
+|GDPRText=GIM does not yet support GDPR compliance. For details about the Info Mart database tables and columns that potentially contain personally identifiable information (PII), see the description of the [https://docs.genesys.com/Documentation/GIM/latest/PDMPostgre/Table-CTL_GDPR_HISTORY CTL_GDPR_HISTORY table] in the Genesys Info Mart on-premises documentation.
 |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 }}

@@ Line 7: / Line 7: @@
 |LimitationsText=Instructions are provided for a single-tenant deployment.
 |HelmStatus=No
-|HelmText=GIM and GIM monitoring are the only services that run in the GIM Docker container. The Helm charts included with the GIM release provision GIM and any Kubernetes infrastructure necessary for GIM to run.
+|HelmText=To configure and deploy Genesys Info Mart, you must obtain the Helm charts included with the Info Mart release. These Helm charts provision Info Mart plus any Kubernetes infrastructure Info Mart requires to run.
-See {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}} for the Helm chart version you must download for your release.
+Genesys Info Mart and GIM monitoring are the only services that run in the Info Mart container.
-For information about how to download the Helm charts, see {{SuiteLevelLink|helmchart}}.
+For the correct Helm chart version for your release, see {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=GIMHelm}}. For information on downloading from the Genesys JFrog image repository, see {{SuiteLevelLink|helmchart}}.
 |ThirdPartyStatus=No
 |ThirdPartyText=For information about setting up your Genesys Multicloud CX private edition platform, see {{SuiteLevelLink|softwarereq}}.
@@ Line 18: / Line 18: @@
 |SectionThirdPartyItem={{SectionThirdPartyItem
 |ThirdPartyItem=1a407778-58fe-4acd-8ca7-5af8eac31283
-|Notes=You must create the Info Mart database (see [[{{FULLPAGENAME}}#CreateDB|below]]).
+|Notes=You must create the Info Mart database (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateGIMDB}}).
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=2f69518e-33af-4c0f-adcc-a98e5427e5e0
-|Notes=The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=Kafka|display text=Kafka configuration}}.
+|Notes=The Kafka topics GIM will consume must exist in the Kafka configuration. GIM consumes the topics GSP produces. For more information, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_KafkaTopics|display text=GSP Kafka topics}}.
 }}{{SectionThirdPartyItem
 |ThirdPartyItem=9ae24d71-5263-4a2e-8d1b-f65660f1cdc0
@@ Line 36: / Line 36: @@
 {{AnchorDiv|PostgreDB}}
 ===PostgreSQL — the Info Mart database===
-The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and other services usage in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
+The Info Mart database stores data about agent and interaction activity, Outbound Contact campaigns, and usage information about other services in your contact center. A subset of tables and views created, maintained, and populated by Reporting and Analytics Aggregates (RAA) provides the aggregated data on which Genesys CX Insights (GCXI) reports are based.
 A sizing calculator for Genesys Multicloud CX private edition is under development. In the meantime, the interactive tool available for on-premises deployments might help you estimate the size of your Info Mart database, see ''{{Repository|GIMSize_85.xlsx|b00cf06a-61e6-4f01-82d3-c6fcbf15dee7|Genesys Info Mart 8.5 Database Size Estimator}}''.
@@ Line 42: / Line 42: @@
 Genesys recommends a minimum 3 IOPS per GB.
-For information about creating the Info Mart database, see [[{{FULLPAGENAME}}#CreateDB|Create the Info Mart database]].
+For information about creating the Info Mart database, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGIM|anchor=CreateGIMDB}}
 <!--{{Editgrn_open}}<font color=red>'''Writer's note:''' Borys, if you have time now to review an additional database-related enhancement, please see the modified Dep Guide content on https://all.docs-qa.genesys.com/User:Jdruker/PE_GIMPrep_AboutGIMdatabase. Otherwise, I'll post that content for your review at a later time.</font>{{Editgrn_close}}-->
-{{AnchorDiv|CreateDB}}
+{{AnchorDiv|CreateGIMDB}}
 ====Create the Info Mart database====
 Use any database management tool to create the Info Mart ETL database and user.
 #Create the database.
-#Create a user for the Genesys Info Mart services to use, and grant full permissions to the user for that database.
+#Create a user for all of the Genesys Info Mart services to use. Grant that user full permissions for the database.
-#:This user’s account is used by Genesys Info Mart jobs to access the Info Mart database schema.
+#:This user’s account is used by Info Mart jobs to access the Info Mart database schema.
-#:The Info Mart schema name is <tt>public</tt>.
+#:The name of the Info Mart schema name is <code>public</code>.
-#:{{NoteFormat|Make a note of the database and user details, which you use to populate database-related Helm chart override values for GIM and GCA.}}
+#:{{NoteFormat|Make a note of the database and user details. You need this information when you  configure GIM and GCA Helm chart override values.}}
 ===Object storage — Data Export packages===
-The GIM Data Export feature enables you to export data from your Info Mart database. Unless you elect to store your exported data in a local directory, your Info Mart data is exported to an object store. GIM supports export to Azure Blob Storage or S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP).
+The GIM Data Export feature enables you to export data from the GIM database so it is available for other purposes. Unless you elect to store your exported data in a local directory, GIM data is exported to an object store. GIM supports export to either Azure Blob Storage or the S3-compatible storage provided by OpenShift and Google Cloud Platform (GCP).
-If you want to use S3-compatible storage, follow the {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=S3|display text=Create object storage}} instructions for GSP to create the S3-compatible storage for GIM.
+If you want to use S3-compatible storage, follow the {{Link-AnywhereElse|product=PEC-REP|version=Current|manual=GIMPEGuide|topic=PlanningGSP|anchor=GSP_Plan_CreateS3Storage}} instructions for GSP to create the S3-compatible storage for GIM.
-{{NoteFormat|GSP and GCA use object storage to store data during processing. For safety and security reasons, Genesys strongly recommends that you use a dedicated object storage account for the GIM persistent storage, and do not share the storage account created for GSP and GCA.}}
+{{NoteFormat|GSP and GCA use object storage to store data during processing. For safety and security reasons, Genesys strongly recommends that you use a dedicated object storage account for the GIM persistent storage, and do not share the storage account created for GSP and GCA. GSP and GCA can share an account, and this is the expected deployment.}}
-As another alternative, you can configure GIM to store your exported data in a local directory<!--{{Editgrn_open}} (see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGIM|anchor=Options|display text=Configure GIM behavior}}){{Editgrn_close}}-->. In this case, you do not need to create the object storage.
+If you are not using obect storage, you can configure GIM to store exported data in a local directory. In this case, you do not need to create the object storage.
 |NetworkStatus=No
 |NetworkText=No special network requirements.
 |BrowserStatus=No
 |DependenciesStatus=No
-|DependenciesText=
+|DependenciesText=*You must have your Tenant ID information available.
-*You must have your Tenant ID information available.
+*There are no strict dependencies among the Genesys Info Mart services, but the logic of your particular pipeline might require them to be deployed in a particular order. Depending on the order of deployment, there might be temporary data inconsistencies until all the Genesys Info Mart services are operational. For example, GCA might try to access the Info Mart database to synchronize configuration data but if GIM has not yet been deployed, the Info Mart database will be empty.
 For detailed information about the correct order of services deployment, see {{SuiteLevelLink|deployorder}}.
 |GDPRStatus=No
-|GDPRText=GIM does not yet support GDPR compliance. For details about the Info Mart database tables and columns that potentially contain personally identifiable information (PII), see the description of the [https://docs.genesys.com/Documentation/GIM/latest/PDMPostgre/Table-CTL_GDPR_HISTORY CTL_GDPR_HISTORY table] in the Genesys Info Mart on-premises documentation.
+|GDPRText={{Editgrn_open}}GIM provides full support for you to comply with Right of Access ("export") or Right of Erasure ("forget") requests from consumers and employees with respect to personally identifiable information (PII) in the Info Mart database.
 |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167
 }}

@@ Line 2: / Line 2: @@
 |DisplayName=Before you begin GIM deployment
 |Context=Find out what to do before deploying GIM.
 |LimitationsStatus=No
 |HelmStatus=No

@@ Line 31: / Line 31: @@
 |BrowserStatus=No
 |DependenciesStatus=No
-|DependenciesText=The following Genesys Engage microservices must be deployed before you deploy GCA:
+|DependenciesText=The following Genesys Multicloud CX microservices must be deployed before you deploy GCA:
 *GIM Stream Processor (GSP)