Author: buildbot
Date: Thu May 30 08:51:42 2013
New Revision: 863742
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/user-doc/getting-started.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 30 08:51:42 2013
@@ -1 +1 @@
-1487784
+1487787
Modified: websites/staging/ace/trunk/content/user-doc/getting-started.html
==============================================================================
--- websites/staging/ace/trunk/content/user-doc/getting-started.html (original)
+++ websites/staging/ace/trunk/content/user-doc/getting-started.html Thu May 30
08:51:42 2013
@@ -212,7 +212,7 @@
<li>Navigate to the sub directory <code>target</code>.</li>
<li>Start the target using <code>java -jar target.jar</code></li>
</ol>
-<h2 id="working-with-ace">Working with ACE</h2>
+<h2 id="provisioning-some-bundles">Provisioning some bundles</h2>
<p>Apache ACE has both a Web UI and a <a href="restapi.html">REST API</a> to
interact with it. Both use a similar workflow. You start by checking out a copy
of the workspace, then you work on that copy, and finally you commit your
changes back to the server.</p>
<p>The following steps can be followed to get started:</p>
<ol>
@@ -225,7 +225,14 @@
<li>Drag a feature onto a distribution and again repeat this process until
you've associated all your features with their relevant distributions.</li>
<li>Drag the distribution onto the target to associate it.</li>
<li>Click on 'Store' to actually store changes on the server, which should
trigger the actual deployment of the artifacts to the target.</li>
-</ol></div>
+</ol>
+<h2 id="validating-that-it-worked">Validating that it worked</h2>
+<p>After following the steps listed above the bundles should have been
provisioned onto the target. But did it work? There are a lot of things that
can go wrong the first time. For exmaple, remember you are provisioning into an
empty OSGi framework so the deployment should be able to resolve. Two ways to
debug problems are;</p>
+<ol>
+<li>Inspect state and log of the target by double-clicking it in the
webui.</li>
+<li>Start of by provisioning a shell to allow inspection of the target
itself.</li>
+</ol>
+<p>Note: In version 1.0 the default binary target comes with a <a
href="http://felix.apache.org/site/apache-felix-gogo.html";>Gogo shell</a>
pre-installed. It can be used right away.</p></div>
<hr>
<footer>
<p>Copyright © 2012 <a href="http://www.apache.org/";>The Apache
Software Foundation</a>, Licensed under the <a
href="http://www.apache.org/licenses/LICENSE-2.0";>Apache License, Version
2.0</a>.<br/>Apache ACE, the Apache ACE logo, Apache and the Apache feather
logo are trademarks of The Apache Software Foundation. All other marks
mentioned may be trademarks or registered trademarks of their respective
owners.</p>
