Secure Stomp Messenger
The Secure Stomp Messenger (SSM) is the messaging system used by APEL to transmit messages. It is written in Python and uses the STOMP protocol.
The SSM is still in development, and we would be happy to hear any comments you have about design, packaging, documentation or anything else - email email@example.com.
The 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 https://wiki.egi.eu/wiki/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.
This is the original and current version of SSM.
- any file can be sent as a message
- messages are encrypted in transit, using IGTF X509 certificates
- all messages are acknowledged by the receiving SSM, so both sides know if a message has been sent
- the same program can act as a sending or receiving SSM, or both
- a receiving SSM must run as a daemon process; a sending SSM can run as a daemon process or can run once, sending all its messages, and quit
The packages (rpm and zip) are available for download here:
External SSM Testing
- APEL SSM Testing: If you are interested in testing the new STOMP interface or want to develop your own client.
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 is under development to conform with EMPA.