Use case #1: Use two different Property Hostnames
Here, you set up two separate Property hostname to Edge hostname associations ("Property hostnames") and include them to target live or on demand content, based on specific rule match criteria.
Phase 1: Create the Property hostnames
We need a new AMD property with two Property hostnames: one for distribution of the Live content, and a second one for the VoD content. We also want to employ Standard TLS security for access. For this example, we set up the following:
- baseball-highlights-live-media.com. The Property hostname for the live content.
- baseball-highlights-ondemand-media.com. The Property hostname for the VoD content.
The steps that follow outline what you need to do to create the property hostnames for this use case.
- You need Standard TLS certificates set up for each property hostname. These can take awhile to provision, so you should create them before you create the AMD property. You need to include your Property hostnames as a CN or SAN in each respective certificate—"baseball-highlights-live-media.com" for the live content certificate, and "baseball-highlights-ondemand-media.com" for the VoD content certificate.
- Create a new AMD property in Control Center.
- Set up two separate, Standard TLS Property Hostname to Edge hostname associations, one for "baseball-highlights-live-media.com" (for the live media) and one for "baseball-highlights-ondemand-media.com."
Phase 2: Configure the Default Rule for Live Media
At this phase, you need to set up the Default Rule to accommodate live media using Media Services Live (MSL). You also need to set up a new live stream using MSL, outside of Property Manager. Both of these tasks—including proper and recommended settings for use case-based behaviors in the Default Rule—are covered in the Live Streaming with MSL 4.x and AMD - Getting Started Guide.
Taking the settings specified in that guide, behaviors in the Default Rule would be configured as follows:
|Segmented Media Delivery Mode||
Phase 3: Add a new rule VoD requests
This new rule uses the VoD property hostname in its match criteria.
- In the Property Configuration Settings click Add Rule.
- Ensure Blank Rule Template is selected (default) and click Insert Rule.
- Click the gear icon in the New Rule and select Edit Name. Input a desired name (for example, "VoD Delivery Rule") and press Enter.
- Click Add Match and set the fields as follows:
- is one of
- Select Items. Click this field and input the Property hostname for the VoD content (for example, " baseball-highlights-ondemand-media.com").
- Click Add Behavior.
- Type "origin" in the Search
available behaviors field to filter results, select Origin Server,
and click Insert
Behavior. Set the options in this behavior as follows:
- Origin Type: NetStorage
- NetStorage Account: Click to select the NetStorage account associated with the Storage Group that houses the VoD content to be delivered.
- Repeat steps 5-6, to add the
Characteristics, Segmented Media Delivery
Mode, Content Characteristics (optional), and Client
Characteristics (optional) behaviors.
Behavior Options Origin Characteristics Set the following options:
Note: These settings assume you've set the Origin Type to "NetStorage" in the Origin Server behavior.
- Origin Location: Set this to the geographic location that corresponds to the NetStorage Account you set in the Origin Server behavior.
- Authentication Method: Akamai Origins - Auto, Others - None
Segmented Media Delivery Mode Set the following options:
- Mode: On Demand
Content Characteristics Set these options to best fit the VoD content you're delivering to your end users, to optimize its delivery.Note: You could leave this behavior out of this rule to use the options you've set for it in the Default Rule. However, your VoD content may have different optimization requirements than your Live content. Detailed information on this behavior can be found in the AMD - Implementation Guide. Client Characteristics Set the following options:
Note: Only include this behavior if you want to use a different setting than what you've applied for Client Location in the Default Rule. (The Default Rule applies to all requests, so you don't have to include this behavior if you're happy with what's set there.)
- Client Location: Select the geographic region that best represents the clients that will be accessing your VoD content.
What happens next?
Once live in production, request logic for your content works as follows:
- Any request that includes the URL "baseball-highlights-live-media.com" will deliver live content. The match criteria you set in the VoD Delivery Rule is unique to requests to "baseball-highlights-ondemand-media.com," so all of the settings applied the VoD Delivery Rule are ignored, and what you've set in the Default Rule is applied, to deliver the live content.
- Any request that includes the
URL "baseball-highlights-ondemand-media.com" will deliver VoD content.
The VoD Delivery Rule exists last in the property, so it's checked first.
Since the match criteria in this rule has been triggered, all of its behaviors
are applied. However, the Default Rule applies to all requests. So, the
following also apply:
Note: The above points apply to all behaviors in either rule, not just the use case-based behaviors.
- With duplicate behaviors in both the VoD Delivery Rule and Default Rule, what's in the VoD Delivery Rule is used. For example, you set up "NetStorage" as your Origin Server for VoD, and "On Demand" for your Segmented Media Delivery Mode, so those are used for requests to "baseball-highlights-ondemand-media.com." Also, if you added the Content Characteristics behavior in this rule, its settings are used in place of what you've set for that behavior in the Default Rule.
- If you've set behaviors in the Default Rule that aren't in the VoD Delivery Rule, they're applied. For example, if you left out the Client Characteristics behavior from the VoD Delivery Rule, what you set in the Default Rule is used.