Difference between revisions of "APEL/SSM2Overview"
< APEL
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
* Back to [[APEL/SSM]] | * Back to [[APEL/SSM]] | ||
'''These notes refer to SSM version 2 | '''These notes refer to SSM version 2. ''' Please send suggestions and queries to | ||
apel-ssm-test@jiscmail.ac.uk | apel-ssm-test@jiscmail.ac.uk | ||
Revision as of 11:38, 1 February 2013
- Back to APEL/SSM
These notes refer to SSM version 2. Please send suggestions and queries to apel-ssm-test@jiscmail.ac.uk
Introduction
The Secure Stomp Messenger (SSM) is a python package designed to send arbitrary files using ActiveMQ and the STOMP protocol. Its key features are:
- It uses the underlying filesystem to store outgoing and / or incoming messages
- It sends arbitrary files from a client to a server SSM
- It can use any broker configured to use STOMP
- Files are signed and may be encrypted during transit using X509 certificates
Interface
The SSM is designed to have a simple interface, which isolates it from any other components it may be used with.
Simplified version
- The sending and receiving SSMs are configured to communicate using a specified queue.
- A file is written to the sending SSM's 'outgoing' directory (by some other process) - see APEL/SSM2AddingFiles.
- The file disappears from outgoing directory when
ssmsend
is run. - The file appears in receiving SSM's 'incoming' directory if
ssmreceive
is running.
Once the sending and receiving SSMs are configured and running correctly, to send a message, put a file in the correct outgoing directory with the correct name, run ssmsend
, and it will disappear. It will arrive in the incoming directory of the receiving SSM.