{"title":"自动协议级中间件互操作","authors":"R. Slamkovic, G. Fernandez, J. McGovern","doi":"10.1109/ASWEC.2008.19","DOIUrl":null,"url":null,"abstract":"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.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"35 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"TUBE: Automated Protocol-Level Middleware Interoperation\",\"authors\":\"R. Slamkovic, G. Fernandez, J. McGovern\",\"doi\":\"10.1109/ASWEC.2008.19\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"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.\",\"PeriodicalId\":231903,\"journal\":{\"name\":\"19th Australian Conference on Software Engineering (aswec 2008)\",\"volume\":\"35 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2008-03-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"19th Australian Conference on Software Engineering (aswec 2008)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ASWEC.2008.19\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"19th Australian Conference on Software Engineering (aswec 2008)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ASWEC.2008.19","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
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.