Cisco DNCS System Release 2.8.1 3.8.1 4.3.1 User Guide

The AppServer section of the Administrative Console Status window indicates whether or not the Application
Server is in operation based on the following conditions:



Running — the Application Server software package is present and in operation



Inactive — the Application Server software package is present, but not in operation



Not Responding — the Application Server does not respond when the DNCS tries to communicate with

it



Not Installed — a Application Server host is defined in the host table, but the Application Server

software package is not present; this usually indicates that you are not using our Application Server, but
the application server of another vendor



Blank — no Application Server host is defined in the host table, and the Application Server software

package is not present; usually indicates that you are not using our Application Server, but the application
server of another vendor

When you click the Control (or Monitor, depending on how the Application Server was installed) button in the
AppServer section, the AppServer Control window opens, which allows you to monitor all of the major Application
Server processes.

The Application Server executes applications, such as those in the following list, that are necessary for providing
digital services to subscribers.



DHCT config server (DHCT Configuration Server) — Generates the files containing the global,

hub-specific, and staging configuration values and places the files on the broadcast server.



IPGServer - language supported (Interactive Program Guide Server) — Generates the IPG files

for each language supported, and places the files on the Broadcast File Server. The languages available
are English, French, Spanish, and Japanese.

Note: Each language that is supported has its own application. For example, if English is supported, the
application would be listed as IPGServer- eng.



ppvfileserver (Pay-per-view File Server) — Generates PPV files and places those files on the

Broadcast File Server.



ppvServer (Pay-per-view Server) — Receives PPV event definitions from the billing system and the

PPV UI and stores them in the database. The ppvServer also notifies the ppvfileserver process when it is
time for the ppvfileserver to generate updated files.



vcServer (Virtual Channel Server) — Places the files for all configured virtual channels on the

Broadcast File Server.



bfsRouter (Broadcast File Server Router) — For a Regional Control System (RCS), routes BFS

Application Program Interface (API) calls from the SARA Server, such as IPG, PPV, or VCS, to the BFS on
the DNCS at the central RCS site. The BFS Server on the central RCS site is site-aware. The BFS router
converts any non-site BFS calls to site-specific calls and passes them along to the BFS server. This
includes calls from Application Server processes, such as IPG, PPV, VCS, and any other third-party
applications using the BFS API.

For more information on the SARA Server, refer to the SARA Application Server 3.4.1 User Guide (part number
4012159). See Printed Resources for information on obtaining documentation.