NEP provides two environments of (most?) of their APIs (See also the code we use for it), which we will refer to as 'NEP staging' and 'NEP production' (set via setting nep.env=[prd|stg])
The POMS environments are referred to as 'production', 'test' and 'development'
The authentication of the player requires the IP of the client. POMS uses for that the request the browser is doing, and sends it to the so called 'player token' services of NEP, of which the result is needed for their SAM services.
The thing is that it seems that this doesn’t work if this is an IP v6 address, which you may or may not have.
This can be avoided by putting the ip v4 address of the poms-servers in your /etc/hosts. So this may be needed if you want to test functionality involving the player.
|
ℹ️
|
It works on production, probably because the poms.omroep.nl domain has no ipv6 adress |
|
🔥
|
Also, it seems that the player won’t (auto?)play in a headless browser. This needs to be explored |
Under the link 'Liveknipper' a tool is found to make MP4 and screen shots for several channels.
The live itemizer should work in all circumstances. Though I’m not sure if in NEP staging all channels are working.
It can be configured on any poms environment (via nep.live.env=[prd|stg]) with NEP production or NEP staging, and that should not make any difference, since the live itemizer in the current situation does not produce any real data.
Via the link 'Segment toevoegen met speler' you can do three things:
-
Use the player to make new 'segments'
-
Use the player to create an MP4 for download
-
Use the player to make a screenshot for download
For the first function it is only needed that the player actually works. AFAIK the player is only using production data, so all this can only be tested on a MID that plays on production.
To create an MP4 or image via the NEP staging environment, the object must also be known there. I don’t know how to know that.
This is a MID that might work: WO_VPRO_043878
Via the link Bronnen → Upload you can upload a new movie. This link is only available for web only content of avtype 'VIDEO'.
It will only work if the MID is available on either poms production (if NEP production) or poms test (if NEP staging). So to test it on poms development you must use a MID that exists on poms test (if configured with NEP staging).
The NEP notification will always go to POMS production or POMS test. So, this cannot be fully tested on e.g. POMS dev. Via JMX the online notification can be simulated, which would more or less complete the process then.
When the notification arrives (and the object has planned platforms) the mediaobject will receive actual locations ('bronnen'). Note that only on poms production this means that the mediaobject is also playable, because the player always communicates with production data.
So, I think testing all functionality on one object (create object, upload a source, and itemize it that) can only be done at poms production.