874 research outputs found

    Upon a Message-Oriented Trading API

    Get PDF
    In this paper, we introduce the premises for a trading system application-programming interface (API) based on a message-oriented middleware (MOM), and present the results of our research regarding the design and the implementation of a simulation-trading system employing a service-oriented architecture (SOA) and messaging. Our research has been conducted with the aim of creating a simulation-trading platform, within the academic environment, that will provide both the foundation for future experiments with trading systems architectures, components, APIs, and the framework for research on trading strategies, trading algorithm design, and equity markets analysis tools. Mathematics Subject Classification: 68M14 (distributed systems).Trading System API, Straight-Through Processing, Distributed Computing, Service-Oriented Architecture (SOA), Message-Oriented Middleware (MOM), Java Message Service (JMS), OpenMQ

    Dimensions of coupling in middleware

    Get PDF
    It is well accepted that different types of distributed architectures require different degrees of coupling. For example, in client-server and three-tier architectures, application components are generally tightly coupled, both with one-another and with the underlying middleware. Meanwhile, in off-line transaction processing, grid computing and mobile applications, the degree of coupling between application components and with the underlying middleware needs to be minimised. Terms such as "synchronous", "asynchronous", "blocking", "non-blocking", "directed", and "non-directed" are often used to refer to the degree of coupling required by an architecture or provided by a middleware. However, these terms are used with various connotations. And while various informal definitions have been provided, there is a lack of an overarching formal framework to unambiguously communicate architectural requirements with respect to (de-)coupling. This article addresses this gap by: (i) formally defining three dimensions of (de-)coupling; (ii) relating these dimensions to existing middleware; and (iii) proposing notational elements to represent various coupling integration patterns. This article also discusses a prototype that demonstrates the feasibility of its implementation

    Context-aware Authorization in Highly Dynamic Environments

    Get PDF
    Highly dynamic computing environments, like ubiquitous and pervasive computing environments, require frequent adaptation of applications. Context is a key to adapt suiting user needs. On the other hand, standard access control trusts users once they have authenticated, despite the fact that they may reach unauthorized contexts. We analyse how taking into account dynamic information like context in the authorization subsystem can improve security, and how this new access control applies to interaction patterns, like messaging or eventing. We experiment and validate our approach using context as an authorization factor for eventing in Web service for device (like UPnP or DPWS), in smart home security

    Distributing Real Time Data From a Multi-Node Large Scale Contact Center Using Corba

    Get PDF
    This thesis researches and evaluates the current technologies available for developing a system for propagation of Real-Time Data from a large scale Enterprise Server to large numbers of registered clients on the network. The large scale Enterprise Server being implemented is a Contact Centre Server, which can be a standalone system or part of a multi-nodal system. This paper makes three contributions to the study of scalable real-time notification services. Firstly, it defines the research of the different technologies and their implementation for distributed objects in today\u27s world of computing. Secondly, the paper explains how we have addressed key design challenges faced when implementing a Notification Service for TAO, which is our CORBA-compliant real-time Object Request Broker (ORB). The paper shows how to integrate and configure CORBA features to provide real-time event communication. Finally, the paper analyzes the results of the implementation and how it compares to existing technologies being used for the propagation of Real-Time Data

    Coupling as a trade-off in an Enterprise Service Bus

    Get PDF
    Traditionally, integration problems between IT systems were solved by point-to-point connections. These point-to-point connections pose issues with scalability, reliability, and flexibility. To overcome these issues, companies typically invest in Enterprise Application Integration (EAI) using an Enterprise Service Bus (ESB) to integrate the IT systems through a central middleware infrastructure. EAI promises improvement of scalability, reliability, and flexibility by implementing loosely coupled integration solutions to realise loosely coupled IT systems. By wrongly implementing EAI on an ESB IT systems may still be tightly coupled and the issues with point-to-point connections could be recreated on the ESB. Currently there is no out-of-the-box solution to identify the integration solution where tight coupling causes these issues. The goal of this research is to investigate an approach to identify the coupling state in an Enterprise Service Bus and identify the integration solutions on an ESB which have a negative impact on the quality attributes due to tight coupling. The first step in the approach is applying a set of properties on the integration solutions to identify their coupling state. Manually identifying the coupling state is labour intensive, so it is automated by implementing a prototype with the Eclipse MoDisco framework. The second step in the approach is evaluating a trade-off between the risk of being in a certain coupling state and the efficiency loss of migrating to a less risky coupling state. With the outcome of the trade-off it can be ascertained whether or not it is beneficial to migrate to a different coupling state. The result of the approach is a list of integration solutions for which it would be beneficial to migrate to a different coupling state. This gives a concrete measure to be able to determine which integration solutions need to be improved to strive for the optimal balance between quality and the effort needed to realise quality. The approach was validated using the ESB implementation of a large European airport as a case study

    Environmental Observing Systems for Assessing Impacts of Land Use Change

    Get PDF
    The purpose of this research is to evaluate the application of technology solutions for enabling environmental research. This project develops a complete environmental observing system in support of an investigation of the hydrological and ecological impacts of land use change on the coast of South Carolina. The land use change study is an ongoing multi-disciplinary effort involving the collection of a large number of monitored and sampled parameters at Bannockburn Plantation, which is located near the City of Georgetown in South Carolina. Long term monitoring will support a hydrological and ecological assessment of the study site before, during, and after proposed residential and commercial development. There are three primary objectives of this work. The first is the comprehensive instrumentation of a portion of the Bannockburn study site for hydrological parameters. The second is the implementation of a wireless sensor network to support the remote acquisition of monitored data. The third objective is the creation of a reliable and robust software solution for transmitting and distributing real time observation data. Collectively, these three objectives provide a complete environmental observing system. Results of this work will benefit land use change research by providing access to real time observation data and enabling the integration of powerful analysis tools. This research will provide a basis for the development of future environmental observation systems

    A Service-Oriented Approach for Network-Centric Data Integration and Its Application to Maritime Surveillance

    Get PDF
    Maritime-surveillance operators still demand for an integrated maritime picture better supporting international coordination for their operations, as looked for in the European area. In this area, many data-integration efforts have been interpreted in the past as the problem of designing, building and maintaining huge centralized repositories. Current research activities are instead leveraging service-oriented principles to achieve more flexible and network-centric solutions to systems and data integration. In this direction, this article reports on the design of a SOA platform, the Service and Application Integration (SAI) system, targeting novel approaches for legacy data and systems integration in the maritime surveillance domain. We have developed a proof-of-concept of the main system capabilities to assess feasibility of our approach and to evaluate how the SAI middleware architecture can fit application requirements for dynamic data search, aggregation and delivery in the distributed maritime domain

    The many faces of publish/subscribe

    Get PDF
    Well adapted to the loosely coupled nature of distributed interaction in large-scale applications, the publish/subscribe communication paradigm has recently received increasing attention. With systems based on the publish/subscribe interaction scheme, subscribers register their interest in an event, or a pattern of events, and are subsequently asynchronously notified of events generated by publishers. Many variants of the paradigm have recently been proposed, each variant being specifically adapted to some given application or network model. This paper factors out the common denominator underlying these variants: full decoupling of the communicating entities in time, space, and synchronization. We use these three decoupling dimensions to better identify commonalities and divergences with traditional interaction paradigms. The many variations on the theme of publish/subscribe are classified and synthesized. In particular, their respective benefits and shortcomings are discussed both in terms of interfaces and implementations
    corecore