loading...
TUBE: Automated Protocol-Level Middleware Interoperation
March 26-March 28
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ASWEC.2008.1919th Australian Conference on Softwar ...
 This Article 
 
PDF
HTML
IEEE Xplore Subscribers
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Following changes in business processes and technology enterprises often need to interoperate protocols of heterogeneous middleware. This paper presents an automated, data-driven approach to protocol-level middleware interoperation, based on declarative descriptions of these protocols. The??run-time engine of TUBE (The Ubiquitous Broker Environment), provides a layer between application-level components and middleware that allows a degree of independence from particular middleware implementations by taking protocol descriptions and performing the necessary translations. The TUBE framework is designed to try alternatives if the searched protocol is unavailable, making it easy to deploy different types of middleware and special protocol extensions.???TUBE has been implemented and successfully tested across a range of commonly used middleware, including synchronous, asynchronous, object-based, binary and text-based protocols. Key components of the system are currently in operation in a large Australian corporation.
Index Terms:
Middleware, Midddleware interoperation, Systems integration
Citation:
Richard Slamkovic, George Fernandez, Jim McGovern, "TUBE: Automated Protocol-Level Middleware Interoperation," aswec, pp.120-129, 19th Australian Conference on Software Engineering (aswec 2008), 2008
Usage of this product signifies your acceptance of the Terms of Use.


Suggestions