PE-GPR/9.0.0/Deployment/cfgAsc - Revision history

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

2021-11-09T20:29:33Z

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

Vivian.hood@genesys.com: Published

2020-12-09T14:51:57Z

Published

Vivian.hood@genesys.com: Published

2020-11-06T20:37:17Z

Published

Vivian: Published

2020-10-08T20:54:34Z

Published

Vivian: Published

2020-09-22T17:02:31Z

Published

Vivian: Published

2020-09-22T13:10:27Z

Published

Show changes

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:33:34Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:45:21Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

2020-06-09T13:39:32Z

Published

Vivian: Published

2020-05-26T15:46:20Z

Published

@@ Line 120: / Line 120: @@
 *#Enter the account information you receive when you start using Predictive Routing in the {{Optionslink|link=Options:DataLoader:default:password}} and {{Optionslink|link=Options:DataLoader:default:platform-username}} options.
 *#*After you set up the initial account access, these options are hidden and Data Loader automatically updates the password every 90 days. Log messages appear in Solution Control Interface indicating when the password is about to expire and when it has been successfully updated.
-*#*Data Loader sets passwords that comply with Genesys Engage cloud security standards.
+*#*Data Loader sets passwords that comply with Genesys Multicloud CX security standards.
 *#Configure the URL used to access the GPR Core Platform, set in the {{Optionslink|link=Options:DataLoader:default:platform-base-url}} option.
 *#Configure the API key used to access the GPR Core Platform, set in the {{Optionslink|link=Options:DataLoader:default:platform-api-key}} option. This API key is available in the {{Link-SomewhereInThisVersion|manual=Help|topic=cfgAccounts|display text='''Settings &gt; Account'''}} window of the GPR web application.

@@ Line 219: / Line 219: @@
 #*gpr belongs to the systemd-journal group (for container log checking).
 #*The Docker service is running.
-#In release 9.0.018.00 and higher, the '''install.sh''' process asks you if you would like to start Data Loader when the container starts. If you reply <tt>Y/y</tt> to the prompt, the script asks you to specify values for the following environment variables:
+#In release 9.0.018.01 and higher, the '''install.sh''' process asks you if you would like to start Data Loader when the container starts. If you reply <tt>Y/y</tt> to the prompt, the script asks you to specify values for the following environment variables:
 #*CONFIG_HOST - The host name where Configuration Server is running.
 #*CONFIG_PORT - The port number where Configuration Server is running.

@@ Line 204: / Line 204: @@
 ===Install Data Loader and Start the Container===
-*Perform the installation using the '''gpr''' user. The '''gpr''' user must have sudo rights to perform the installation.
+#Perform the installation using the '''gpr''' user. The '''gpr''' user must have sudo rights to perform the installation. '''Do NOT use the root user to install Data Loader.'''
-*Do NOT use the root user to install Data Loader.
+#Verify that you have created the Data Loader user and assigned it the SERVICE role before starting Data Loader for the first time. For instructions, see {{Link-SomewhereInThisVersion|manual=Help|topic=cfgUserMgmt|anchor=service|display text=Create the Data Loader user}} in the ''Predictive Routing Help''.
-*You should have created the Data Loader user and assigned it the SERVICE role before starting Data Loader for the first time. For instructions, see {{Link-SomewhereInThisVersion|manual=Help|topic=cfgUserMgmt|anchor=service|display text=Create the Data Loader user}} in the ''Predictive Routing Help''.
+#Execute the '''install.sh''' script, using the following command from the folder containing the Data Loader IP package:
 #:<source lang="bash">$ cd ./ai-data-loader-scripts/scripts</source>
 #:<source lang="bash">$ bash install.sh</source>
@@ Line 222: / Line 219: @@
 #*gpr belongs to the systemd-journal group (for container log checking).
 #*The Docker service is running.
 #(Optional) To disable the target server verification checks, execute '''install.sh''' with the <tt>-s</tt> parameter:

@@ Line 16: / Line 16: @@
 *It can join agent and customer data to an interaction dataset on-premises, prior to upload to the GPR Core Platform.
 *It enables you to upload datasets to the cloud-based Feature Engineering pipeline (CFEP), which facilitates computation of aggregated features and complex data joins for more broad-based predictive analysis. The CFEP is enabled by default. See {{Link-SomewhereInThisVersion|manual=Deployment|topic=DL-CFEP|display text=Configure for Feature Engineering}} for the steps required to use feature engineering and, if you do not want to use the CFEP, how to disable it.
