Previous: Brick Command Line OptionsUp: Brick User GuideNext: Brick Configuration Files

Addanc Reference Manual
Addanc User Guide

Addanc HomeIndexTable of Contents

Brick User Guide

The Addanc Brick in Daemon Mode

The Addanc Brick can be run attached to a console or as a daemon in detached mode. When running in daemon mode, the Addanc Brick receives command information from an associated Addanc Commander. The Addanc Brick and the Addanc Commanderuse accounts on a jabber server as their messaging backbone.

The Addanc Brick is run in daemon mode by specifying the --deamon option when starting the brick instance or setting the configuration file deamonparameter to "True".

When running in daemon mode, the Addanc Brick requires access to a jabber server to facilitate communication between the Addanc Commander and the Addanc Brick(s). Thus, running in daemon mode means that you have to specify addition configuration information about the jabber server and the IDs of the brick(s) and commander.

[The Addanc Development Team recommends that your use a dedicated jabber server configured to support your testing requirements. Public jabber servers may throttle the rate of messages and interfere with the brick heartbeat message.]

The following configuration parameters must be set when running in daemon mode:
  1. jid - Set the jabber ID of the brick; e.g., ""
  2. jabberpassword - Specify the brick's jabber password.
  3. commanderjid - Set the jabber ID of the associated AddancCommander;e.g., ""
  4. resource_name - Set the brick ID of this instance of the AddancBrick. This ID is used by the AddancCommander to communicate with this brick and to report this brick's status;e.g.,  "Brick01"
When running in daemon mode, the AddancBrick can be controlled and monitored via the AddancCommander. See the Addanc Commander User Guide  Section of this document for more information on the command support available from the AddancCommander.

Multiple instances of the AddancBrick on one workstation

You may want to run multiple instances of the Addanc Brick on a single workstation or server. You may want to take advantage of a multiple processor configuration by running one instance of  a brick for each CPU. You can easily manage this situation, and have all the instances share configuration files, by using the --brickid command line option. For example (assuming all the standard jabber information is in the config file), the following commands would start 3 instances of the Addanc Brick, each with a distinctive ID:

addanc>brick --daemon --brickid="Brick01" sometest.xml 30
addanc>brick --daemon --brickid="Brick02" sometest.xml 30
addanc>brick --daemon --brickid="Brick02" sometest.xml 30

Each of the instances can be monitored and controlled individually by the Addanc Commander using the specified brick ID.

Previous: Brick Command Line Options Up:Brick User Guide Next: Brick Configuration Files
Page Updated: 02/15/2003