- Back to APEL/SSM
Running the SSM
First, install and configure the SSM:
IMPORTANT - once you have installed the SSM, you must provide us with the DN of the certificate you are using so that we can authenticate the messages we receive. In future, this will be done automatically via GOCDB, but for now you need to email us the DN.
Once you have installed and configured an SSM correctly, running it as a sender should be simple. You will have some messages or files which you wish to send to a server. The procedure the SSM follows is:
- It checks its 'outgoing' directory for files (
$SSM_HOME/messages/outgoing, or perhaps elsewhere depending on configuration).
- It sends any files found in this directory as messages, one message per file.
It can do this in one of two ways:
- It can run once, sending any files it finds in that directory at runtime and then exiting
- It can run continuously in the background as a daemon process, checking periodically for new files and sending them when it finds them
The EGI message broker network administrators prefer clients connect only as long as is necessary. We therefore recommend that clients collect their messages for one day and write them to the outgoing directory, then run the SSM once per day to send all those messages.
Running the SSM
These instructions assume you have installed the RPM. If not, you should be able to adapt them to your installation.
Running the SSM once
The prompt will return once all messages have been sent. Hint: if you run the SSM before sending messages, it will create the messages directory and subdirectories for you.
Running the SSM continuously
To monitor the SSM, look in the ssm.log file (default location is /var/log/apel/ssm.log).