---
title: Single Connect Redundancy Testing
slug: singleconnect-2-16/single-connect-redundancy-testing
description: This document provides insights into redundancy testing for Single Connect, a service that relies on a load balancer. It explains how the load balancer uses health check control to determine the availability of the service by sending HTTP requests to port
docTags: 
createdAt: 2022-03-28T07:48:03.000Z
---

::Image[]{src="https://api.archbee.com/api/presign/g9cApVza9NIhSh0pjZYtA/umK0C6Ol23cJRAgd218WP_Single%20Connect%201280-01.png" size="64" position="flex-start" showCaption="false"}



# Redundancy Testing



Health check control is done with http request to port 80 or 443. Receiving HTTP Code 200 OK as a response means that the service is up. The mentioned control is performed by the load balancer belonging to the company. Single Connect nodes do not load balancing within themselves. Requires independent load balancer for load balancing.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/rU8ArbPh0onsGhobntYRH_image.png" size="70" width="648" height="509" position="flex-start" showCaption="false"}


Two methods are available for Single Connect to control redundancy. 
-------------------------------------------------------------------------

### 
Redundancy control can be done by stopping the related service of Single Connect. 

It will be sufficient to run the following commands in the cli with the authorized user. 

**UI Service**

:::BlockQuote
systemctl stop netright-tomcat
:::

**Proxy Services**

:::BlockQuote
systemctl stop nssoapp
systemctl stop sftp\_prox
:::

After the related services are stopped, the load balancer Health check will fail and all traffic should be forwarded to other nodes. After the load balancer directs the traffic, it is seen that the data in the Single Connect is up-to-date and there is no problem in receiving the traffic. 


::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/w7UKtegK_VKLhtbHO8G5A_image.png" size="70" width="672" height="511" position="flex-start" showCaption="false"}

Single connect provides data redundancy with database. When the services at the application level are stopped, the database will continue to be redundant. 

**UI and Proxy Start command**

:::BlockQuote
systemctl start nssoapp
systemctl start sftp\_prox
systemctl start netright-tomcat
:::

### Redundancy control can be done by shutdown the Single Connect server.

After  shutting down Single Connect server, the load balancer Health check will fail and all traffic should be forwarded to other nodes. After the load balancer directs the traffic, it is seen that the data in the Single Connect is up-to-date and there is no problem in receiving the traffic.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/w7UKtegK_VKLhtbHO8G5A_image.png" size="70" width="672" height="511" position="flex-start" showCaption="false"}

When server is turned on again, the difference between the database will be synchronized by the replication. During the synchronization process, the server will be actively available. Single Connect nodes will continue to provide up-to-date services. 


## In structures where load balancer is not used, Single Connect can continue to use and redundancy test by accessing the other node ip address.



::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/kvoOeQMG1bJLV_jSM5NNg_image.png" size="70" width="664" height="379" position="flex-start" showCaption="false"}