ContentDirector architecture

Components of ContentDirector distributed architecture

ContentDirector has a distributed architecture based on the following main components:

Core application on a Windows or Solaris server, consisting of
- Content control manager that originates and manages content distribution tasks
- Scheduler that schedules content distribution tasks
- Logger
- Integrated Sybase database
ContentDirector Agents (CDAs) on NetCache^TM appliances, that can perform one or both of the following roles:
- 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 on a remote Java-enabled client, to enable remote administration of the core application

The following illustration shows how information flows through the components of ContentDirector.

How the API fits into the ContentDirector architecture

The API communicates only with the database component of the core application. It has no direct communication with the other components. By communicating with the database, the API can control objects that trigger events in the other components. This allows it to act as foundation for a customized user interface or as a mechanism for other applications that utilize the API to interface and communicate with ContentDirector.

The following illustration compares how the standard ContentDirector user interface and the API interact with the core application.