Child pages
  • Running a management agent
Skip to end of metadata
Go to start of metadata

There are a number of ways to run a management agent on your system.

Rolling your own from bundles

See Configuring the Management Agent for the guide on this.

Using the ace-target-devgateway module

The ace-target-devgateway results in a zip file, which contains a ready-to-run target, which looks a lot like the 'rolling your own' solution above. You can run it using the run.bat or run.sh files, and the configuration can be changed in the conf directory.

Running your own using the managementagent target

The ace-managementagent module creates a single bundle, which contains all of the necessary bundles to run a management agent. It responds to system properties for its settings; the supported properties are

Property

Description

Default

discovery

The ACE server to connect to

http://localhost:8080

identification

The identification of this target

configuredGatewayID

syncinterval

How often should we contact the server? The interval is in ms.

2000

You can also use the Config Admin to configure the managementagent.

Using the single-bundle launcher

For most situations, this will be the preferred solution. The output of the ace-launcher module is a single jar, which contains Felix and a management agent.
ace-launcher understands all system properties that the managementagent target uses. Furthermore, it supports the following command line arguments,

Property

Description

Example

fwOption

Additional framework options. You can use this argument multiple times for multiple properties.

fwOption=org.osgi.framework.system.packages.extra=sun.misc,com.sun.management

As an integrated example, we start a managementagent which

  • identifies itself as 'myTarget'
  • connects with the server at 'http://ace.mycompany.com:8080'
  • runs its HTTP service on port 5678
    java -Ddiscovery=http://ace.mycompany.com:8080 -Didentification=myTarget -jar ace-launcher.jar fwOption=org.osgi.service.http.port=5678
  • No labels