# Running the Jaxer server diagnostic tools [edit]

This page gives an overview of the Jaxer server diagnostics tools that are included with Jaxer.

## Introduction

The Jaxer server includes a set of simple diagnostic tools to help you make sure that you have the server and your environment configured correctly to use Jaxer. The instructions below explain how to run the diagnostic tests and how to interpret the results.

The diagnostic tools include the following tests:

- Whether or not the `Jaxer` namespace is present and the Jaxer build number
- Your JavaScript versions for your browser and server
- Whether or not it found your (optional) local_config.js file
- Whether or not it found your JaxerCoreJSConsole.log file
- Whether or not a server callback passed the server-side deferred execution test
- Whether or not a server callback passed the callback test
- How many function blocks were saved to the database as part of the database callback test.

## Instructions

### Running the diagnostic tests

To run the Jaxer server diagnostic tests:

1. In your web browser, go to http://localhost:8081/aptana/
2. In the column on the left, click the link to Server Diagnostics.

The diagnostic tests run on Jaxer, and your browser displays the results.

## Related Topics

- About the Jaxer server
- Getting Started with Jaxer in Aptana Studio
- Creating a new Jaxer project
- Previewing a Jaxer project
- About Jaxer Views
  - Displaying the Servers View
  - Displaying the TailView View
  - Displaying the Jaxer Activity Monitor View
  - Displaying the Jaxer Shell View
- Configuring your Jaxer servers
- Setting your TailView preferences
- JaxerManager_Command_Line_Interface_(CLI) Reference

Retrieved from "http://aptana.com/docs/index.php/Running_the_Jaxer_server_diagnostic_tools"

Category: AptanaHelp