Cargo query

Jump to: navigation, search

Showing below up to 50 results in range #101 to #150.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

Page ThirdPartyItem Notes Introduced Variation
Draft:PEC-REP/Current/PulsePEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283
Draft:PEC-REP/Current/PulsePEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd Note: Pulse does not currently support Redis Cluster; use Redis in stand-alone mode.
Draft:PEC-REP/Current/PulsePEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1
Draft:PEC-REP/Current/PulsePEGuide/Planning f1d380bf-42b1-4b67-9d27-d574bad90c86 No
Draft:PrivateEdition/Current/TenantPEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283 NOTE: Starting with version 100.0.100.0041, Tenant Service supports PostgreSQL 11.x.


Before deploying Tenant Service, you must provision a PostgreSQL database for Tenant Service using one of the following methods:

  • Create a PostgreSQL database specifically for use by Tenant Service.
  • Use the shared PostgreSQL database, which is recommended in the OpenShift platform.

Deploy a PostgreSQL database using the following commands:?'"`UNIQ--source-0000004B-QINU`"'?During deployment, you require the database information, including credentials. For the list of database parameters that you override in the Tenant Helm chart values.yaml file, see Backend parameters in Override Helm chart values.

Draft:PrivateEdition/Current/TenantPEGuide/Planning 2afd763e-337c-47eb-8428-3bafcc89dbca Starting with version 100.0.100.0041, Tenant Service supports Consul 1.10.
Draft:PrivateEdition/Current/TenantPEGuide/Planning 2f69518e-33af-4c0f-adcc-a98e5427e5e0
Draft:PrivateEdition/Current/TenantPEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd
Draft:PrivateEdition/Current/TenantPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 No
Draft:STRMS/Current/STRMSPEGuide/Planning 2936260e-26af-4170-a54f-30ce99564b4b
Draft:STRMS/Current/STRMSPEGuide/Planning 2f69518e-33af-4c0f-adcc-a98e5427e5e0 No
Draft:STRMS/Current/STRMSPEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd This Redis instance must be a dedicated & non-clustered Redis instance. Support for clustered Redis is planned for a future iteration of Event Stream.
Draft:UCS/Current/UCSPEGuide/Planning 0d238336-2626-4954-8be3-2f1e16fdd0ce Dedicated (one for UCS cluster) as all indices for all tenants are stored in it.
  • UCS does not support SSL communication with Elasticsearch.
Draft:UCS/Current/UCSPEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283 Dedicated for master DB and for each tenant DB due to high load.
  • DB users must have super user privileges or the following PostgreSQL extensions must be installed before deploying UCS-X service:
    • pg_prewarm
    • intarray
Draft:UCS/Current/UCSPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 You can use any Docker OCI compliant registry. No
Draft:UCS/Current/UCSPEGuide/Planning bc90a902-fc45-4546-b05b-bba8f567dba2 If UCS is accessed from outside of a K8s cluster, it is recommended to deploy/configure an ingress controller (for example, NGINX), if not already available. No
Draft:UCS/Current/UCSPEGuide/Planning f1d380bf-42b1-4b67-9d27-d574bad90c86 For UCS, a single regional Google external network LB will be setup as part of the platform setup.


No
Draft:VM/Current/VMPEGuide/Planning 2afd763e-337c-47eb-8428-3bafcc89dbca For additional information, see Voice services configuration in Consul.
Draft:VM/Current/VMPEGuide/Planning 2f69518e-33af-4c0f-adcc-a98e5427e5e0
Draft:VM/Current/VMPEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd
Draft:VM/Current/VMPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 No
Draft:VM/Current/VMPEGuide/Planning f006784a-0bf7-42b7-9838-033f4acb61fe Required for Voice Voicemail Service if you integrate voicemails with email. No
Draft:WebRTC/Current/WebRTCPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 No
Draft:WebRTC/Current/WebRTCPEGuide/Planning 45f198e3-934c-4b6f-848a-393bd81773fe KEDA can be enabled or disabled for WebRTC. But, WebRTC cannot be configured to use HPA instead of KEDA.


