Examples of how to use the .NET API for various features and functions.

When building configuration files without the Admin Console, or to change settings in the API, use this reference to map Admin Console General settings to the relevant config file node or API key.

There are a number of precautions that should be taken before running Exago in a production environment.

A list of supported operating systems, server software, .NET and mono versions and web browsers.

The Scheduler Queue is a custom-built application library that sits between the Exago core application and any number of Scheduler Service instances and handles how schedule traffic is managed. The Scheduler Queue is completely optional, but configurations with multiple scheduler instances for which load balancing is a priority are ideally suited to making use of this feature.

When updating Exago, consult this guide for potential breaking changes.

A variety of resources are available to both end-users, system administrators and developers for help, support and training. This article points out where this information can be found across our web sites.

User logins must be handled by a security layer in the embedding host application. After a user logs in, the host application should pass identification parameters to the Exago API, which can be used to set permissions on content and data objects within Exago.

This reference guide describes the structure of the base configuration file (typically WebReports.xml), for all nodes outside of the node. Use this guide if you build or edit your config XML directly, without using the Admin Console.