Test and debug a client-side script

To help test a client-side script, use trace() statements to monitor each processing point. The output is shown in the Flash Output window (this example is from the Create a Hello World application):

To debug a client-side script, use the Debug menu in Flash to set breakpoints, step into functions, and so forth. You can inspect the state of the script with Windows > Debug Panels.

Test and debug a server-side script

To test a server-side script, use trace() statements to monitor each processing point. View the output of trace() statements in the Live Log in the Administration Console.

To open the Administration Console, choose Start > All Programs > Adobe > Adobe Media Server 3.5 > Adobe Media Administration Console.

When a client connects to an application on the server, the application is loaded and can be seen in the Administration Console. To load an application directly from the Administration Console, select from the New Instance list of available application names. You can also stop an application or reload it—in either case, all clients are disconnected.

Note:

When you edit and save an .asc file, the changes do not take effect until the application is restarted. Use the Administration Console to restart the application, then connect to the application again.

For each application instance, you can observe its live log, clients, shared objects, if any, streams in use, and performance statistics.

View the output of a server-side script

The output of the trace() statements in a main.asc file is sent to the following log file:

rootinstall/logs/_defaultVHost_/yourApplicationName/yourInstanceName/application.xx.log

Where yourInstanceName is _definst_ by default and xx is the instance number, 00 for the most recent log file, 01 for the previous instance, and so on. You can view a log file with any text editor.

While an application is running, you can view the Live Log in the Administration Console. In the Administration Console opens, click View Applications, then Live Log.

Debug with the Administration Console

To playback streams and inspect data about shared objects, an application must make a special debug connection to the Administration Console.

The availability and number of debugging sessions is set in the AllowDebugDefault and MaxPendingDebugConnections elements of the Application.xml configuration file. By default, debugging is not allowed. To override the debug setting in the Application.xml file, add the following code to an application’s server-side code:

 application.allowDebug = true;

Note:

Set allowDebug to false before deploying the application.

To start a debugging session:

  1. Open the Administration Console.

  2. Choose View Applications.

  3. Select the application to debug from the list or choose New Instance and create a new instance of an application.

  4. Press the Streams button to see the list of playing streams, if any.

  5. Click on one of the streams.

  6. Press the Play Stream button.

  7. A pop-up window will open and the stream will play.

  8. Press the Shared Objects button to see the application’s shared objects, if any.

  9. Select a shared object.

  10. Press the Close Debug button to end the debug session.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy