EMI Messaging


Messaging services are common component in industrial distributed systems, and solutions based on such services have been used for high-level cross-grid applications for a while. Recently this technology has been adopted within the EGEE infrastructure as an integration framework for service monitoring and other operational tools including accounting, ticketing and operational dashboards. It also has been used for publishing event logs from gLite middleware components.

So far, Apache ActiveMQ, has been used for this work as it was seen as the most mature messaging open-source implementation available at the time of implementation that provided the required support in terms of reliability, stability, scalability and access from clients in multiple languages. ActiveMQ has also been used by NDGF to change the communications mechanism in dCache.

The goals of the EMI Messaging Product Team are to:

  • collate messaging requirements from the other EMI Product Teams
  • analyse the available messaging solutions with regard to these requirements
  • recommend which solution(s) to use within EMI
  • provide the necessary additional software (tools, libraries...) to run a messaging service on top of existing software
  • provide consultancy, guidelines, best practices, examples... to help other product teams with messaging integration

Other wiki pages describe more formally the work and the objectives.


Components are still in design phase so there are not products yet.


You can find very useful information about messaging on the CERN IT/GT/TOM messaging wiki, in particular the introductory pages:

The EMI 2010 All Hands Meeting included a Messaging Workshop. You can find interesting information in the slides presented there (they are all in Indico). See in particular the slides from the Crash course on messaging.

In addition, here are some EMI-specific documents:

Work Plan

Year 1:

  • collate messaging requirements from the other EMI Product Teams
  • perform a paper survey of the various options for an EMI messaging service
  • provide messaging introductory information including guidelines

Year 2:

  • based on the requirements from year 1 as well as practical tests, recommend which messaging solution(s) should be used within EMI
  • prototype the additional software that complements the chosen messaging solution(s)
  • provide consultancy to help the other product teams with messaging integration
  • improve the messaging documentation with best practices and examples

Year 3:

  • develop and document the additional software part of the EMI messaging solution(s)
  • provide consultancy to help the other product teams with messaging integration
  • improve and finalise the messaging documentation

See also the Clarification from the F2F meeting at CERN.


  • Lionel Cons (CERN)


Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf 20110419_EMI-MessagingPT-Guidelines.pdf r1 manage 503.0 K 2012-05-10 - 15:08 MassimoPaladin 20110419 EMI MessagingPT - Guidelines
PDFpdf 20110530_EMI-MessagingPT-Status.pdf r1 manage 753.6 K 2012-05-10 - 15:07 MassimoPaladin 20110530 EMI MessagingPT - Status
PDFpdf 20111018_EMI-MessagingPT-report.pdf r1 manage 262.8 K 2012-05-10 - 15:06 MassimoPaladin 20111018 EMI MessagingPT - report
PDFpdf 2012-03-27_EMI_Messaging_Software.pdf r1 manage 876.4 K 2012-05-10 - 15:05 MassimoPaladin 2012-03-27_EMI_Messaging_Software
PDFpdf EMI-JRA-MESSAGING-SOLUTIONS-TECHNICAL-EVALUATION-v1_0_0.FINAL.pdf r1 manage 476.9 K 2011-09-27 - 12:00 MassimoPaladin Enterprise Messaging Solutions Technical Evaluation
PDFpdf EMI-JRA-MESSAGING_SOLUTIONS_SURVEY-v1_0.FINAL.pdf r1 manage 1808.5 K 2011-04-07 - 15:50 MassimoPaladin Enterprise Messaging Solutions Survey
Edit | Attach | Watch | Print version | History: r21 < r20 < r19 < r18 < r17 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r21 - 2012-05-10 - MassimoPaladin
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback