APEL/SSMConfiguration

From EGIWiki
< APEL
Revision as of 17:15, 6 June 2012 by Wrogers (talk | contribs)
Jump to: navigation, search

Configuring the SSM

The SSM has two configuration files, located in $SSM_HOME/conf.

The supplied configuration will send messages to the test server without any changes. However, if you'd like to configure something differently, it should be simple.

ssm.cfg

This is in the python ConfigParser format - see http://docs.python.org/library/configparser.html.

Things you might want to change

Connection details

There are two ways the SSM can find details of a broker to connect to. One is using the EGI broker networks, the other is specifying host and port of a specific broker.

For the rest of testing and for production, we will use the broker networks. To retrieve information about brokers in the network, we require two pieces of information:

  • the URL of a BDII
  • the name of a broker network
    • currently available are 'PROD' and 'TEST-NWOB'

You can use SSL or username and password or both to connect to the brokers. If you are using SSL, it is important to get the port number right (it will be a different port to the non-SSL connection) - otherwise the connection may hang indefinitely.

We plan to use SSL for production, and for testing once the broker network have authorised the testing DNs.

Other
  1. pidfile location - the pidfile is only created if the process is running continuously as a daemon
  2. Certificate location
  3. messagedb location

Things you probably don't want to change

  1. Consumer configuration - you probably don't want to receive messages
  2. Producer configuration
    1. The default topic will be the one we're listening to
    2. The default consumer DN will be the one of our test server's certificate
    3. The ack topic can be anything, but needs to be unique to your SSM. The default is probably fine

ssm.log.cfg

This is in the standard python logging module's format.

Things you might want to change

  1. log file location:
    1. under the [handler_fileHandler] heading, change the line beginning 'args'.
    2. the 'a' argument means that the log file is appended to.
    3. beware! - the logging module won't expand environment variables, so you must use a full path
  2. logging levels for stomppy or SSM:
    1. under the [logger_*] headings, change the line beginning 'level'.
    2. the possible values are DEBUG, INFO, WARN, ERROR, CRIITICAL.

Things you probably don't want to change

Everything else. If you know the python logging system, you can configure the logging as you like - see http://docs.python.org/library/logging.config.html.