Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "APEL/SSM"

From EGIWiki
Jump to navigation Jump to search
m
 
(39 intermediate revisions by 4 users not shown)
Line 2: Line 2:
* Back to [[APEL/Server]]
* Back to [[APEL/Server]]


== Secure Stomp Messenger ==
= 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.
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 ====
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'''.
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.
 
For more on testing, see [[APEL/Test_APEL_Server]].
 
 
== Introduction ==
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.
 
 
== SSM2 ==
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.


Key features:
Key features:
* any file can be sent as a message
* any file can be sent as a message
* messages are encrypted in transit, using IGTF X509 certificates
* messages are signed and may be encrypted in transit, using x509 certificates
* all messages are acknowledged by the receiving SSM, so both sides know if a message has been sent
* a receiving SSM acts as a daemon process; a sending SSM runs, sending all its messages, and then quits
* 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
==== Downloads ====
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.


==== Documentation ====
==== Documentation ====
* [[APEL/SSM2Overview|SSM2 Overview]]
* [[APEL/SSM2Installation|SSM2 installation instructions]]
* [[APEL/SSM2Configuration|Configuring SSM2]]
* [[APEL/SSM2AddingFiles|Adding files to SSM2]]
* [[APEL/RunningSSM2|Running SSM2]]


* [[APEL/SSMOverview|SSM Overview]]
[[Category:Accounting]]
* [[APEL/SSMInstallation|SSM installation instructions]]
* [[APEL/SSMConfiguration|Configuring the SSM]]
* [[APEL/RunningSSM|Running the SSM]]
* [[APEL/SSMProblems|Common SSM problems]]
 
==== 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.

Latest revision as of 18:14, 1 November 2018

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.


Introduction

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.


SSM2

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.

Key features:

  • 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

Downloads

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.

Documentation