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 24: | Line 24: | ||
== Record loader == | == Record loader == | ||
This has the | This has the task of taking the received messages and inserting the records in the database. At present there are three message types defined: | ||
* Job Record messages | |||
* Summary Record messages | |||
* Sync Record messages | |||
The header in the message defines the type of records the message will contain and the version of the format. This will enable us to identify newer versions if they are defined. | |||
This simple model allows the definition of alternative message types for different records which the record loader can then be configured to handle, for example, there will be a SpecIntHistory Record message type. | |||
== Record publisher == | == Record publisher == | ||
Revision as of 12:56, 18 January 2012
This page is under construction and is not yet complete.
APEL Server Design
The new APEL server is written in Python. It has the following components:
- SSM
- Record loader
- Summarizer
- Record publisher
- Authentication
- Monitoring
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.
External SSM Testing
APEL SSM Testing: If you are interested in testing the new STOMP interface or want to develop your own client.
Record loader
This has the task of taking the received messages and inserting the records in the database. At present there are three message types defined:
- Job Record messages
- Summary Record messages
- Sync Record messages
The header in the message defines the type of records the message will contain and the version of the format. This will enable us to identify newer versions if they are defined.
This simple model allows the definition of alternative message types for different records which the record loader can then be configured to handle, for example, there will be a SpecIntHistory Record message type.
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.