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/Server"
| Line 19: | Line 19: | ||
* [[APEL/SSMOverview|SSM Overview]] | * [[APEL/SSMOverview|SSM Overview]] | ||
* [[APEL/SSMInstallation|SSM installation instructions]] | * [[APEL/SSMInstallation|SSM installation instructions]] | ||
* [[APEL/SSMProblems|Common SSM probems]] | |||
== Record loader == | == Record loader == | ||
Revision as of 15:20, 7 July 2011
This page is under construction and is not yet complete.
APEL STOMP Testing
APEL SSM Testing: If you are interested in testing the new STOMP interface or want to develop your own client.
APEL Server Design
The new APEL server is written in Python. Its design is described in APEL Server Design. It has four components:
- SSM
- Record loader
- Record publisher
- Authentication
APEL Message Format
SSM
The SSM is the messaging system used by APEL to transmit messages. It is written in Python and uses the STOMP protocol.
Record loader
This has the fairly simple job of taking the received messages and putting them in the database.
Record publisher
This takes the information from a database and produces messages.
Authentication
This verifies that the senders of the messages via the SSM are known to APEL.