Author: buildbot
Date: Thu May 30 08:37:58 2013
New Revision: 863739
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:37:58 2013
@@ -1 +1 @@
-1487781
+1487784
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:37:58 2013
@@ -175,34 +175,55 @@
<h1>Getting Started</h1>
<div class="clear"></div>
<div id="content"><p>This guide shows the core functionality of ACE,
organizing bundles and other artifacts into logical features and distributions
and associating those with specific targets, all done using a convenient web
interface.</p>
-<h2 id="download-and-startup">Download and startup</h2>
+<h2 id="download-the-distribution">Download the distribution</h2>
<p>To start using ACE, you must first launch a server. If you're a developer,
you can do that inside Eclipse, as explained <a
href="/dev-doc/getting-started.html">here</a>. Otherwise, you need to download
a distribution of the server, unpack it, and start it up:</p>
<h3 id="version-081">Version 0.8.1</h3>
<ol>
<li>Download a binary distribution of the server from the <a
href="/downloads.html">download</a> page.</li>
<li>Unpack the archive somewhere on your filesystem.</li>
-<li>Start it by running <code>run.sh</code> (on Linux and Mac OS X) or
<code>run.bat</code> (on Windows).</li>
</ol>
<h3 id="version-10-comming-soon">Version 1.0 (comming soon)</h3>
<ol>
<li>Download the binary distribution called
<code>apache-ace-<version>-bin.zip</code> from the <a
href="/downloads.html">download</a> page.</li>
<li>Unpack the archive somewhere on your filesystem.</li>
+</ol>
+<h2 id="start-the-ace-server">Start the ACE server</h2>
+<h3 id="version-081_1">Version 0.8.1</h3>
+<ol>
+<li>Open a terminal and navigate into the root of the distribution.</li>
+<li>Start the server using <code>run.sh</code> (on Linux and Mac OS X) or
<code>run.bat</code> (on Windows).</li>
+</ol>
+<h3 id="version-10">Version 1.0</h3>
+<ol>
+<li>Open a terminal and navigate nto the root of the distribution.</li>
<li>Navigate to the sub directory <code>server-allinone</code>.</li>
-<li>Start it by running <code>java -jar server-allinone.jar</code></li>
+<li>Start the server using <code>java -jar server-allinone.jar</code></li>
+</ol>
+<h2 id="start-an-ace-target">Start an ACE target</h2>
+<h3 id="version-081_2">Version 0.8.1</h3>
+<ol>
+<li>Open a terminal and navigate into the root of the distribution.</li>
+<li>Navigate to the sub directory <code>ace-launcher/target</code>.</li>
+<li>Start the agent using <code>java -jar
org.apache.ace.launcher*.jar</code></li>
+</ol>
+<h3 id="version-10_1">Version 1.0</h3>
+<ol>
+<li>Open a terminal and navigate into the root of the distribution.</li>
+<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>
<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>
-<li>Now the server is started, let's connect to it. Launch a browser and point
it to: http://localhost:8080/ace/ You should now be greeted with a login
prompt. Log in with user "d" password "f" and you should see a view with 4
empty columns and some buttons at the top of the screen.</li>
-<li>Click on 'Retrieve' to get the initial version of the repository. It will
look as if nothing's happened, but you have now in fact retrieved the first,
empty version of the repository and can start manipulating it. Once you're
happy with it, you can commit it back (which we'll do a bit later).</li>
+<li>Launch a browser and point it to: http://localhost:8080/ace/ You should
now be greeted with a login prompt. Log in with user "d" password "f" and you
should see a view with 4 empty columns and some buttons at the top of the
screen.</li>
+<li>Click on 'Retrieve' to get the initial version of the repository. The
column on the right will show you have a target running with name
<code>defaultTargetID</code>. The other columns remain empty as this is an
initial empty version of the repository.</li>
<li>Upload some sample bundles into the artifacts column by first clicking the
'Add Artifact...' button. In the dialog that appears, you can upload a bundle
using the 'Upload' button in the middle of the window. You can perform this
step multiple times if you want to upload more than one bundle. Finally, hit
the 'Add' button to add all uploaded artifacts to ACE.</li>
<li>Create a feature by clicking on the 'Add Feature...' button. Features are
the first level of logical grouping for artifacts.</li>
<li>Create a distribution by clicking on the 'Add Distribution...' button.
Distributions are another level of logical grouping: you group features into
distributions.</li>
<li>Drag an artifact onto a feature to create an association between the two.
By repeating this process you can associate all relevant artifacts to
features.</li>
<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>Now we need a target to actually deploy our artifacts to. To start a
target, go to <code>ace-launcher/target</code> and start it using <code>java
-jar org.apache.ace.launcher*.jar</code>.</li>
-<li>After a few seconds, the target should show up in the Web UI. To associate
it with a distribution, drag that distribution onto the target.</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>
<hr>
