Index Records into Broadcast Monitoring

The Broadcast Monitoring output engine transforms information produced by Media Server and indexes it into Broadcast Monitoring.

Media Server segments data into documents, which each represent a fixed amount of video content. You can specify how many documents to index into each asset.

To index information into Broadcast Monitoring

  1. Create a new configuration or open an existing configuration to send to Media Server with the process action. Alternatively, you can modify the Media Server configuration file (mediaserver.cfg).

  2. In the [Output] section, add a new output task by setting the OutputEngineN parameter. You can give the task any name, for example:

    [Output]
    OutputEngine0=BroadcastMonitoring
  3. Below the [Output] section, create a configuration section for the engine by typing the task name inside square brackets. For example:

    [BroadcastMonitoring]
  4. In the new section, set the following parameters:

    Type The output engine to use. Set this parameter to BM.
    BroadcastMonitoringTrickleURL The Broadcast Monitoring URL to send data to. Setting this parameter overrides the setting specified in the [Resources] section, if BroadcastMonitoringTrickleURL has been set there.
    Input (Optional) A comma-separated list of the tracks that you want to output. Specify one or more tracks. If you do not set this parameter, the engine outputs all tracks that are configured by default as 'output' tracks. For information about whether a track is considered an 'output' track, refer to documentation for your analysis, encoding, and ESP engines in the Media Server Reference.
    OutputInterval The amount of video content represented by each output document, in seconds.
    IntervalsPerAsset

    The number of output documents to index into an asset in Broadcast Monitoring. After this number of intervals, Media Server starts a new asset.

    For example, if you set OutputInterval=30 and IntervalsPerAsset=10, Media Server sends documents to Broadcast Monitoring that represent 30 seconds of video content. After 10 of these documents have been sent to Broadcast Monitoring and the asset represents 5 minutes of video, Media Server starts a new asset.

    XSLTemplate The path to the XSL template to use to transform the output so that it can be indexed into Broadcast Monitoring. HPE recommends that you use the XSL template supplied with Media Server, because Broadcast Monitoring requires the data in a specific format.
    LabelSetBroadcaster The name of the video broadcaster, to add to the "Broadcaster" field in the Broadcast Monitoring label set.
    LabelSetCompleted The value to use for the "Completed" field in the Broadcast Monitoring label set (true/false).
    LabelSetProgram The program name, to add to the "Program" field in the Broadcast Monitoring label set.
    DefaultProxyTrack The proxy track to output to Broadcast Monitoring as the default proxy track.
    ProxyTracks (Optional) A comma-separated list of additional proxy tracks to output to Broadcast Monitoring.
    SavePostXML (Optional) Specifies whether to save XML files produced by the Broadcast Monitoring engine. If this parameter is set to true, you must also set the XMLOutputPath parameter.
    SavePreXML (Optional) Specifies whether to save records received by the Broadcast Monitoring engine. If this parameter is set to true, you must also set the XMLOutputPath parameter.
    XMLOutputPath (Optional) The path and file name of the file to save pre-XML and post-XML output to.
  5. (Optional) You can set further optional parameters. For information about the configuration parameters that you can use with a Broadcast Monitoring output task, refer to the Media Server Reference.
  6. Save and close the configuration file. If you modified the Media Server configuration file, you must restart Media Server for your changes to take effect.


_HP_HTML5_bannerTitle.htm