You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2016/08/17 11:18:12 UTC

svn commit: r995300 - in /websites/staging/sling/trunk/content: ./ documentation/bundles/osgi-installer.html

Author: buildbot
Date: Wed Aug 17 11:18:11 2016
New Revision: 995300

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Aug 17 11:18:11 2016
@@ -1 +1 @@
-1756376
+1756615

Modified: websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html Wed Aug 17 11:18:11 2016
@@ -166,8 +166,16 @@ Therefore, for initial provisioning to m
 <li><a href="/documentation/bundles/file-installer-provider.html">File Installer Provider</a></li>
 <li><a href="/documentation/bundles/jcr-installer-provider.html">JCR Installer Provider</a></li>
 </ul>
+<h2 id="health-check">Health Check<a class="headerlink" href="#health-check" title="Permanent link">&para;</a></h2>
+<p>The OSGi installer provides a <a href="/documentation/bundles/sling-health-check-tool.html">Sling Health Check</a> which validates that the processed OSGi installer resources have the correct state (<a href="https://issues.apache.org/jira/browse/SLING-5888">SLING-5888</a>).
+By default it will only check resources with a URL prefix <code>jcrinstall:/apps/</code>, so only the resources being provided through the <a href="/documentation/bundles/jcr-installer-provider.html">JCR Installer Provider</a> initially located below the repository resource <code>/apps/</code> are considered.
+The health check will fail in the following cases:</p>
+<h3 id="bundles-installation-failure">Bundles Installation Failure<a class="headerlink" href="#bundles-installation-failure" title="Permanent link">&para;</a></h3>
+<p>The checked bundle was not installed because it has been installed in a newer version through some other means (e.g. manually through the Felix Web Console or by another provider. For further details please review the OSGi Installer console at <code>/system/console/osgi-installer</code> and check for all bundles with the given symbolic name (=OSGi installers resource id) and the according URL.</p>
+<h3 id="configuration-installation-failure">Configuration Installation Failure<a class="headerlink" href="#configuration-installation-failure" title="Permanent link">&para;</a></h3>
+<p>The checked configuration was not installed because it has either been overwritten manually in the Felix Web Console or is installed by some non-checked provider (which has a higher priority). To revert manually overwritten configurations just go to <code>/system/console/configMgr</code> and delete the according configuration. That way the OSGi installer should automatically create a new configuration for the same PID based on the configuration provided by some provider with the highest prio. In case another non-checked provider has provided already a configuration you can see from where it has been installed by looking at the OSGi Installer console at <code>/system/console/osgi-installer</code> and look for all configurations with the given PID.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1665483 by cziegeler on Tue, 10 Mar 2015 11:33:30 +0000
+        Rev. 1756615 by kwin on Wed, 17 Aug 2016 11:17:54 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project