Understanding how ContentDirector maps to your network

Ways ContentDirector maps to your network

ContentDirector maps to your network in two different ways:

Physically, through transport groups to move data over the network
Logically, through destination groups to target specific content to individual destinations

Understanding the difference between transport and destination groups is critically important to using ContentDirector efficiently.

Transport groups

ContentDirector maps physically to your network through transport groups. Transport groups are configured during the installation process, and are defined by how devices are physically grouped. ContentDirector uses them to move content to the periphery of the network. Each transport group consists of a distribution point or transport group leader, and destinations or transport group members. The group leader passes content from the core application to the group members. Group leaders can also function as group members.

Destination groups

Superimposed on the transport groups are logical destination groups. Destination groups are collections of destinations that all receive the same content. They preposition content to where viewers are expected to need it.

A destination group can include destinations from any transport group. Destination groups do not need group leaders, because they deal only with the final destination. The task of deciding how the content gets there is left to the transport groups.

Users define destination groups to suit their needs through the ContentDirector management console.

How content flows through ContentDirector architecture

The flow of content in ContentDirector starts at the content source, passes through the core application and transport group leaders, and ends at the destination groups.

The following diagram illustrates the content flow through destination groups and transport groups.