IXN/Current/IXNPEGuide/Overview - Revision history

WikiSysop at 09:01, February 28, 2023

2023-02-28T09:01:36Z

WikiSysop at 08:00, September 29, 2022

2022-09-29T08:00:47Z

WikiSysop at 19:51, March 30, 2022

2022-03-30T19:51:35Z

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

2021-11-09T20:28:15Z

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

Karl abraham.abel@genesys.com: Published

2021-10-29T17:33:54Z

Published

New page

{{Article
|Standalone=No
|DisplayName=About Interaction Server
|Context=Learn about Interaction Server and how it works in Genesys Engage cloud private edition.
|ComingSoon=No
|Section={{Section
|alignment=Vertical
|structuredtext====IXN Service===
The new Interaction Server (IXN) Service is built basing on the existing IXN Server with few peculiarities only. It consists of the following PODs:

*IXN Node POD
**IXN Server container
**IXN Node container (new component)
*IXN VQ Node POD
**IXN VQ Node container (new component)

===IXN Server===
Almost all IXN Server functionality is available in IXN Service. Refer to [https://docs.genesys.com/Documentation/IXN/9.0.x/Depl/Overview Overview] for more information about IXN Server.

IXN Server in container image is configured to work with Postgres DB only. MSSQL and Oracle are not supported now.

===IXN Node===
IXN Node is provided in IXN Node POD alongside with IXN Server. It's used as a bridge between IXN Server and new Redis-based routing system. It uses IXN Server protocol like old ORS, fetches interactions for routing, sends them for routing via Redis and RQ Service and forwards routing instructions received from routing system to IXN Server.

===IXN VQ Node===
IXN VQ Node is provided in own IXN VQ Node POD. It's used for sending VQ events from URS to the rest of the system, primarily to Kafka for new Kafka based reporting. StatServers should be connected to IXN VQ Node to receive VQ events as well.
|Status=No
}}
|PEPageType=f94c5001-0cfd-4352-ace3-a27b07d5f3a1
}}

← Older revision		Revision as of 09:01, February 28, 2023
Line 32:		Line 32:

	*Google Kubernetes Engine (GKE)		*Google Kubernetes Engine (GKE)
−	*OpenShift Container Platform (OpenShift)
	*Azure Kubernetes Service (AKS)		*Azure Kubernetes Service (AKS)

@@ Line 32: / Line 32: @@
 *Google Kubernetes Engine (GKE)
 *OpenShift Container Platform (OpenShift)
 See the [https://all.docs.genesys.com/ReleaseNotes/Current/GenesysEngage-cloud/InteractionServer Interaction Server Release Notes] for information about when support was introduced.

@@ Line 5: / Line 5: @@
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
-|structuredtext====IXN Service===
+|structuredtext=The new Interaction Server (IXN) Service is built basing on the existing IXN Server with few peculiarities only. It consists of the following PODs:
 *IXN Node POD
@@ Line 25: / Line 25: @@
 ===IXN VQ Node===
 IXN VQ Node is provided in own IXN VQ Node POD. It's used for sending VQ events from URS to the rest of the system, primarily to Kafka for new Kafka based reporting. StatServers should be connected to IXN VQ Node to receive VQ events as well.
 |Status=No
 }}
 |PEPageType=f94c5001-0cfd-4352-ace3-a27b07d5f3a1
 }}

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=About Interaction Server
-|Context=Learn about Interaction Server and how it works in Genesys Engage cloud private edition.
+|Context=Learn about Interaction Server and how it works in Genesys Multicloud CX private edition.
 |ComingSoon=No
 |Section={{Section