Configure A Service – Video Enablement

Prerequisites

Prior to Configuring a Video Enablement Product, the developer must have completed the following:

  • Creation of an Alef Developer Portal Account
  • Subscription to the Alef Video Enablement Product

If there is any confusion as to how to complete these tasks. Please refer to the following document for instruction, https://developer.alefedge.com/get-started/create-edge-native-services/user-guide/. If these two things have been completed, the configuration of the Video Enablement Product can begin.

 

Configuration Page Navigation 

Immediately after the creation of an Alef Video Enablement Subscription, the user is taken to the Configuration Page for the newly created service. Once on the page, the configuration process can begin. If the user is unable to complete the configuration immediately after the subscription creation, please find the steps to get to the configuration page below:

  1. Select “My EdgeNet” from the Horizontal Navigation Bar
  2. Select “My Services” from the subsequent drop-down taking the user to the Subscription Overview Page
  3. On the Subscription Overview Page, click the button furthest to the right on the same row of the Subscription to be configured taking the user to the Content Analytics page of the specific subscription
  4. Once on the Content Analytics Page, click Configure from the Vertical Navigation bar on the left side
  5. The User is now on the Configure Page for the Subscription specified in step 3 and the configuration can proceed.

 

Configure Video Enablement Service

Video Enablement Configuration Steps

Once on the configuration page, data fields are presented to the developer. Some of the data fields will be prepopulated as it is either information that has already been collected by Alef or Alef generated information. Some data fields will be left blank, and the developer will be expected to input the data. Required fields are denoted by an asterisk

On the Video Enablement Subscription Configuration Page, there is some data that needs to be entered by the Developer and some that are pre-populated. The first four fields are pre-populated. Those fields are Service ID, Username / Email ID, Name, and Phone Number. Service ID is generated by the Alef Portal. An additional field, outside the initial four, that is prepopulated is the Edge Storage Size. This is set by Alef to ensure all developers can have sufficient resources.

The rest of the data fields on this page are to be entered by the developer. These fields include Whitelist domain, Secret Key, Secret Token, and Tenancy. Please note, of the four remaining fields, only Whitelist domain and Tenancy are required. If there is any confusion with respect to any of the fields mentioned here, please see the next section for descriptions of these values.

Once all required fields have been properly entered, the developer should click the “Submit” button in the bottom right hand of the page. Once selected, the page will refresh and the “Submit” button will be grayed out. There will also be a black pop-up at the bottom of the page indicating that the Configuration Data has been onboarded successfully. This informs the developer they are ready to interact with the Video Enablement APIs. If there is any confusion on how to leverage the Video Enablement APIs, please read the following document: https://developer.alefedge.com/reference-docs/edgenet-developer-portal/service-usage-docs/api-usage-5g-video-enablement/

 

Video Enablement Service Configuration Fields

Below are explanations of the data fields contained within the Video Enablement Configuration page:

  • Username / Email ID – Email ID of the administrator. This is a pre-populated field
  • Phone Number – The Phone Number entered of the administrator. This is a pre-populated field.
  • Name – The full name of the administrator. This is a pre-populated field.
  • Service ID – The service ID gets assigned to this field. Please note, for API Parameters this is the equivalent to Partner Name. This is a pre-populated field and will be generated when the administrator adds the In-App Video Notification Product.
  • Whitelist Domain(s) – This is the domain that needs to be provided to allow access to the content resources hosted by the Video Enablement when a request is made off the domain. The field format should be a valid URL. Multiple domains can be added with a comma (,) separator.
  • Edge Storage Size – The Edge storage size denotes the space that Alef will need to allocate for this subscription. The edge storage space provided is measured in GB and is pre-populated.
  • Secret Key – The Secret key will be used when we try to onboard content which is private and will be downloaded by using the key. Field input can be alphanumeric, including special characters etc.
  • Secret Token – The secret token will be used when we try to onboard content which is private and will be downloadable by using the token.
  • Tenancy – The Video Enablement service is set as shared tenancy. Please find a short explanation below: 
    • Shared – If the tenancy is selected as Shared, then the video enablement service will function in a default container deployed at the edge site. Multiple services with tenancy denoted as shared will function under the same default container deployed at the edge.
  •  

 

 

How useful was this post?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?