Open topic with navigation

# Index Records into Broadcast Monitoring

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

HPE 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 to send to HPE Media Server with the `process` action, or open an existing configuration that you want to modify.

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 HPE 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, HPE Media Server starts a new asset. For example, if you set `OutputInterval=30` and `IntervalsPerAsset=10`, HPE 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, HPE 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 HPE 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.

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 HPE Media Server Reference.

6. Save and close the configuration file. HPE recommends that you save your configuration files in the location specified by the `ConfigDirectory` parameter.

© 2016 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close Send Documentation Feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm