Addanc Reference Manual Addanc User Guide
	Installing Addanc System Components

Installing Addanc System Components

The Addanc system uses several "off-the-shelf" components to store and share data and command and control messages:

• MySQL is used by the MySQL Instrumentation Recorder to store the response time data for tests.
• Jabber is used by the Addanc Commander to control and monitor the Addanc Brick(s).

MySQL Server

The MySQL Instrumentation Recorder uses a MySQL database. It is beyond the scope of this documentation to discuss installing a MySQL server. Most Linux distributions include MySQL as one of the standard system components. You may run the Addanc MySQL service on a remote server, on the same workstation/server as the Addanc Commander, or on the same workstation/server as one (or only) Addanc Brick. You may even run the MySQL service on the same server/workstation as the Jabber server.

Creating the Addanc Database

The Addanc Brick's MySQL Instrumentation Recorder assumes the existence of an Addanc database on the MySQL server. The scripts directory contains a MySQL command file, mysqlschema.sql,  that will create the database and table(s). This command file should be use as a mysql command file when logging into to MySQL using an account with database and table creation privileges.

>mysql -h mysql.mydomain.com -u mysqladmin -p mysqlschema.sql

This command file creates a database named "addanc". If your site's needs differ, make sure that you edit the command file to change the database name before issuing the above command.

Addanc MySQL User Account

The MySQL Instrumentation Recorder needs a MySQL user account on MySQL server with (at least) insert privileges for the Addanc database. All Addanc Bricks in a system can share the same MySQL user account. The Addanc MySQL account information is typically stored in the Addanc Brick configuration file.

 Jabber Server

The Addanc Comander and the Addanc Bricks use a jabber server for communication, command, and control. The Addanc development team recommends the use of a dedicated Jabber server. The system components can generate a large volume of jabber traffic (each Addanc Brick reports status every two second, by default) that may be inappropriate for a public or common Jabber server. In addition, most Jabber servers are configured to throttle traffic from a user if that user is "too active." A dedicated Jabber server can be configured to ignore the volume of traffic from the bricks.

The dedicated Jabber server may be provisioned on a separate workstation/server, on the same workstation/server as the MySQL server and database, or on the same workstation/server as a Commander or a Brick.

Once again, it is beyond the scope of this documentation to discuss the installation of a jabber server. The jabber distribution and excellent installation directions are available at www.jabber.org.

Required Accounts

• addanc_commander - The Addanc Commander needs a single account to monitor and control the associated Addanc Bricks. This account information is typically stored in the configuration files of the commander and brick.
• addanc_brick(s) - The Addanc system needs only one jabber account that is shared by all Addanc Bricks. (Individual bricks identify themselves as different jabber resources.) This account information is typically stored in the brick's configuration file. The brick will also need the jabber id of the commander.
• addanc_sink - The Addanc Sink is (was) used to measure the timing accuracy of Addanc connections and transactions. It may optionally be controlled and monitored via a jabber account. Create a jabber id an password for the sink if you want to use this feature.

Jabber Configuration 

The standard Linux Jabber distribution includes configuration defaults that can cause negative results when using the Addanc Commander to monitor the activity of Addanc Bricks. The following changes to the karma parameter in the jabber.xml configuration file will prevent jabber from buffering messages from the brick(s) due to the amount of traffic:

  <service id="c2s">
    <load>
      <pthsock_client>./pthsock/pthsock_client.so</pthsock_client>
    </load>
    <pthcsock xmlns='jabber:config:pth-csock'>
      <authtime/>
      <karma>
        <init>10</init>
        <max>10</max>
        <inc>0</inc>
        <dec>0</dec>
        <penalty>-6</penalty>
        <restore>10</restore>
      </karma>
      <ip port="5222"/>
    </pthcsock>
  </service>

The <inc> and <dec> parameters for the "c2s" service should be set to 0.