Interaction with the HTTP Large Platform

Dynamic Cloud Packaging leverages the HTTP Large platform to stream live and on-demand content. Specifically, it leverages the HTTP Large platform to achieve efficient worldwide delivery. This allows it to take advantage of the services and features that are available on the HTTP Large platform.

Learn how to:

• Generate Dynamic Cloud Packaging-specific reports.
• Configure Rules Engine to be compatible with Dynamic Cloud Packaging.
• Secure streams.

Reports and Analytics

Traffic generated by the Dynamic Cloud Packaging service is logged under the HTTP Large platform. This report data may be viewed via our Analytics product. Detailed information on how this data is reported for each module is provided below.

Module	Description
Core Reports	Core Reports does not distinguish or segregate Dynamic Cloud Packaging traffic from other HTTP Large traffic. The following reports include data for all HTTP Large traffic: Traffic Summary "All Platforms" reports "HTTP Large" reports
Custom Reports	If Dynamic Cloud Packaging is streamed via an edge CNAME, then a custom report may be generated to view hits and data transferred statistics. Enable the logging of the number of hits and total data transferred for a specific edge CNAME by enabling its Custom Reports option.
Real-Time Statistics	Real-Time Statistics does not distinguish or segregate Dynamic Cloud Packaging traffic from other HTTP Large traffic. The following reports include data for all HTTP Large traffic: Overview dashboard "HTTP Large Object" dashboard
Advanced Content Analytics	The following HTTP Large reports track usage by origin directory: By File By Directory By Download By 404 Errors
Edge Performance Analytics	Origin Directory The following HTTP Large reports track usage by origin directory: URLs Cache status reports View a list of cache status reports. NONE Details Report CONFIG_NOCACHE Details Report UNCACHEABLE Details Report TCP_HIT Details Report TCP_MISS Details Report TCP_EXPIRED_HIT Details Report TCP_EXPIRED_MISS Details Report TCP_CLIENT_REFRESH_MISS_Details Report Error reports View a list of HTTP error status reports. 404 Errors Report 403 Errors Report 4xx Errors Report 504 Errors Report 502 Errors Report 5xx Errors Report Origin Name The Origins (HTTP Large) report tracks usage by origin name.

To track Dynamic Cloud Packaging usage via Custom Reports

1. Create an edge CNAME that points to one of the origin directories listed below.

2. Set the edge CNAME's Custom Reports option to "Enabled."
3. Wait an hour after creating the above edge CNAME.
4. From your DNS service provider, create or update a CNAME record to point the edge CNAME's hostname to the CDN hostnameRefers to a system-defined hostname that is specific to your customer account and a CDN service. (e.g., wpc.0001.{Base Domain}).

To generate a custom report on Dynamic Cloud Packaging traffic

1. Verify the following:

   • An edge CNAME that points to Dynamic Cloud Packaging has been created.
   • The Custom Reports option has been enabled on this edge CNAME configuration.
   • Traffic is being served over this edge CNAME.

2. Navigate to the HTTP Large custom report. How?From the main menu, navigate to Analytics | Custom Reports. Click HTTP Large from the side navigation bar.

3. Statistics on the Dynamic Cloud Packaging-specific edge CNAME may be viewed in the table displayed below the bar graph.

Rules Engine

Rules Engine can impact the functionality of Dynamic Cloud Packaging. For example, a rule that defines a cache policy on all requests will prevent a player from retrieving an updated manifest file. In turn, this will prevent the player from properly streaming the requested media.

Under most circumstances, it is recommended to modify each rule's match conditions (e.g., CDN Origin, Customer Origin, Edge CNAME, etc.) to exclude this service. An exception takes place when securing manifest files (e.g., via the Token Auth feature).

Tips for defining or reviewing rules:

• Most rules that apply to all requests will impact this service. Please carefully review all such rules.

• The best way to ensure that a rule will not apply to this service is to match by origin server or by URL.

  View the origin directories used by Dynamic Cloud Packaging.

Origin Directories

Dynamic Cloud Packaging uses the following origin identifiers:

Type	Origin Directory
Live Streaming - Playback	/24ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC. (Dynamic Cloud Packaging Live Playback Instance) Sample Playback URL: http://wpc.0001.{Base Domain}/240001/myinstance/movie.mp4.m3u8
Live Streaming - Publishing	/20ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC. (Dynamic Cloud Packaging Live Publish Instance) Report data is not generated for publishing points. Sample Publishing Point URL: http://wpc.0001.{Base Domain}/200001/myinstance/stream.m3u8
On-Demand Streaming - CDN Storage	/04ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC. (Dynamic Cloud Packaging CDN Origin) Sample Playback URL (CDN Storage): http://wpc.0001.{Base Domain}/040001/videos/movie.mp4.m3u8
On-Demand Streaming - Customer Origin	/84ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC./customeroriginIdentifies a customer origin configuration by its directory name. Sample Playback URL (Customer Origin): http://wpc.0001.{Base Domain}/840001/sales/videos/movie.mp4.m3u8