Author | Conference | Journal | Organization | Year | DOI
Look for results that meet for the following criteria:
Academic
Publications
A COMPONENT-BASED FRAMEWORK FOR INTEGRATED MESSAGING SERVICES

A COMPONENT-BASED FRAMEWORK FOR INTEGRATED MESSAGING SERVICES,George N. Kogiomtzis,Drakoulis Martakos

Edit
A COMPONENT-BASED FRAMEWORK FOR INTEGRATED MESSAGING SERVICES  
BibTex | RIS | RefWorks Download
In the last decade companies focus on building enterprise-wide messaging and communication infrastructures in order to meet the ever-increasing requirements for inter- and intra-enterprise communications. In this perspective, enterprise services are crafted to facilitate and improve the communications within the enterprise, with the goal of reducing the overall cost of communication for the enterprise as a single entity. Towards this direction, they continue to evolve towards a core set of standards and capabilities that will offer organizations benefits such as universal interoperability, network convergence, end-to-end media fidelity and high reliability. Communications and messaging in information systems development, an ever growing and rapidly changing milieu itself, have nowadays become the fastest growing kind of middleware and are constantly being extended to support new technologies and infrastructures as they emerge. The exchange of application data that support day-to-day transactions and activities lies beyond a simple file transfer or transmission of an email message. As a result, the existence of a sophisticated communications infrastructure is often highly desirable by both small companies and large enterprises with numerous business units dispersed all over the world. In this paper, we propose a well-defined communication management system architecture that supports application integration across diverse business environments and applications. It has been developed as part of a wider Enterprise Business Operating System (EBOS) architecture, with the aim of integrating business-related artefacts (modelled as messages) with any information modelled in EBOS, such as purchase orders, customer records and invoices. It should be noted however that it represents a generic, open middleware architecture that can be applied in a variety of organizational models, similar to EBOS, regardless of the purpose, content and structure of the information to be transmitted. Any further reference of the EBOS architecture specifics is *
Cumulative Annual
View Publication
The following links allow you to view full publications. These links are maintained by other sources not affiliated with Microsoft Academic Search.
Share this on