Page History

Introduction

Using Apache ACE

...

...

Note that the Web UI is still very much a work in progress. No interaction design whatsoever has been applied and the actual interface is very much in flux. It might be these instructions are outdated because of that.

The following steps can be followed to get started:

1. First we need to actually checkout and build ACE. Follow the link to get more information on how to do that.
2. Once ACE is built, we can start
3. Download and start frameworklauncher-ace.zip; alternatively, you can checkout heckout and build ACE yourself.
4. Start the server with integrated Web UI. If you built ACE youself, go to core/deploy/target/dev-server-webuiGo to ace-target-devserver/target/org.apache.ace.target.devserver-*-distribution/ace-devserver. Start it using the run.sh or run.bat file.
5. Now the server is started, let's connect to it. Launch a browser , and point it to: http://localhost:8080/webui/^{Image Removed}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.
6. 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).
7. Upload Copy some sample bundles into the artifacts column by first clicking the 'store' folder of the server. The packaged version above already contains the Felix Application Demonstration bundles.
8. Click on the '+' in the Bundles column and select one or more bundles to import from the OBR (you have to select them one at a time for now) and hit 'Save'.
9. Create a group by hitting the '+' in the groups column.
10. Create a license by hitting the '+' in the licenses column.
11. Select the bundle and group, hit the '<->' button between those columns to link them.
12. Select the group and license, hit the '<->' button between those columns to link them.
13. Start a target. If you built ACE yourself, go to core/deploy/target/dev-gateway. Start it using the run.sh or run.bat file.
14. 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.
15. Create a feature by clicking on the 'Add Feature...' button. Features are the first level of logical grouping for artifacts.
16. Create a distribution by clicking on the 'Add Distribution...' button. Distributions are another level of logical grouping: you group features into distributions.
17. 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.
18. Drag a feature onto a distribution and again repeat this process until you've associated all your features with their relevant distributions.
19. Now we need a target to actually deploy our artifacts to. To start a target, go to ace-launcher/target and start it using java -jar org.apache.ace.launcher*.jar.
20. After a few seconds, the The target should show up in the Web UI. Select it and the license, hit the '<->' button between those columns to link themTo associate it with a distribution, drag that distribution onto the target.
21. Click on 'Store' to actually store changes on the server, which should trigger the actual deployment of the bundle artifacts to the target.
22. Now, you can start adding and removing bundles. Remember to store the state of the repository by using the 'store' button.

How does it work?

Debugging

You can hook up a standard remote debugger to either target. To do that, edit the run.sh (or run.bat) script and include the following extra parameter for Pax Runner:

--vmOptions="-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y"

Now run the target, and start the debugger of your favorite IDE...