24.0 Configuration Files

Moab Accounting Manager uses four configuration files: one for the connection information (site.conf), one for the server (goldd.conf), one for the clients (gold.conf) and one for the graphical user interface (goldg.conf). For configuration parameters that have hard-coded defaults, the default value is specified within brackets.

24.1 Site Configuration

The site configuration file specifies the connection information for the current site such as the server host name, port, backup server, default security method and the symmetric key. Optionally, it may also have blocks that specify connection information for other sites. This file should be readable only by the accounting admin user.

Example 1. The following is an example site.conf file

server.host = red-head1
backup.host = red-head2
server.port = 7071
token.type = Symmetric
token.value = pBaIapJqbfLd8NiyzTJefFXW

[white]
server.host = white-head1
server.port = 7071
token.value = Fl7wOkioUpyjdqJ8ckvWK_ta

[blue]
server.host = blue-head1
server.port = 7071
token.valne = gVSeQ8Diz5O3pzj01y4inGWq

The following configuration parameters may be set in the site configuration file (site.conf).

• backup.host - The hostname of the backup server. Each site can have both a primary server and a hot-standby backup server. They should either point to the same database or separate instances of replicated database. If backup.host is specified, clients will try communicating with the primary server first, and if the connection fails, they will try communicating with the backup server.
  
• server.host - The hostname of the server
• server.port [7112] - The port that the server listens on
  
• token-type [Symmetric] - Indicates the default security token type to be used in both authentication and encryption. Valid token types include Password and Symmetric. The default is Symmetric.
• token.value - When using the Symmetric token type, token.value is the secret key. It is a base64-encoded symmetric key used between clients and the server for authentication and encryption.

24.2 Server Configuration

The following configuration parameters may be set in the server configuration file (goldd.conf).

• currency.itemization [false] — Enables (true) or disables (false) the storing of itemized charges to the Charge table for charge transactions.

• currency.precision [0] — Indicates the number of decimal places in the resource credit currency. For example, if you are will be dealing with an integer billable unit like processor-seconds, use 0 (which is the default). If you will be charging dollars and cents, then use 2. This parameter should be the same in the goldd.conf and gold.conf files.

• database.datasource [DBI:Pg:dbname=mam;host=localhost] — The Perl DBI data source name for the database you wish to connect to

• database.password — The password to be used for the database connection (if any)

• database.user — The username to be used for the database connection (if any)

• event.scheduler [false] — Specifies whether the event scheduler is enabled (true) or not (false)

• event.pollinterval [5] — The period in minutes that the event scheduler uses to check and fire events. The poll interval must divide evenly into the number of minutes in a day (1440).

• log4perl.appender.Log.filename — Used by log4perl to set the base name of the log file

• log4perl.appender.Log.max — Used by log4perl to set the number of rolling backup logs

• log4perl.appender.Log.size — Used by log4perl to set the size the log will grow to before it is rotated

• log4perl.appender.Log.Threshold — Used by log4perl to set the debug level written to the log. The logging threshold can be one of TRACE, DEBUG, INFO, WARN, ERROR, and FATAL

• log4perl.appender.Screen.Threshold — Used by log4perl to set the debug level written to the screen. The logging threshold can be one of TRACE, DEBUG, INFO, WARN, ERROR, and FATAL

• notification.deliverymethod [store] — Specifies which deliverymethod is used by default if unspecified

• notification.duration [1209600] — Defines how long in seconds that stored notifications persist before being automatically deleted. The default is two weeks.

• response.chunksize [0] — Indicates the line length in the data response that will trigger message segmentation (or truncation). A value of 0 (zero) means unlimited, i.e. that the server will not truncate or segment large responses unless overriden by a chunksize specification in a client request. The response chunksize will be taken to be the smaller of the client and server chunksize settings.

• security.authentication [true] — Indicates whether incoming message authentication is required

• security.encryption [false] — Indicates whether incoming message encryption is required

• super.user [root] — The primary Moab Accounting Manager system admin which by default can perform all actions on all objects. The super user is sometimes used as the actor in cases where an action is invoked from within another action.