Content-based routing

The topic provides information about how the content-based routing works in the Virtual Directory.

Content-based routing distributes requests to multiple backend servers that host different content. Requests are routed to an appropriate server based on the contents of the request.

A cluster contains a group of servers. Each server in a cluster has a distinct role that is defined in the corresponding server stanza. Depending upon roles that are defined, the server can handle the specific type of request.

A server can have one of the following roles:

Any: Fulfills requests such as search, add, modify, delete, and authentication.
UpdateServer: Fulfills the add, modify, and delete requests.
ReadServer: Fulfills only search requests.
AuthenticationServer: Fulfills only authentication requests.

Depending upon the type of the request, the Virtual Directory server directs the request to an appropriate server. For example, authentication request is directed to the server that has AuthenticationServer role; add, modify, or delete requests are directed to the server that has UpdateServer role.

If a request is made for a particular role and that server is not available, then the Virtual Directory directs that request to a server that has Any role. For example, if an authentication request is made and the Virtual Directory verifies that the AuthenticationServer is not available, the request is directed to the server that has the Any role.