DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Property | Default Value | Description | |||
|---|---|---|---|---|---|
| | The root path to the OSGi Management Console. | |||
| | The name of the default configuration page when invoking the OSGi Management console. | |||
| | The name of the HTTP Authentication Realm. | |||
| | The name of the user allowed to access the OSGi Management Console. To disable authentication clear this value. | |||
| | The password for the user allowed to access the OSGi Management Console. | |||
| | The root path to the OSGi Management Console. | |||
| all plugins enabled | The labels of the plugins enabled and displayed. | |||
| | Log level filter for the | |||
| – | If set, this locale forces the localization to use this locale instead of the one requested by the web browser | | | The name of the default configuration page when invoking the OSGi Management console. |
The default values apply if the respective property is missing from the configuration or if no configuration is provided at all.
Framework Properties
Some of the configuration properties supported through the OSGi Configuration Admin service can also be set globally and statically as framework properties. Such framework properties will also be considered actual default values for missing properties in Configuration Admin configuration as well as for the Metatype descriptor.
Framework Property | Configuration Admin Property |
|---|---|
| |
| |
| |
| |
| |
| |
Please note that setting any of these properties as framework property makes them visible to all bundles deployed. This is particularly to be considered in case of the felix.webconsole.password property (as for authentication, the use of a Web Console Security Provider is suggested anyway).
Configuration of the OSGi Http Service
As said above, the configuration of the OSGi Http Service used by the Web Console to register itself is outside of the scope of the Web Console. Lets just say, the OSGi Http Service specification defines a system propety – org.osgi.service.http.port – which may be set to define the port at which the Http Service should listen for HTTP requests. The respective Http Service implementation may define additional properties to define the actual interface on which to listen or to define a servlet context path.
By default it is probably safe to assume, that having set the org.osgi.service.http.port to a defined value, the Http Service implementation will listen on all interfaces for requests at the set port number and that no servlet context path actually exists. For example, given the org.osgi.service.http.port property is set to 8888 the Web Console in the local system can be reached at : http://localhost:8888/system/console, where the 
/system/console path is configured using the manager.root configuration property (see the Configuration section).
If you happen to deploy an OSGi framework instance inside a traditional web application and thus the Http Service implementation is actually a bridge into the existing servlet container (see for example Equinox in a Servlet Container or the Apache Sling Launchpad Web application), the host, port and context path are defined by your servlet container and web application deployment. For example, if the servlet container listens on host sample.org at port 8888 and the web application with your OSGi container is available in the /osgi context, the Web Console would be accessible at http://sample.org:8888/osgi/system/console.
Security
...
To enhance the security of the Web Console you strongly encouraged to change at least the password for the admin user.
As of Web Console 3.1.0 this simple user setup can be extended by providing Web Console Security Provider. See that page for more information.
Browser Compliance
The goal of the Web Console is to support as big a range of Web Browsers as possible. As it stands now, Firefox (versions 2 and 3), Opera and Internet Explorer (versions 6 and 7) seem to be capable of using the Web Console. Should you encounter any problems with your particular browser, please report an issue for the Web Console in our issue tracking system (JIRA).
...
Please for to the Extending the Apache Felix Web Console for full documentation on extending the Apache Felix Web Console.
RESTful API
While the Web Console does not have a full featured and documented REST-ful API, most plugins try to follow REST approaches. For example the Bundles plugin is able to send information on all bundles or a single directly addressed bundle.
An attempt is made to document the current state of REST-like APIs at Web Console RESTful API
Issues
Should you have any questions using the Web Console, please send a note to one of our Mailing Lists.
...