Applications
Contents
The Applications admin tool is where you install, configure, and manage the lifecycle of XP applications from the user interface.
| The Applications app is still using the legacy admin UI, and will be upgraded to Enonic UI in the future. |
Introduction
Applications are the units of functionality that run on Enonic XP - everything from Content Studio to ID providers and custom integrations. The Applications tool gives you a single place to inspect what is installed, install new apps, and start or stop them.
For background on what an XP application is, see XP Applications.
Browsing applications
The Applications tool lists all installed applications across the cluster. Selecting an application opens a detail panel showing:
-
Display name, key, and version
-
Current state (started, stopped, installed)
-
Declared components - sites, parts, layouts, content types, schemas, services, ID providers, etc.
-
Active configuration, if any
| Applications deployed via the file system appear in the list but cannot be uninstalled from the UI - they are managed by your system administrator. |
Installing applications
Click [btn:install] to open the install dialog.
The dialog is directly connected to the Enonic Market, allowing you to browse and search for applications published by Enonic and third-party developers.
Installing custom applications:
- Upload local file
-
Upload a built
.jarfrom your machine. Useful for distributing internal apps that are not published to the Market. - Paste URL
-
Paste a URL pointing to a pre-compiled application file. Useful for installing from private artifact repositories.
| For automated and CI/CD-driven deployment, applications can be installed via the Management API using the Enonic CLI. |
Lifecycle controls
Selecting an application exposes Start, Stop, and Uninstall actions. Stopping an application runs its disposer; starting it re-runs main.js. See Application life cycle for the full sequence.
Configuration
Applications may optionally be configured with environment specific settings by placing a <app-name>.cfg file in the XP configuration directory - see Custom configuration.