No
Draft:WebRTC/Current/WebRTCPEGuide/Planning 9196f7d6-6782-467f-a664-627a2c293000 No
Draft:WebRTC/Current/WebRTCPEGuide/Planning f1d380bf-42b1-4b67-9d27-d574bad90c86 No
GVP/Current/GVPPEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283 The GVP Configuration Server is separate from the Tenant Configuration Server and requires its own database. No
GVP/Current/GVPPEGuide/Planning 2936260e-26af-4170-a54f-30ce99564b4b The following features must be enabled in Consul:

Service Discovery – to register MCP service for auto discovery of MCP pods by RM

No
GVP/Current/GVPPEGuide/Planning 29577a1d-7351-4c78-8369-62f84d696d05 No
GVP/Current/GVPPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 No
GWS/Current/GWSPEGuide/Planning 0ce020f7-57d0-430e-bd82-27bef7d7834c
GWS/Current/GWSPEGuide/Planning 0d238336-2626-4954-8be3-2f1e16fdd0ce GWS requires Elasticsearch 7.17+. You must configure additional options for Elasticsearch to support the Data Collector Service.?'"`UNIQ--syntaxhighlight-00000016-QINU`"'?

You can set up Elasticsearch as a shared or dedicated service.


Yes
GWS/Current/GWSPEGuide/Planning 17ed8d61-7149-43bb-8f0e-199f7d206ec8
GWS/Current/GWSPEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283 GWS supports PostgreSQL 12.x. You can set up PostgreSQL as a shared or dedicated service.


No
GWS/Current/GWSPEGuide/Planning 2afd763e-337c-47eb-8428-3bafcc89dbca GWS supports Consul 1.8. Consul can be installed either inside or outside the Kubernetes cluster. GWS pods require a Consul agent that is running at the Kubernetes node and GWS only communicates with this Consul agent. You must configure a connection to the Consul server in the local Consul agent. Yes
GWS/Current/GWSPEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd The Redis server must run in cluster mode. You can set up Redis as a shared or dedicated service. No
GWS/Current/GWSPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 No
GWS/Current/GWSPEGuide/Planning 9196f7d6-6782-467f-a664-627a2c293000 No
GWS/Current/GWSPEGuide/Planning bc90a902-fc45-4546-b05b-bba8f567dba2
GWS/Current/GWSPEGuide/Planning f1d380bf-42b1-4b67-9d27-d574bad90c86
IXN/Current/IXNPEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283 No
IXN/Current/IXNPEGuide/Planning 2936260e-26af-4170-a54f-30ce99564b4b No
IXN/Current/IXNPEGuide/Planning 2f69518e-33af-4c0f-adcc-a98e5427e5e0 Kafka is required to deliver IXN reporting events to Genesys Info Mart (GIM). It is the same Kafka for GIM and IXN Server. No
IXN/Current/IXNPEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd Redis is required for communication between Orchestration Server (ORS) and IXN Server. It is the same Redis for ORS and IXN Server. No
IXN/Current/IXNPEGuide/Planning 3e732261-b78e-4921-b6a6-08ee0a322ca1 No
PEC-CAB/Current/CABPEGuide/Planning 1a407778-58fe-4acd-8ca7-5af8eac31283 Before you deploy Genesys Engagement Service (GES), a table and user with database owner (DBO) permissions must be deployed and ready for use by GES. You require the following information for GES deployment:
  • Database name
  • Database port
  • Database hostname
  • Database user
PEC-CAB/Current/CABPEGuide/Planning 2afd763e-337c-47eb-8428-3bafcc89dbca
PEC-CAB/Current/CABPEGuide/Planning 3aee73ed-68e0-4c70-8693-2421c68b86cd You require the following information for GES deployment:
  • Redis hostname
  • Redis password (only required if you use a password)
  • Redis port

You require access to the Voice Microservices deployment Redis as well (specifically the Voice Orchestration Service Redis stream). You require the following information about the Voice Microservices Redis for your GES deployment:

  • Redis hostname
  • Redis password (only required if you use a password)
  • Redis port
PEC-DC/Current/DCPEGuide/Planning 0ce020f7-57d0-430e-bd82-27bef7d7834c
PEC-DC/Current/DCPEGuide/Planning 17ed8d61-7149-43bb-8f0e-199f7d206ec8

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

Modify query
  
  
  
  
  
  
    
  
  

Retrieved from "https://all.docs.genesys.com/Special:CargoQuery (2024-03-28 15:19:37)"