Manage Server Capabilities
Server capabilities are designed to enable users with the Operations or Admin Role to control the flow of Delivery Service traffic through only the cache servers (Edge or Mid) that have the required capabilities. For example, Delivery Services designed to serve large binary files should only have requests routed to cache servers with sufficient disk cache. Currently, this can be controlled at the Edge-tier where system operators can explicitly assign only Edge-tier caches with sufficient disk cache to the Delivery Service. However, operators do not have control of Mid-tier cache assignments and cannot dictate which Mid-tier caches are qualified to serve these large binary files. This will cause a problem if a Mid-tier cache with insufficient disk cache is asked to serve the Delivery Services’ large binary files.
A list of the server capabilities can be found under Role (“operations” or “admin”) can create or delete server capabilities. Server capabilities can only be deleted if they are not currently being used by a cache server or required by a Delivery Service.. Users with a higher-level
Manage server capabilities assigned to a server
Users with the Operations or Admin Role can associate one or more server capabilities with a cache servers (Edge or Mid) by navigating to a server via and using the context menu for the server table and selecting or by navigating to .
Configure delivery service required server capabilities
Users with the DELIVERY-SERVICE:CREATE or DELIVERY-SERVICE:UPDATE permission can associate one or more required server capabilities with a Delivery Service by navigating to a Delivery Service via and clicking on Required Capabilities checkbox present on Delivery Services form (HTTPS and DNS)`.
Adding a required server capability to a Delivery Service will ensure two things: