felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Felix > Apache Felix Web Console
Date Wed, 17 Feb 2010 12:03:00 GMT
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=FELIX&amp;forWysiwyg=true"
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Web+Console">Apache
Felix Web Console</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~fmeschbe">Felix
     <div class="notificationGreySide">
         <p><a name="ApacheFelixWebConsole-top"></a></p>

<h1><a name="ApacheFelixWebConsole-ApacheFelixWebConsole"></a>Apache Felix
Web Console</h1>

<div><a href='#ApacheFelixWebConsole-Requirements'>Requirements</a> | <a
href='#ApacheFelixWebConsole-Variants'>Variants</a> | <a href='#ApacheFelixWebConsole-Installation'>Installation</a>
| <a href='#ApacheFelixWebConsole-Configuration'>Configuration</a> | <a href='#ApacheFelixWebConsole-Security'>Security</a>
| <a href='#ApacheFelixWebConsole-BrowserCompliance'>Browser Compliance</a> |
<a href='#ApacheFelixWebConsole-ExtendingtheWebConsole'>Extending the Web Console</a>
| <a href='#ApacheFelixWebConsole-Issues'>Issues</a> | <a href='#ApacheFelixWebConsole-Screenshots'>Screenshots</a></div>

<p>The Apache Felix Web Console is a simple tool to inspect and manage OSGi framework
instances using your favourite Web Browser.</p>

<h2><a name="ApacheFelixWebConsole-Requirements"></a>Requirements</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>The Web Console only has a single required dependency on the framework: A running
implementation of the OSGi Http Service Specification. The reason for this is, that the Web
Console is implemented as a servlet (actually just a gateway servlet dispatching to Web Console
plugins) which is registered with the Http Service. If your framework does not yet have a
Http Service installed, you might select from a variety of such implementations. The following
is just an incomplete list:</p>

	<li>Apache Felix HTTP Service. This is a very basic implementation of the OSGi Http
Service based on Jetty 6.1.7. The Apache Felix HTTP Service has not been released yet, so
you would have to build it yourself.</li>
	<li>PAX Web Service. The PAX Web Service is the basis for a whole range of additions
from the <a href="http://www.ops4j.org" rel="nofollow">OPS4J</a> project. The
PAX Web Service is also based on Jetty 6 and may be dowloaded from the <a href="http://wiki.ops4j.org/confluence/display/ops4j/Pax+Web"
rel="nofollow">OPS4J PAX Web</a> page.</li>
	<li>Equinox HTTP Service implementation. You can get more information on the Equinox
implementation from the <a href="http://www.eclipse.org/equinox/server/" rel="nofollow">Server-Side
Equinox</a> page.</li>

<p>Apart from that Web Console has the following dependencies, which do not need to
be satisfied. In this case the respective functionality is just missing.</p>

	<li>OSGi Log Service &#8211; The Log Service is used for logging. If the service
is not available the Web Console prints logging to the standard output</li>
	<li>OSGi Configuration Admin Service and OSGi Metatype Service &#8211; The Configuration
Admin and Metatype services are used to support simple form based configuration administration</li>
	<li>Apache Felix Declarative Services &#8211; If your framework uses the Apache
Felix Declarative Services implementation, you can use to the Web Console to inspect the declared
components available from the various bundles and managed by the Service Component Runtime.</li>

<p>Note, that the Apache Felix Declarative Services implementation is the only Apache
Felix dependency contained in the Web Console. If you do not use the Apache Felix Declarative
Services implementation, you just cannot inspect the declared components (because there is
no official public API for this). Otherwise the Web Console perfectly operates without any

<h2><a name="ApacheFelixWebConsole-Variants"></a>Variants</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>The Web Console Bundle is available in two variants: A <em>full</em>
variant and a <em>bare</em> variant. The <em>full</em> variant embeds
three Java libraries which are not embedded in the <em>bare</em> variant. The
<em>bare</em> variant expects the packages provided by those libraries to be exported
from bundles installed in the framework.</p>

<p>The three libraries are :</p>

	<li>Apache Commons IO</li>
	<li>Apache Commons FileUpload</li>

<p>Version 2.0.6 is the first release providing a <em>bare</em> variant.
In this release both variants have the same symbolic name but a different file name: <tt>org.apache.felix.webconsole-2.0.6.jar</tt>
for the <em>full</em> variant and <tt>org.apache.felix.webconsole-2.0.6-bare.jar</tt>
for the <em>bare</em> variant. This is <a href="https://issues.apache.org/jira/browse/FELIX-2086"
rel="nofollow">considered a bug</a> and will be fixed in the next release as follows:</p>

	<li><em>Full</em> variant symbolic name: <tt>org.apache.felix.webconsole</tt></li>
	<li><em>Bare</em> variant symbolic name: <tt>org.apache.felix.webconsole.bare</tt></li>

