Difference between revisions of "PE-GPR/9.0.0/Deployment/envPrereqs"

From Genesys Documentation
Jump to: navigation, search
 
(8 intermediate revisions by 4 users not shown)
Line 2: Line 2:
 
|Standalone=No
 
|Standalone=No
 
|DisplayName=System requirements and interoperability
 
|DisplayName=System requirements and interoperability
−
|Platform=PureEngage
 
 
|TocName=System requirements and interoperability
 
|TocName=System requirements and interoperability
−
|ComingSoon=No
 
 
|Context=Genesys Predictive Routing (GPR) includes several components. This topic provides an overview of the prerequisite hardware and software required to run each component.  
 
|Context=Genesys Predictive Routing (GPR) includes several components. This topic provides an overview of the prerequisite hardware and software required to run each component.  
  
 
It also includes an {{Link-SomewhereInThisManual|topic=envPrereqs|anchor=interop|display text=interoperability table}}, showing which versions of the Genesys components required to run an end-to-end GPR solution are compatible.{{NoteFormat|In addition to the prerequisites noted here, see the [https://docs.genesys.com/Documentation:System:SOE:GPM:Current ''Genesys Supported Operating Environment Reference Guide''], which provides operating system, database, and browser requirements information for most Genesys products.}}
 
It also includes an {{Link-SomewhereInThisManual|topic=envPrereqs|anchor=interop|display text=interoperability table}}, showing which versions of the Genesys components required to run an end-to-end GPR solution are compatible.{{NoteFormat|In addition to the prerequisites noted here, see the [https://docs.genesys.com/Documentation:System:SOE:GPM:Current ''Genesys Supported Operating Environment Reference Guide''], which provides operating system, database, and browser requirements information for most Genesys products.}}
 +
|ComingSoon=No
 +
|Platform=GenesysEngage-onpremises
 
|Section={{Section
 
|Section={{Section
 
|sectionHeading=The GPR components: hardware and software requirements
 
|sectionHeading=The GPR components: hardware and software requirements
 
|anchor=HardwareandSoftwareRequirements
 
|anchor=HardwareandSoftwareRequirements
−
|Standalone=No
 
−
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext={{Link-SomewhereInThisManual|topic=envPrereqs|anchor=ascPrereqs|display text='''Data Loader'''}}
 
|structuredtext={{Link-SomewhereInThisManual|topic=envPrereqs|anchor=ascPrereqs|display text='''Data Loader'''}}
  
−
*Connects to Configuration Server to read the Data Loader Application object, which includes the configuration for your Datasets.
+
*Connects to Configuration Server to read the Data Loader Application object, which includes the configuration for your datasets.
−
*Connects to the Genesys Info Mart Database to upload interaction data; enables upload of customer and outcome data from CSV files.
+
*Connects to the Genesys Info Mart Database to upload interaction data; enables upload of customer and outcome data from .csv files.
 
**Data Loader is deployed in a Docker container. See {{Link-SomewhereInThisManual|topic=envPrereqs|anchor=dockerPrereqs|display text=environment prerequisites and supported versions for your Docker deployment}} for specific requirements.
 
**Data Loader is deployed in a Docker container. See {{Link-SomewhereInThisManual|topic=envPrereqs|anchor=dockerPrereqs|display text=environment prerequisites and supported versions for your Docker deployment}} for specific requirements.
 +
**To enable Data Loader to connect to the GPR Core Platform, you must create the Data Loader user in your account and assign it the SERVICE role. For instructions, see {{Link-SomewhereInThisVersion|manual=Help|topic=cfgUserMgmt|anchor=service|display text=Create the Data Loader user}} in the ''Predictive Routing Help''.
 
**To achieve HA, Data Loader uses a primary/backup HA architecture. Failover is controlled by Local Control Agent, which is deployed in the Docker container with Data Loader. See {{Link-SomewhereInThisVersion|manual=Deployment|topic=cfgAsc|display text=Deploy Data Loader}} for details.
 
**To achieve HA, Data Loader uses a primary/backup HA architecture. Failover is controlled by Local Control Agent, which is deployed in the Docker container with Data Loader. See {{Link-SomewhereInThisVersion|manual=Deployment|topic=cfgAsc|display text=Deploy Data Loader}} for details.
 
*Data Loader must be deployed on a host that has no other instances of Local Control Agent installed.
 
*Data Loader must be deployed on a host that has no other instances of Local Control Agent installed.
  
−
{{Link-SomewhereInThisManual|topic=envPrereqs|anchor=subsPrereqs|display text='''URS Strategy Subroutines/Composer Subroutines'''}}
+
{{Link-SomewhereInThisManual|topic=envPrereqs|anchor=subsPrereqs|display text='''URS Strategy Subroutines'''}}
  
−
*Editable out-of-the-box strategy subroutines to use with your Genesys routing components. Genesys Predictive Routing includes a set of subroutines created for use with Universal Routing Server (URS) and Interaction Routing Designer (IRD).
+
*Out-of-the-box strategy subroutines to use with your Genesys routing components. Genesys Predictive Routing includes a set of subroutines created for use with Universal Routing Server (URS) and Interaction Routing Designer (IRD).
  
 
{{Link-SomewhereInThisManual|topic=envPrereqs|anchor=Reporting|display text='''Genesys Reporting Integration'''}}
 
{{Link-SomewhereInThisManual|topic=envPrereqs|anchor=Reporting|display text='''Genesys Reporting Integration'''}}
Line 33: Line 32:
  
 
*You might need an active internet connection to download additional libraries when installing Docker.
 
*You might need an active internet connection to download additional libraries when installing Docker.
−
*The GPR uses CentOS 7 as the base Docker image.
+
*The GPR uses the RHEL8 universal base image as the base Docker image.
 
*To operate correctly in a Docker environment, SELinux (Security Enhanced Linux) should be disabled or running in permissive mode. For instructions, see {{#Widget:ExtLink|link=https://linuxize.com/post/how-to-disable-selinux-on-centos-7/|displaytext=How to disable SELinux}} on the Linux web site.
 
*To operate correctly in a Docker environment, SELinux (Security Enhanced Linux) should be disabled or running in permissive mode. For instructions, see {{#Widget:ExtLink|link=https://linuxize.com/post/how-to-disable-selinux-on-centos-7/|displaytext=How to disable SELinux}} on the Linux web site.
 
*If you are deploying components in Docker containers in an HA architecture, the system clocks on all target servers must be synchronized. You can use Network Time Protocol (NTP) for this.
 
*If you are deploying components in Docker containers in an HA architecture, the system clocks on all target servers must be synchronized. You can use Network Time Protocol (NTP) for this.
Line 41: Line 40:
 
*Chrome - Latest and one previous
 
*Chrome - Latest and one previous
 
*Internet Explorer - IE 11
 
*Internet Explorer - IE 11
−
|fullwidth=No
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=System requirements and required components/versions
 
|sectionHeading=System requirements and required components/versions
 
|anchor=SystemRequirementsandRequiredComponents/Versions
 
|anchor=SystemRequirementsandRequiredComponents/Versions
−
|Standalone=No
 
−
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=The following table lists the hardware and software requirements that should be in place before starting your deployment.{{AnchorDiv|jopPrereqs}}
 
|structuredtext=The following table lists the hardware and software requirements that should be in place before starting your deployment.{{AnchorDiv|jopPrereqs}}
Line 60: Line 56:
 
{{!}}{{!}}OS
 
{{!}}{{!}}OS
 
{{!}}{{!}}
 
{{!}}{{!}}
−
*CentOS Linux 7 (64-bit)
+
*Red Hat Enterprise Linux Server release 8
 
{{!}}{{!}}
 
{{!}}{{!}}
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}Docker
 
{{!}}{{!}}Docker
 
{{!}}{{!}}docker-ce version 18.09.2 or higher; OR docker-ee 18.09.2 or higher
 
{{!}}{{!}}docker-ce version 18.09.2 or higher; OR docker-ee 18.09.2 or higher
−
{{!}}{{!}}The recommended version was updated in March, 2019. For security reasons, ''all'' deployments should upgrade to the recommended Docker version.
+
{{!}}{{!}}
 
{{!}}-
 
{{!}}-
 
{{!}}{{!}}RAM
 
{{!}}{{!}}RAM
−
{{!}}{{!}}1 GB
+
{{!}}{{!}}16 GB
 
{{!}}{{!}}
 
{{!}}{{!}}
 
{{!}}-
 
{{!}}-
Line 89: Line 85:
 
{{!}}{{!}} 
 
{{!}}{{!}} 
 
{{!}}}
 
{{!}}}
−
|fullwidth=No
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=Interoperability
 
|sectionHeading=Interoperability
 
|anchor=interop
 
|anchor=interop
−
|Standalone=No
 
−
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=Among GPR components:
 
|structuredtext=Among GPR components:
Line 110: Line 103:
  
 
For Routing using the URS Strategy Subroutines:
 
For Routing using the URS Strategy Subroutines:
−
{{{!}} style="height: 88px; width: 548.267px;" data-mce-style="height: 88px; width: 548.267px;" border="1"
+
{{{!}} border="1"
 
{{!}}-
 
{{!}}-
−
! style="width: 206px;" data-mce-style="width: 206px;"{{!}}Hardware/Software Type
+
{{!}}Hardware/Software Type
−
! style="width: 148px;" data-mce-style="width: 148px;"{{!}}Requirement
+
{{!}}Requirement
−
! style="width: 170.267px;" data-mce-style="width: 170.267px;"{{!}}Comments
+
{{!}}Comments
 
{{!}}-
 
{{!}}-
−
{{!}} style="width: 206px;" data-mce-style="width: 206px;"{{!}}Universal Routing Server
+
{{!}}Universal Routing Server
−
{{!}} style="width: 148px;" data-mce-style="width: 148px;"{{!}}8.1.400.60 or higher
+
{{!}}8.1.400.60 or higher
−
{{!}} style="width: 170.267px;" data-mce-style="width: 170.267px;"{{!}} Requires a connection to Stat Server 8.5.108.18 or higher
+
{{!}} Requires a connection to Stat Server 8.5.108.18 or higher
 
{{!}}-
 
{{!}}-
−
{{!}} style="width: 206px;" data-mce-style="width: 206px;"{{!}}Interaction Routing Designer
+
{!}}Interaction Routing Designer
−
{{!}} style="width: 148px;" data-mce-style="width: 148px;"{{!}}8.1.400.39 or higher
+
{{!}}8.1.400.39 or higher
−
{{!}} style="width: 170.267px;" data-mce-style="width: 170.267px;"{{!}} 
+
{{!}} 
 
{{!}}}
 
{{!}}}
 
For integration with Genesys Reporting:
 
For integration with Genesys Reporting:
Line 147: Line 140:
 
{{!}}{{!}} 
 
{{!}}{{!}} 
 
{{!}}-
 
{{!}}-
−
{{!}}{{!}}Genesys Interactive Insights/GCXI
+
{{!}}{{!}}Genesys CX Insights (GCXI)
 
{{!}}{{!}}9.0.012.01 or higher
 
{{!}}{{!}}9.0.012.01 or higher
 
{{!}}{{!}} 
 
{{!}}{{!}} 
 
{{!}}}
 
{{!}}}
 
{{BestPractices}}
 
{{BestPractices}}
−
|fullwidth=No
+
|FAQHeading=removed table cell sizing styles
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Latest revision as of 12:45, March 31, 2022

This topic is part of the manual Genesys Predictive Routing Deployment and Operations Guide for version 9.0.0 of Genesys Predictive Routing.

Genesys Predictive Routing (GPR) includes several components. This topic provides an overview of the prerequisite hardware and software required to run each component.

It also includes an interoperability table, showing which versions of the Genesys components required to run an end-to-end GPR solution are compatible.
Important
In addition to the prerequisites noted here, see the Genesys Supported Operating Environment Reference Guide, which provides operating system, database, and browser requirements information for most Genesys products.
Related documentation:

The GPR components: hardware and software requirements

Data Loader

  • Connects to Configuration Server to read the Data Loader Application object, which includes the configuration for your datasets.
  • Connects to the Genesys Info Mart Database to upload interaction data; enables upload of customer and outcome data from .csv files.
  • Data Loader must be deployed on a host that has no other instances of Local Control Agent installed.

URS Strategy Subroutines

  • Out-of-the-box strategy subroutines to use with your Genesys routing components. Genesys Predictive Routing includes a set of subroutines created for use with Universal Routing Server (URS) and Interaction Routing Designer (IRD).

Genesys Reporting Integration

Important Considerations Related to Docker

  • You might need an active internet connection to download additional libraries when installing Docker.
  • The GPR uses the RHEL8 universal base image as the base Docker image.
  • To operate correctly in a Docker environment, SELinux (Security Enhanced Linux) should be disabled or running in permissive mode. For instructions, see How to disable SELinux on the Linux web site.
  • If you are deploying components in Docker containers in an HA architecture, the system clocks on all target servers must be synchronized. You can use Network Time Protocol (NTP) for this.

Supported Browsers

  • Chrome - Latest and one previous
  • Internet Explorer - IE 11

System requirements and required components/versions

The following table lists the hardware and software requirements that should be in place before starting your deployment.
Data Loader
Hardware/Software Type Requirement Comments
OS
  • Red Hat Enterprise Linux Server release 8
Docker docker-ce version 18.09.2 or higher; OR docker-ee 18.09.2 or higher
RAM 16 GB
Configuration Server 8.1.300.36 or higher
Message Server—for logging 8.1.300.11 or higher


URS Strategy Subroutines
Hardware/Software Type Requirement Comments
See the Genesys Predictive Routing Sizing Worksheet to calculate the memory and CPU requirements for URS when using Predictive Routing.    

Interoperability

Among GPR components:

GPR Component Requirement Comments
Data Loader Requires GPR Hybrid environment  

For Routing using the URS Strategy Subroutines:

{! Interaction Routing Designer
Hardware/Software Type Requirement Comments
Universal Routing Server 8.1.400.60 or higher  Requires a connection to Stat Server 8.5.108.18 or higher
8.1.400.39 or higher  

For integration with Genesys Reporting:

Hardware/Software Type Requirement Comments
Genesys Predictive Routing 9.0.016 or higher  
Interaction Concentrator 8.1.5 or higher  
Genesys Info Mart 8.5.014.19 or higher  
Reporting and Analytics Aggregates 8.5.010.01 or higher  
Genesys CX Insights (GCXI) 9.0.012.01 or higher  

}}

Retrieved from "https://all.docs.genesys.com/PE-GPR/9.0.0/Deployment/envPrereqs (2025-06-21 18:02:37)"
Comments or questions about this documentation? Contact us for support!