Secure Stomp Messenger
Secure Stomp Messenger (SSM) is the messaging system used by APEL to transmit messages. It is written in Python and uses the STOMP protocol.
We would be happy to hear any comments you have about SSM - design, packaging, documentation or anything else - email apel-admins [at] stfc.ac.uk.
For more on testing, see APEL/Test_APEL_Server.
SSM was designed as a way of using python and STOMP to securely and reliably send messages from APEL clients to the APEL server. It is designed to use the EGI broker network (see Message_brokers), but should be compatible with any stomp broker.
It is not tied to any other APEL components, so is also being used for sending StAR and Cloud accounting records.
After discussion within EMI, it was decided that SSM1's design was too complicated for interoperation with other tools. The discussion led to the definition of the EMI Messaging Protocol for Accounting (EMPA), which you can find here: APEL/MessagingProtocol. SSM2 has been developed to conform with EMPA. SSM2 has been released in EMI3.
- any file can be sent as a message
- messages are signed and may be encrypted in transit, using x509 certificates
- a receiving SSM acts as a daemon process; a sending SSM runs, sending all its messages, and then quits
The latest version can be downloaded from this page:
https://github.com/apel/ssm/releases - Choose the apel-ssm rpm for your OS.
Alternatively, you may install using the UMD3 repo. See APEL/SSM2Installation for instructions.