THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Info |
|---|
Under heavy construction |
Introduction
| Excerpt |
|---|
Apache ACE consists of a number of components, which can be deployed more-or-less independently. |
Overview
TODO show the possible topologies: single server and gateway, separate OBR, several relays, where does the client fit in, etc.
...
Software provisioning is the main task of ACE. The provisioning components are responsible for determining the set of bundles to be deployed to a given target, creating a deployment package, and feeding the deployment package to the Deployment Admin.
Components
Topology
TODO think about the client sideTODO show the components of the provisioning mechanism, and where they operate. Remember to point out that the gateway contains separate bundles, but there is also an integrated management agent.
Further reading
TODO create a child page that describes the provisioning part in more detail
...
ACE contains a logging and reporting facility, known as the audit log. This mechanism allows a target to send back logging information to the server, and allows the storing of arbitrary key-value pairs.
The logging mechanism is extensible with extra logging information. The basic implementation will log framework events (e.g., starting and stopping of bundles), and deployment events.
Components
TODO add a description of the components
- o.a.a.server.log The server's log bundle handles the access to the access logs on the server, and provides a servlet that is used for synchronizing logs between target (or relay) and server.
- o.a.a.server.log.store Stores the log on the file; this functionality is separated to allow some other storage mechanism than the file system.
- o.a.a.server.log.task This task is provided to the o.a.a.scheduler so the relay server can synchronize its logs with the 'master' server.
- o.a.a.log Contains general interfaces for the gateway's logs.
- o.a.a.log.listener Listens for framework events, and logs those to the gateway log.
- o.a.a.gateway.log Provides a Log service to which events can be logged.
- o.a.a.gateway.log.store Stores the logs on the gateway until they can be synchronized.
- o.a.a.scheduler
Further reading
TODO create a child page that shows what the logging is about, and how to add your own logging to the mechanism.