Backend Services
About
Incoming requests to the vServices are directed to the Backend Services. Backend Services are the services that are actively providing web services within your network such as e-mail servers. Backend Services can be the services within your local network (inaccessible over the internet), or can be services exposed to the internet (accessible over the internet).
How to Add Backend Services?
To add a new Backend Service, navigate to the Traffic Manager > Backend Services > Add tab from the TR7 ASP web interface.
Interface
Backend Services Listing Screen
Navigate to "Traffic Manager > Backend Services" to see the list of all added Backend Services to TR7 ASP. From this tab, new Backend Services can be added, existing Backend Services can be edited or deleted.
- 1 (Information to be Displayed in the Table)
Information to be displayed on the Backend Services list can be selected.
Following information are selected by default and can be unselected;
- Health
- Backend Service Name
- Route Table
- Cookie Content
- Health Check Type
- Weight
- Address
- 2 (Add)
Add button can be clicked to open the Add Backend Service form.
- 3 (Delete)
One or more Backend Service can be selected and Delete button can be clicked to delete the selected Backend Service(s).
- 4 (Edit)
Edit button can be clicked to open the edit tab for the relevant Backend Service.
- 5 (Search)
Used to search any expression within the table of Backend Services.
- 6 (RegExp Search)
Used to regexp search for all expressions in the table.
- 7 (Column Based Search)
Used to column based search for all expressions in the table.
- 8 (Usage Filter)
Used to filter which vServices all expressions in the table are used in.
- 9 (Health Check Status)
Health status of Backend Services are shown with colors. Scrolling on the health status color displays the explanation for the color code of the Backend Service's health.
Green > Active
Red > Error (If the health probe is unsuccessful, the color turns Red.)
Gray > Inactive (If the related Backend Service is deployed on a Virtual Machine and the Virtual Machine is powered off, health status turns Gray.)
Off > Health Probe is not used.
- 10 (Page Information)
In the opened list, information about how many Backend Services are present and being listed can be found. When a Backend Service is selected from the left side, information regarding the selected Backend Service is displayed here.
- 11 (Page Size)
Maximum number of displayed Backend Services can be selected from here. Navigation between pages can be done using the arrows.
- Preview of the Selected Backend Services
After following the steps "Traffic Manager > Backend Services" and clicking on any Backend Service, a window with information about the relevant Backend Service opens on the right side of the screen.
In this window, information about the relevant Backend Service as well as "Used In" information is also provided. It is seen that the Backend Service named "www.tr7.com" is used in the vService named "www.tr7.com".
The preview can be closed by clicking the (x) button at the top right of the opened window.
Interface
Backend Services Adding Form
"Traffic Manager > Backend Services > Add" steps are followed to add a new Backend Service to the TR7 ASP machine.
- Backend Service Name
Name of the new Backend Service is typed.
- Address
IP:PORT information of the new Backend Service are entered here. By clicking the (+) button, more than one Backend Services can be added from the same form. Names of the Backend Services after addition are given below.
- Route Table
Route table in which the new Backend Service will be in is selected. If no route table is added, it should remain as DEFAULT. For more information on Route Tables click here.
- Health Check
Protocol for the Health Check of the new Backend Service is selected. In the dropdown list, "Traffic Manager > Profiles > Health Check" list lists the present Health Checks. To add a new Health Check Profile Add button is clicked. For more information on Health Check Profiles click here.
- Backup Service
When there are no healthy Backend Services for the redirected traffic coming from a given vService, this method allows traffic to be redirected to the Backend Services marked as "Backup Service". As long as there are healthy Backend Services, traffic is not directed to Backend Services marked as "Backup Service". By default, it is unselected.
- SSL Service
When the Backend Service is selected as "SSL Service", traffic with this service is established with SSL. In this case, traffic to the Backend Service is communicated via SSL protocol. However SSL verification is not a part of this functionality. Connection remains open even if there is an unverified SSL certificate in the Backend Service. By default, it is unselected.
Standart > Communication is established between the Backend Service and TR7 ASP using standard cipher information.
Low > Communication is established between the Backend Service and TR7 ASP using low cipher information. It is recommended to select it in cases where old generation Backend Services (server) are used.
It is used in cases where communication between the Backend Service and TR7 ASP is required only with domain information.
HTTP 2.0 Disabled
HTTP 2.0 Enabled
- Maintenance Mode
By selecting Maintenance Mode, traffic is not directed to the relevant Backend Service. It is used in cases where operations such as maintenance and updates will be carried out in the Backend Services and TR7 does not want the traffic to be directed to the relevant Backend Services.
- Details
Details button can be selected to list given functionalities.
- Use Frontend Port
Instead of the given Port number for the Backend Service, requests incoming to the Port numbers defined on the vService are redirected to the Backend Service from the respective port. By default, it is unselected.
- SNAT
System communicates via the most accessible IP address.
Backend Service is communicated via the IP address of the client. For information about Spoofing click here.
A connection is made to the Backend Service via a different IP address.
A connection to the Backend Service is established via the IP address to be entered manually. Only IP addresses defined in the "Network > Interfaces" tab can be used in this tab. If an IP address that is not defined on TR7 is entered, the connection will fail.
By selecting from the IP addresses defined in the "Network > Interfaces" tab, the connection to the Backend Service is made through the selected IP address.
- Use Different IP for Health Check
The target IP address for which the health check will be performed on the Backend Service is selected.
By default, a health check is performed on the IP:Port of the Backend Service. It is selected by default.
IP:Port health check is performed when entered manually. It is used in cases where the control of the defined Backend Service is desired via a different IP:Port.
- Health Check Source IP
The source IP address for which the health check will be performed on the Backend Service is selected.
A health check is performed from the first Interface IP addresses on the Route Table to which the Backend Service is connected.
A health check is performed via the IP address entered manually. Only IP addresses defined in the "Network > Interfaces" tab can be used in this tab. If an IP address that is not defined on TR7 is entered, the health check will fail.
By selecting from the IP addresses defined in the "Network > Interfaces" tab, the health check is performed through the selected IP address.
- Cookie Content
To use cookie based connectivity (persistance) a cookie name related to the Backend Service can be given here. If left empty, system will randomly assign a cookie to establish cookie persistance.
- Connection Limit
Theoretically, connection limit can range between 1-65535. At most 65535 connections can be made with a service spontaneously. For instance, if the Connection Limit is set to 20, at most 20 connections will be allowed into the Backend Service, and further requests will be directed to other Backend Services based on the configured load balancing algorithm. If there is a single Backend Service, further requests are queued.
- Weight
Weight can range between 1-256. If left empty, all weightless services will have the same (1) weight. Load balancing is done depending on the given weights of the Backend Services. For instance, let us assume that a vService contains 9 Backend Services. If 8 of these services was set to have the weight of 10, and the remaining Backend Service had the weight 20, 2 of the 10 incoming requests to the vService would be directed to the Backend Service with weight 2, and the rest would be equally distributed among the other Backend Services.
- Proxy
It is used if the Backend Service is a Proxy server.
It is not selected by default.
It is selected if the Backend Service has a Proxy server.
It is selected if the Backend Service has a Proxy v2 server.
- Add
Add button can be clicked to add the configured Backend Service.