Data Center-based Routing

The AppViewX Cloud Connector instances that need to connect to the network endpoints are deployed inside a specific DataCenter in an enterprise's premises. Based on the DataCenter in which the cloud connector is added, the calls to manage the end points are routed to the specific cloud connector inside a DataCenter.

AppViewX supports the following two types of data center routing:

• Non strict routing (Default)

• Strict routing

Non strict routing (Default)

In this mode of routing, when a user selects a specific DC when performing an action (like discovery, device addition, cert push etc), the specific action will be routed to the AppViewX Cloud Connector in the selected DC. However, when there are no healthy AppViewX Cloud Connector instances available in the selected DC, the request will be routed to the next available healthy instance in a different DC.

This is a preferred method of deployment when you do not have a restriction in communication across your data centers.

Strict routing

When you want the requests to an endpoint in a DC to be routed only to the AppViewX Cloud Connector instance in the same DC, enable strict routing. This method ensures that when there are no healthy AppViewX Cloud Connectors in the selected DC to perform the action, the request does not get routed to any other available AppViewX Cloud Connector instance in a different DC. This method is most suitable when you are trying to manage devices within restricted DMZ zones and high latency between DCs.