Grass Valley iTX Delivery Manager v.2.6 - Manual (Page 45)

39
Adding Core Endpoints
This chapter is for customers who are in the process of migrating from either an iTX 1.4 or a
Colossus system (which are sometimes referred to as Core systems) to an iTX 2.x system. It
can also be used by customers who are running a Core system and an iTX 2.x system in
parallel.
Summary
About the Core Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Preparing the Database for Core Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Generic Steps for Adding a Core Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Generic Steps for Adding a Core Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Additional Configurations for Colossus Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Additional Configurations for iTX 1.4 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Additional Configurations for Both Colossus and iTX 1.4 Systems . . . . . . . . . . . . . . . . . . . . . . 48
Configuring Omneon Video Servers and FTP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
About the Core Endpoint
The Core endpoint facilitates the movement of media and asset records from a
Colossus/iTX 1.4 system.
Because the iTX 2.x and Colossus/iTX 1.4 databases differ in structure, the Core endpoint
effectively acts as a translator between the two systems. It does not in itself handle the
transfer of any media or asset data. Transfers are passed to one of the other endpoints.
For example, if a schedule added to a channel in the new 2.x system requires a piece of
media, its metadata (duration in/out points etc.) from the Colossus/iTX 1.4 system are
imported directly by the Core endpoint while the retrieval of the actual media is passed to a
separate endpoint (e.g. a CIFS or FTP endpoint, configured to point at the Colossus/iTX 1.4
system's relevant storage location).
Just like the other endpoints, the Core endpoint can operate in either Content Change
mode or Search Media mode. The endpoint connects to a Colossus/iTX 1.4 Database and
creates or modifies asset records in iTX 2.x when either:
• Assets are created or modified in the Colossus/iTX 1.4 system.
• Assets are requested by iTX as they are required in a future schedule.