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 23: | Line 23: | ||
This verifies that the senders of the messages via the SSM are known to APEL. | This verifies that the senders of the messages via the SSM are known to APEL. | ||
* APEL/UsingAuth | * [[APEL/UsingAuth]] | ||
Revision as of 16:53, 14 April 2011
This page is under construction and is not yet complete.
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
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.