-*If your GPR Core Platform account is created for on-premises anonymization, Data Loader anonymizes sensitive data and personally identifiable information (PII). (By default, GPR anonymizes data in the cloud. For more information, see {{Link-SomewhereInThisVersion|manual=Deployment|topic=dataReqs|anchor=anonymize|display text=Data anonymization}}.)
+*It anonymizes sensitive data and personally identifiable information (PII). For more information, see {{Link-SomewhereInThisVersion|manual=Deployment|topic=dataReqs|anchor=anonymize|display text=Data anonymization}}.
 Deploying Data Loader has the following main phases:

@@ Line 225: / Line 225: @@
 <tt>$ bash install.sh -s</tt>
 ===Mapping Between Folders on the Host and in the Container===
 The following list shows the full path to the various folders on the host machine where the Data Loader container is deployed and the corresponding Docker container folders:

@@ Line 10: / Line 10: @@
 *It can join agent and customer data to an interaction Dataset for more broad-based predictive analysis.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Prereq=
 |Section={{Section

@@ Line 170: / Line 170: @@
 When your environment is configured for anonymization on-premise, assign Read, Change, Execute, and Read & Execute permissions to the following configuration objects.
-* The Data Loader '''Application''' object.
+*The Data Loader '''Application''' object.
-* The Predictive_Route_DataCfg '''Transaction List''' object, which is used by the GPR URS Strategy Subroutines.
+*The Predictive_Route_DataCfg '''Transaction List''' object, which is used by the GPR URS Strategy Subroutines.
-* All levels of the folder/directory structure within which the Data Loader '''Application''' object and the Predictive_Route_DataCfg '''Transaction List''' object exist.
+*All levels of the folder/directory structure within which the Data Loader '''Application''' object and the Predictive_Route_DataCfg '''Transaction List''' object exist.
 This ensures that Data Loader can create and read the options specific to anonymization in the Data Loader '''Application''' object and the Predictive_Route_DataCfg '''Transaction List''' object.
@@ Line 300: / Line 300: @@
 {{!}}To
 {{!}}For Microsoft SQL Server, the default communication port is 1433; for Oracle, it is 1521; for PostgreSQL, it is 5432.
-{{!}}The database access point (DAP) for the Genesys Info Mart database. For more information about configuring this DAP, see [[Documentation:GIM:Dep:GIMConfigDAPs:Current{{!}}Configuring Required DAPs]] in the ''Genesys Info Mart Deployment Guide''.
+{{!}}The database access point (DAP) for the Genesys Info Mart database. For more information about configuring this DAP, see [https://docs.genesys.com/Documentation/GIM/Current/Dep/GIMConfigDAPs Configuring Required DAPs] in the ''Genesys Info Mart Deployment Guide''.
 {{!}}-
 {{!}}GPR Data Loader

@@ Line 9: / Line 9: @@
 *It enables you to upload CSV files containing customer and outcome data, which is used to create the Customer Profile and outcome Datasets.
 *It can join agent and customer data to an interaction Dataset for more broad-based predictive analysis.
 |ComingSoon=No
 |Platform=PureEngage
 |Prereq=
 |Section={{Section
@@ Line 25: / Line 21: @@
 *Download the Data Loader IP and unzip the installation files.
 *{{Link-SomewhereInThisManual|topic=cfgAsc|anchor=cfgApp|display text=Create and configure the Data Loader <tt>Application</tt> object}} in your Genesys configuration application.
 *Create, and set appropriate values for, [https://docs.genesys.com/Documentation/Options/Draft/GPM/GPM_DL configuration sections and options]. In addition to controlling aspects of Data Loader performance and connections, these options also specify Dataset schemas and data upload parameters.
@@ Line 170: / Line 167: @@
 #Verify that the '''Log On As''' parameter is configured as the '''SYSTEM''' account.
 #Click '''OK'''.
 |structuredtextwide=
 |FAQHeading=
@@ Line 215: / Line 220: @@
 *Perform the installation using the '''gpr''' user. The '''gpr''' user must have sudo rights to perform the installation.
 *Do NOT use the root user to install Data Loader.
 #To install Data Loader, execute the '''install.sh''' script, using the following command from the folder containing the Data Loader IP package:

PE-GPR/9.0.0/Deployment/cfgAsc - Revision history

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

Vivian.hood@genesys.com: Published

Vivian.hood@genesys.com: Published

Vivian: Published

Vivian: Published

Vivian: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

Vivian: Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"