<h2><a name="ApacheFelixWebConsole-Installation"></a>Installation</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>To install just use your favourite current means of installing new bundles in to
the OSGi framework. For example using the Apache Felix shell console you might do:</p>

<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
<pre>&gt; install http://mirror.switch.ch/mirror/apache/dist/felix/org.apache.felix.webconsole-2.0.6.jar
bundle x
&gt; start x

<p>where <em>x</em> is the bundle number printed by the Shell Console indicating
the Bundle ID of the Web Console bundle.</p>

<h2><a name="ApacheFelixWebConsole-Configuration"></a>Configuration</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>The configuration of the Web Console consists of two parts: One part is the configuration
of the Http Service defining at which host address (host and port number) the servlet container
is accessible. This configuration is technically outside of the scope of the Web Console configuration.
See below for more information and how this is influenced.</p>

<p>The second part of the Web Console configuration is the configuration of the console
itself. The Web Console is configured using the OSGi Configuration Admin Service in that the
Web Console registered a <tt>ManagedService</tt> with Service PID <tt>org.apache.felix.webconsole.internal.servlet.OsgiManager</tt>
(of course you may well use the Web Console to edit the configuration of the Web Console itself).</p>

<p>The Web Console supports the following settings with their corresponding default

<table class='confluenceTable'><tbody>
<th class='confluenceTh'> Property </th>
<th class='confluenceTh'> Default Value </th>
<th class='confluenceTh'> Description </th>
<td class='confluenceTd'> <tt>realm</tt> </td>
<td class='confluenceTd'> <tt>OSGi Management Console</tt> </td>
<td class='confluenceTd'> The name of the HTTP Authentication Realm. </td>
<td class='confluenceTd'> <tt>username</tt> </td>
<td class='confluenceTd'> <tt>admin</tt> </td>
<td class='confluenceTd'> The name of the user allowed to access the OSGi Management
Console. To disable authentication clear this value. </td>
<td class='confluenceTd'> <tt>password</tt> </td>
<td class='confluenceTd'> <tt>admin</tt> </td>
<td class='confluenceTd'> The password for the user allowed to access the OSGi Management
Console. </td>
<td class='confluenceTd'> <tt>manager.root</tt> </td>
<td class='confluenceTd'> <tt>/system/console</tt> </td>
<td class='confluenceTd'> The root path to the OSGi Management Console. </td>
<td class='confluenceTd'> <tt>default.render</tt> </td>
<td class='confluenceTd'> <tt>bundles</tt> </td>
<td class='confluenceTd'> The name of the default configuration page  when invoking
the OSGi Management console. </td>

<p>The default values apply if the respective property is missing from the configuration
or if no configuration is provided at all.</p>

<h4><a name="ApacheFelixWebConsole-ConfigurationoftheOSGiHttpService"></a>Configuration
of the OSGi Http Service</h4>

<p>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 &#8211; <tt>org.osgi.service.http.port</tt>
&#8211; 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.</p>

<p>By default it is probably safe to assume, that having set the <tt>org.osgi.service.http.port</tt>
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 <tt>org.osgi.service.http.port</tt> property is set to <em>8888</em>
the Web Console in the local system can be reached at : <tt><a href="http://localhost:8888/system/console"
rel="nofollow">http://localhost:8888/system/console</a></tt>, where the <tt>/system/console</tt>
path is configured using the <tt>manager.root</tt> configuration property (see
the Configuration section).</p>

<p>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 <a href="http://www.eclipse.org/equinox/server/http_in_container.php"
rel="nofollow">Equinox in a Servlet Container</a> 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 <tt>sample.org</tt>
at port <tt>8888</tt> and the web application with your OSGi container is available
in the <tt>/osgi</tt> context, the Web Console would be accessible at <tt><a
href="http://sample.org:8888/osgi/system/console" rel="nofollow">http://sample.org:8888/osgi/system/console</a></tt>.</p>

<h2><a name="ApacheFelixWebConsole-Security"></a>Security</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>The Web Console only has very basic security at the moment supporting only HTTP Basic
authentication. This security is enabled by default and may be disabled by simply clearing
the <tt>username</tt> property.</p>

