JADE is distributed with a graphical control center called Remote Monitoring Agent (RMA).
An extended version of the RMA is included with Jadex.
The class of the agent isjadex.adapter.jade.tools.rma.rma.
The Jadex RMA is mainly a clone of the JADE RMA (cf. Figure A.1, “Jadex RMA Main Window”).
The extended RMA provides shortcut icons for starting the new tool agents:
The main difference to the JADE RMA is the new dialog for starting agents (seeFigure A.2, “Agent Start Dialog”). With the Jadex RMA, an agent definition file (ADF) can be selected for execution. This ADF is supplied either by entering the file name in the Model (ADF) textfield, or by selecting the file from a file requester ( Browse... button). The configuration choice box contains all available start configuration of the loaded agent. After loading the default configuration is automatically selected. The other start parameters ( Agent Name, Class Name, Arguments, Container) are the same as in the JADE RMA.
When loading an agent model from an ADF, the agent name and agent class values are filled in automatically. In addition to the and buttons for starting the agent or aborting the dialog, the Jadex RMA has three more buttons: will read again the currently specified agent model (ADF), e.g. after you have edited the file to correct errors. The Jadex RMA keeps a list of recently loaded agents (stored in a file called rma.properties). This list can be cleared with the button. The button allows viewing a description (see below) of the loaded agent model, before launching the agent.
When an error occurs while loading an agent model, the error message is also displayed below the start parameters in the Description panel. In addition, the panel keeps available the tabs of the last loaded agent models.
Since release 0.92 the Jadex RMA is capable of directly loading agent models from jar files. Use the file requester opened by the button to select a jar file. The RMA will inspect the jar file and allow to choose one of the ADFs that are contained in the jar file (see Figure A.3, “ JAR Selection Dialog ”). The RMA will also add the jar file to the class loader used by Jadex, so any resources from this jar (classes, images, etc.) can be used by the loaded agent, even if the jar file is not contained in the class path. If you want to clean the classpath used by the rma, you can either manually edit the rma properties or just hit the start dialog's reset button.
