Table of Contents

Fedora Middleware

This project is funded by a grant to Cornell University from the Andrew W. Mellon Foundation. The goal of this work is to provide an improved Fedora Repository service and to enable new service integrations in accordance with the principles of Service Oriented Architecture (SOA). This work is motivated by use cases that suggest new models of scientific and scholarly communication. The Fedora Middleware Project will demonstrate reference integrations of middleware products provided in open source which are suitable for use in solutions that include services supplied by Fedora software. Middleware products for consideration and use include messaging products such as JMS providers, Enterprise Service Bus products, Choreography Engines, Business Rules Engines, Workflow/Business Process Execution Engines and Distributed Transaction Managers. No middleware products will be built as part of this project though a select group of best-of-breed integrations will be demonstrated. Both simple, lightweight approaches and enterprise-level approaches will be included as part the project. Also, approaches to management of business/mission semantics, message formats and governance issues will be considered.

Feature Action Availability Notes
FR A T M FM O Q108 Q208 Q308 Q408 2009
Mellon ESB Study I D D X – Group study of open source offerings for Enterprise Service Bus (informs design)
RepoMMan Support I D D X – Informs design; possible re-use or re-distribution of components or examples
-- http://www.hull.ac.uk/esig/repomman/
Messaging (JMS) Integration I D I X – Repository as publisher of Events in Atom
GSearch JMS Subscriber I D I X – Search service automatically updated via JMS
Proai JMS Subscriber I D I X – OAI provider service automatically updated via JMS
Lightweight Pipeline Ingest I D I X – Both attached content and referenced content
Lightweight Workflow (BPE) I D I X
Middleware Security I D I X – Includes XACML and other technologies
-- Likely will use several community partners
JTA Compliance I D I X – Requires Repository and Akubra JTA compliance
-- Middleware Transaction Manager
Enterprise integration: Workflow/BPE within ESB for Preservation and Archiving I D I X This will be driven by user demand; If lightweight approaches meet requirements, we may re-evaluate.


Legend
Project FR – Fedora Repository Project A – Akubra Project T – Topaz Project M – Mulgara Project FM – Fedora Middleware Project O – Other independent open source projects
Action D – Develops Software I – Integrates Software
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels