|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
19th Australian Conference on Software Engineering (aswec 2008)
TUBE: Automated Protocol-Level Middleware Interoperation
March 26-March 28
ISBN: 978-0-7695-3100-7
| ASCII Text | x | ||
| Richard Slamkovic, George Fernandez, Jim McGovern, "TUBE: Automated Protocol-Level Middleware Interoperation," Software Engineering Conference, Australian, pp. 120-129, 19th Australian Conference on Software Engineering (aswec 2008), 2008. | |||
| BibTex | x | ||
| @article{ 10.1109/ASWEC.2008.19, author = {Richard Slamkovic and George Fernandez and Jim McGovern}, title = {TUBE: Automated Protocol-Level Middleware Interoperation}, journal ={Software Engineering Conference, Australian}, volume = {0}, year = {2008}, issn = {1530-0803}, pages = {120-129}, doi = {http://doi.ieeecomputersociety.org/10.1109/ASWEC.2008.19}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - Software Engineering Conference, Australian TI - TUBE: Automated Protocol-Level Middleware Interoperation SN - 1530-0803 SP120 EP129 A1 - Richard Slamkovic, A1 - George Fernandez, A1 - Jim McGovern, PY - 2008 KW - Middleware KW - Midddleware interoperation KW - Systems integration VL - 0 JA - Software Engineering Conference, Australian ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ASWEC.2008.19
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.
