KM Deployment - intro

First, let me explain this clearly:
Verint KM is part of a larger application called Channel Automation. Here, we will focus only on how to deploy KM, not the entire suite.

We will also be deploying KM in a High Availability (HA) setup. The architecture we are aiming for is as follows:

as let point some of the flows of this design

1. We do not currently have High Availability (HA) for the database. If you want to implement HA, I recommend using an active-active synchronized database and configuring a DNS name that KM can use to connect to the database.
   This is important because performing a manual switchover for KM in any other way is difficult and can cause a lot of trouble.

2. According to the documentation, I’m supposed to provide both the external and internal load balancer details. I’m not planning to set that up right now to keep the work simpler, but if this project gets extended, I may consider doing it later.

3. In a which over the user need to change the link