<p>To enhance the security of the Web Console you strongly encouraged to change at least
the <tt>password</tt> for the admin user.</p>

<h2><a name="ApacheFelixWebConsole-BrowserCompliance"></a>Browser Compliance</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>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 <em>Web Console</em> in our
issue tracking system (<a href="https://issues.apache.org/jira/browse/Felix" rel="nofollow">JIRA</a>).</p>

<p>Beginning with Release 1.2.8 the Web Console is using JQuery to enhance the user
experience. This should also help in keeping browser support on the broadest possible basis.</p>

<h2><a name="ApacheFelixWebConsole-ExtendingtheWebConsole"></a>Extending
the Web Console</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>The Web Console can be extended by registering an OSGi service for the interface
<tt>javax.servlet.Servlet</tt> with the service property <tt>felix.webconsole.label</tt>
set to the label (last segment in the URL) of the page. The respective service is called a
Web Console Plugin or a plugin for short.</p>

<p>Please for to the <a href="/confluence/display/FELIX/Extending+the+Apache+Felix+Web+Console"
title="Extending the Apache Felix Web Console">Extending the Apache Felix Web Console</a>
for full documentation on extending the Apache Felix Web Console.</p>

<h2><a name="ApacheFelixWebConsole-Issues"></a>Issues</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<p>Should you have any questions using the Web Console, please send a note to one of
our <a href="/confluence/display/FELIX/mailinglists" title="mailinglists">Mailing Lists</a>.</p>

<p>Please report any issues with the Web Console in our issue tracking system (<a
href="https://issues.apache.org/jira/browse/Felix" rel="nofollow">JIRA</a>) and be
sure to report for the <em>Web Console</em> component. See our <a href="/confluence/display/FELIX/Issue+Tracking"
title="Issue Tracking">Issue Tracking</a> page for more details.</p>

<h2><a name="ApacheFelixWebConsole-Screenshots"></a>Screenshots</h2>
<p><a href="#ApacheFelixWebConsole-top">Top</a></p>

<table class='confluenceTable'><tbody>
<td class='confluenceTd'> <a class="confluence-thumbnail-link 1076x880" href='http://cwiki.apache.org/confluence/download/attachments/95821/console-bundles.png'><img
src="/confluence/download/thumbnails/95821/console-bundles.png" align="absmiddle" border="0"
title="Bundle List" /></a> </td>
<td class='confluenceTd'> <a class="confluence-thumbnail-link 1076x880" href='http://cwiki.apache.org/confluence/download/attachments/95821/console-bundles-details.png'><img
src="/confluence/download/thumbnails/95821/console-bundles-details.png" align="absmiddle"
border="0" title="Bundle Details" /></a> </td>
<td class='confluenceTd'> <a class="confluence-thumbnail-link 1076x880" href='http://cwiki.apache.org/confluence/download/attachments/95821/console-components.png'><img
src="/confluence/download/thumbnails/95821/console-components.png" align="absmiddle" border="0"
title="Declarative Services Components (requires Apache Felix SCR)" /></a> </td>
<td class='confluenceTd'> Bundle List </td>
<td class='confluenceTd'> Bundle Details </td>
<td class='confluenceTd'> Declarative Services Components (requires Apache Felix SCR)
<td class='confluenceTd'> <a class="confluence-thumbnail-link 1076x880" href='http://cwiki.apache.org/confluence/download/attachments/95821/console-config.png'><img
src="/confluence/download/thumbnails/95821/console-config.png" align="absmiddle" border="0"
title="Configuration Admin" /></a> </td>
<td class='confluenceTd'> <a class="confluence-thumbnail-link 1076x880" href='http://cwiki.apache.org/confluence/download/attachments/95821/console-status.png'><img
src="/confluence/download/thumbnails/95821/console-status.png" align="absmiddle" border="0"
title="System Status: Bundles, Configuration, Services, Properties, ..." /></a> </td>
<td class='confluenceTd'> <a class="confluence-thumbnail-link 1076x880" href='http://cwiki.apache.org/confluence/download/attachments/95821/console-system-info.png'><img
src="/confluence/download/thumbnails/95821/console-system-info.png" align="absmiddle" border="0"
title="System Information" /></a> </td>
<td class='confluenceTd'> Configuration Admin </td>
<td class='confluenceTd'> System Status </td>
<td class='confluenceTd'> System Information </td>
     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>

       <a href="http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Web+Console">View
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=95821&revisedVersion=21&originalVersion=20">View
       <a href="http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Web+Console?showComments=true&amp;showCommentArea=true#addcomment">Add

View raw message