Administering the server

The Administration Console (built with the Administration API) has an easy-to-use interface to manage administrators, monitor servers, and view details about applications running on the server. There are two levels of Administration Console users: server administrators and virtual host administrators. This enables hosting organizations to provide lesser administrative rights to companies using their hosting services. Application developers use the Administration Console to debug applications.

For more information, see Using the Administration Console.

Command-line tools

Adobe provides two command-line tools to help you administer the server: AMSCheck and FLVCheck. AMSCheck provides information about whether the server is running or not, what the response time is, and which amscore processes are not responding. AMSCheck supports only FLV files.

FLVCheck lets you verify that a video file will run properly on Adobe Media Server. The FLVCheck tool supports MP4 files and FLV files.

See Checking server statusand Checking video files.

Log files

Adobe Media Server logs provide real-time server monitoring to help you manage the server and troubleshoot issues. The log files track activity, such as general traffic and server load, who is accessing the server, client behavior and interaction, and general diagnostics. Log files are written in W3C format. You can use standard parsing tools to parse the log files. You can also view log data in the Administration Console.

Adobe Media Server maintains the following logs in the RootInstall/logs folder:

Tracks information about server access. For example, the date and time a client connected to the server and the total bandwidth consumed during a session. It also tracks the streams accessed by the connection and whether the client published a stream. In addition, it tracks whether the client jumped to a new location within a recorded stream.

Tracks information about activities in application instances. For example, the date and time of the event and the server process ID of the event. It also tracks the event status level (warning, error, information, debug, and so on).

Tracks information about Apache HTTP Server errors. This file is in the RootInstall/Apache2.4/logs directory.

Tracks information about Apache HTTP Server access. This file is in the RootInstall/Apache2.4/logs directory.

Track information about server operations; for example, information about stream events, application instances, virtual hosts, and edge/origin issues. By default, the server is configured to create a diagnostic log for each type of server process. The default diagnostic logs are master.xx.log, edge.xx.log, core.xx.log, admin.xx.log, and httpcache.xx.log.

For more information, see Monitoring and Managing Log Files.