Difference between revisions of "APEL/SSM"
< APEL
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
* [[APEL/SSMOverview|SSM Overview]] | * [[APEL/SSMOverview|SSM Overview]] | ||
* [[APEL/SSMInstallation|SSM installation instructions]] | * [[APEL/SSMInstallation|SSM installation instructions]] | ||
* [[APEL/SSMConfiguration|Configuring the SSM]] | |||
* [[APEL/RunningSSM|Running the SSM]] | |||
* [[APEL/SSMProblems|Common SSM problems]] | * [[APEL/SSMProblems|Common SSM problems]] | ||
==== External SSM Testing ==== | ==== External SSM Testing ==== | ||
[[APEL/APELSSMExternalTesting|APEL SSM Testing]]: If you are interested in testing the new STOMP interface or want to develop your own client. | [[APEL/APELSSMExternalTesting|APEL SSM Testing]]: If you are interested in testing the new STOMP interface or want to develop your own client. |
Revision as of 19:21, 15 February 2012
- Back to APEL
- Back to APEL/Server
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.
Introduction
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 could be used elsewhere.
Key features:
- 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
Documentation
External SSM Testing
APEL SSM Testing: If you are interested in testing the new STOMP interface or want to develop your own client.