Web Console web-console

The Web console in Adobe Experience Manager (AEM) is based on the Apache Felix Web Management Console. Apache Felix is a community effort to implement the OSGi R4 Service Platform, which includes the OSGi framework and standard services.

On the Web console, any descriptions that mention default settings relate to Sling defaults.
AEM has its own defaults and so the defaults set might differ from those documented on the console.

The Web console offers a selection of tabs for maintaining the OSGi bundles, including:

  • Configuration: used for configuring the OSGi bundles, and is therefore the underlying mechanism for configuring AEM system parameters
  • Bundles: used for installing bundles
  • Components: used for controlling the status of components required for AEM

Any changes made are immediately applied to the running system. No restart is required.

The console can be accessed from ../system/console; for example:


Configuration configuration

The Configuration tab is used for configuring the OSGi bundles, and is therefore the underlying mechanism for configuring AEM system parameters.

See OSGi Configuration with the Web Console for further details.

The Configuration tab can be accessed by either:

  • The drop-down menu:

    OSGi >

  • The URL; for example:


A list of configurations is shown:


There are two types of configurations available from the drop-down lists on this screen:

  • Configurations
    Lets you update the existing configurations. These have a Persistent Identity (PID) and can be either:

    • standard and integral to AEM; these are required, if deleted the values return to the default settings.
    • instances created from Factory Configurations; these instances are created by the user, deletion removes the instance.
  • Factory Configurations
    Lets you create an instance of the required functionality object.

    This is allocated to a Persistent Identity and then listed in the Configurations drop-down list.

Selecting any entry from the list displays the parameters related to that configuration:


You can then update the parameters as required and:

  • Save

    Save the changes made.

    For a Factory Configuration, this creates an instance with a Persistent Identity. The new instance is then listed under Configurations.

  • Reset

    Reset the parameters shown on the screen to those saved last.

  • Delete

    Delete the current configuration. If standard, the parameters are returned to the default settings. If created from a Factory Configuration, then the specific instance is deleted.

  • Unbind

    Unbind the current configuration from the bundle.

  • Cancel

    Cancel any current changes.

Bundles bundles

The Bundles tab is the mechanism for installing the OSGi bundles required for AEM. The tab can be accessed by either of the following methods:

  • The drop-down menu:

    OSGi >

  • The URL; for example:


A list of bundles is shown:


Using this tab you can:

  • Install or Update

    You can Browse to find the file containing your bundle and specify whether it should Start immediately and at which Start Level.

  • Reload

    Refreshes the list displayed.

  • Refresh Packages

    This checks the references of all the packages and refreshes, as necessary.

    For example, after an update both the old and new version may still be running due to prior references. This option checks and moves all references to the new version, allowing the old version to stop.

  • Start

    Starts a bundle according to the start level specified.

  • Stop

    Stops the bundle.

  • Uninstall

    Uninstalls the bundle from the system.

  • see the status

    The list specifies the status of the bundle; clicking the name of a specific bundle with show further information.

After Update, Adobe recommends that you perform a Refresh Packages.

Components components

The Components tab lets you Enable and/or Disable the various components. It can be accessed by either:

  • The drop-down menu:

    Main >

  • The URL; for example:


A list of components is shown. Various icons are available to enable you to enable, disable or (where appropriate) open configuration details for a specific component.


Clicking the name of a particular component displays further information on its status. Here you can also enable, disable, or reload the component.


Enabling, or disabling, a component only applies until AEM/CRX is restarted.
The start state is defined within the component descriptor, which is generated during development and stored in the bundle at bundle creation time.