If this is the first time you're configuring Akamai edge network services, you should familiarize yourself with some of the common concepts and terms used with the process.
You set up individual rules in a property to determine how to distribute your Adaptive Media Delivery content. Rules consist of match criteria and behaviors. If a request meets the conditions in a rule's match criteria, the behaviors in that rule are applied. Behaviors let you fine-tune and optimize how your content is delivered if the rule's match criteria are met in an end-user request.
Content Provider (CP) code
This is an identifier for a particular subset of content on your origin server. Some features are applied individually to particular CP codes. CP codes are also used to provide additional granularity in reports and to track billing. You'll have at least one CP code per contract. Also, a CP code is associated with a single contract.
This is a record that you maintain that associates your domain name to a unique IP address.
This describes your customer-specific subdomain on the Akamai edge network domain. It maps incoming requests to Akamai edge servers. Typically, you specify edge hostnames in your canonical name (CNAME) records. You associate your property hostname with an edge Hostname in Property Manager when creating a Adaptive Media Delivery property configuration file. For example, via a property hostname your site, www.mymedia.com would point to the edge hostname, www.mymedia.com.akamaized.net. When requests are made to your hostname, they're pointed to the associated edge hostname which resolves to Akamai edge servers. A server then accesses your Adaptive Media Delivery property to read its settings and determine how content is to be delivered.
This is a server in the Akamai edge network that ultimately receives your end-user requests. End-user requests to your domain name are directed to the property hostname and are then redirected to its associated edge hostname which resolves to an applicable edge server. The edge server reads from the Adaptive Media Delivery property configuration tied to the property hostname and determines how your content is to be delivered via rules and behaviors set in that property.
Forward HOST Header
This is the name the edge server forwards (often to the origin server) in the HTTP host request header. This is also referred to as the expected host. Often, this is the same name as the property hostname.
This is the server where you keep your content to be served to end users, typically where your content resides. Edge servers read from the Adaptive Media Delivery property file to determine origin server parameters. You provide these settings when creating your Adaptive Media Delivery property.
Origin Server Hostname
This is the hostname that maps to your origin server from which edge servers retrieve your content. Origin server hostnames should follow a specific naming convention. See Your origin server hostname for details.
This is an identifier that indicates which Adaptive Media Delivery property file and product to use when processing incoming HTTP/HTTPS requests. Often, the property hostname is the full, end-user-facing hostname or fully qualified domain name of your application or site. For instance,
This is your Akamai delivery configuration that includes all of the common rules and the associated behaviors used to process end-user requests for your content. You can use the Property Manager Editor application in Akamai Control Center or the Property Manager API to configure a property.
You set up individual rules in a property to determine how to distribute your Adaptive Media Delivery content. Rules consist of match criteria and behaviors. If a request meets the conditions in a rule's match criteria, the behaviors in that rule are applied. See Define property configuration settings for more details on rule and behavior logic as well as the Default Rule and how it applies in a property.
Updated 22 days ago