Edge-to-edge chaining
If your organization is geographically dispersed, you might want all your users to have an edge server nearby.
An edge server can get files and metadata from another edge server rather than from a distant commit server.
You can have any number of such edge servers in the chain.
Configure each server so that its P4TARGET is the closest inner server, where "inner" means toward the commit server.
Log in sequence for service users
Although a regular end-user is only required to log in to the closest edge, service users must log in according to the sequence described in this section.
Step for the inner-most edge (edge1):
1. Log into the commit server.
Step for edge2:
1. Log into edge1
Steps for edge3:
1. Log into edge1
2. Log into edge2
- Only the inner-most edge connects directly to the commit server.
- If you include a forwarding replica, it must connect directly with another forwarding replica or the commit server. An edge server between a forwarding replica and a commit server is not supported.