ContentDirector architecture

ContentDirector components

ContentDirector contains the following components:

Core application, consisting of the content control manager that originates and manages content distribution tasks, scheduler, logger, and an integrated Sybase database
ContentDirector Agents (CDAs):
- Group members (GMs) that receive content and serve it to clients
- Group leaders (GLs) that manage communications between the core application and group members
Optional administrator applet to enable remote administration of the core application

Device types for installed components

Each component installs on specific device types.

Component	Device type
Core application	Windows or Solaris server
CDA	NetCache appliance Note You do not need to install ContentDirector on NetCache. It is part of the NetCache kernel. See Configuring the ContentDirector Agent Software for details.
Applet	Remote Java-enabled client

Component

Device type

Core application

Windows or Solaris server

CDA

NetCache appliance

Note
You do not need to install ContentDirector on NetCache. It is part of the NetCache kernel. See Configuring the ContentDirector Agent Software for details.

Applet

Remote Java-enabled client

Master keys and security

ContentDirector components must be able to identify and authorize each other to maintain security. Each installation of the ContentDirector core application has a master key for this purpose. The core application and the CDA reference the master key to verify identity.

A default master key is created when the core application is installed. For higher security, you can create a unique master key for your ContentDirector network. See the ContentDirector Administration Guide for detailed instructions.