Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This overview shows how the Applications work in Aspire and what can be done with them.

These configuration files are loaded on startup (via <autoStart> in the settings.xml file) or via Admin Web Interface commands. Each one causes a new Component Manager to be launched and configured. System configuration files can be refreshed, removed, or added via the admin user interface.

This contains settings for the specific installation of Aspire. Things like server names, file system paths, etc., anything which is unique to the particular installation of Aspire. It is loaded by the Aspire Application and made available to all components.

This servlet for accessing the administration user interface is initialized by the Aspire application. In addition, the application provides application-level administration commands, such as browsing a list of all OSGi services, memory garbage collection, and JVM memory statistics.