Grass Valley iTX System v.2.6 - Manual (Page 395)

BXF As Run Support
BXF As Run Support
TX Play supports providing BXF based traffic systems with As Run data, via the iTX Metadata
Database.
TX Play not only writes As Run information via the As Run Service to a log file, it also sends the
same information to the Opus Service, which then writes the records to the iTX Metadata
database. This then allows any third party BXF traffic system the ability to query that database
at any convenient time in order to acquire the information dynamically.
This is done via the BXF Schedule Processing Service, the query can be over SOAP, REST or file
based transport mechanisms.
As Run schedules are stored based on the iTX channel name. So for an iTX channel named “A1”
the As Run data is stored in a schedule named “A1_AsRun”. If the schedule does not exist when
As Run data is ready to be stored then a new schedule is created.
The iTX Metadata database is used to store extended data from ingested schedules. In the case
of BXF, extended data is used to store the original BXF event for usage in the As Run records
that are read back by the traffic system.
The As Run Service can still be configured to send As Run records to a web service if required,
but the option is now configurable in the As Run service itself.
March 2015 System Administrator Guide Page 395 of 404