Systems integration with DLSI

Systems integration aims to provide a homogenous view to a system consisting of many heterogeneous systems. Systems integration can be achieved by many means out of which the middleware approach is the most popular. This is because middleware can be built around existing systems thereby reducing the amount of changes needed for the integration. Nowadays many middleware technologies are available to integrate heterogeneous systems. One can chose among them depending upon the requirements. But due to the many technologies available for Middleware, a muddle of middleware exists. To reduce this muddle and to integrate the systems already implemented using different middleware technologies, Web Services plays a key role. Web Services is an XML-based technology which uses known protocols to communicate between applications, thus making them platform and technology independent. Digital Library Service Integration (DLSI) provides a systematic approach in integrating the digital library collections and services. Amazon\u27s website www.amazon.com is integrated with DLSI such that users see the same web pages as they see when they are logged in normally, but these pages will be augmented with link anchors. Wrappers will parse the web pages to look for elements of interests like book title, author name, etc., and provide them with link anchors which will connect the user to the library at New Jersey Institute of Technology where he or she can search for books or request them through interlibrary loan. The thesis proposes a new architecture for the DLSI as a web service, which can provide this functionality

Ecosystem Competition and the Antitrust Laws

I. Introduction II. Three Examples of Ecosystem Competition ... A. Middleware and Operating Systems ... B. E-Books and Tablets … C. Connected and Automated Vehicles III. How Ecosystem Competition Enhances Consumer Welfare IV. Implications for Antitrust Law and Polic

Middleware’s message : the financial technics of codata

In this paper, I will argue for the relevance of certain distinctive features of messaging systems, namely those in which data (a) can be sent and received asynchronously, (b) can be sent to multiple simultaneous recipients and (c) is received as a “potentially infinite” flow of unpredictable events. I will describe the social technology of the stock ticker, a telegraphic device introduced at the New York Stock Exchange in the 1860s, with reference to early twentieth century philosophers of synchronous experience (Bergson), simultaneous sign interpretations (Mead and Peirce), and flows of discrete events (Bachelard). Then, I will show how the ticker’s data flows developed into the 1990s-era technologies of message queues and message brokers, which distinguished themselves through their asynchronous implementation of ticker-like message feeds sent between otherwise incompatible computers and terminals. These latter systems’ characteristic “publish/subscribe” communication pattern was one in which conceptually centralized (if logically distributed) flows of messages would be “published,” and for which “subscribers” would be spontaneously notified when events of interest occurred. This paradigm—common to the so-called “message-oriented middleware” systems of the late 1990s—would re-emerge in different asynchronous distributed system contexts over the following decades, from “push media” to Twitter to the Internet of Things

Seleclting Middleware for N-tier applications

This paper describes middleware for n-tier architecture, describes how this middleware is meeting the unique demands of Internet applications and e-commerce, and suggests selection guidelines to assist business managers in choosing appropriate types of middleware for n-tier systems that will meet their internet needs. Different types of middleware provide the functionality for addressing many distinct and disparate problems arising from the distributed processing associated with n-tier systems. This paper associates the type of middleware with the nature of the system being developed

Ecosystem Competition and the Antitrust Laws

Conventional antitrust norms analyze market power—as a stepping stone to anticompetitive effects and, hence, prohibited conduct—from the perspective of product substitutability. Two goods or services are said to compete with one another when they are reasonably interchangeable from the perspective of consumers, or to put it in more formal economic terms, when there is cross-elasticity of demand between them. Conversely, when two goods or services are not reasonably interchangeable, they are not horizontally related and are said not to compete with one another. Since a concern over horizontal agreements and horizontal effects dominate antitrust—courts even analyze vertical agreement or merger cases in terms of their horizontal effects—proof of effects among substitutable goods or services is a crucial touchstone of antitrust analysis

Dimensions of coupling in middleware

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

Dimensions of coupling in middleware

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

A new competetive advantage over the cloud

CEM

JSB Composability and Web Services Interoperability Via Extensible Modeling & Simulation Framework (XMSF), Model Driven Architecture (MDA), Component Repositories, and Web-based Visualization

Study Report prepared for the U. S. Air Force, Joint Synthetic Battlespace Analysis of Technical Approaches (ATA) Studies & Prototyping Overview: This paper summarizes research work conducted by organizations concerned with interoperable distributed information technology (IT) applications, in particular the Naval Postgraduate School (NPS) and Old Dominion University (ODU). Although the application focus is distributed modeling & simulation (M&S) the results and findings are in general easily applicable to other distributed concepts as well, in particular the support of operations by M&S applications, such as distributed mission operations. The core idea of this work is to show the necessity of applying open standards for component description, implementation, and integration accompanied by aligned management processes and procedures to enable continuous interoperability for legacy and new M&S components of the live, virtual, and constructive domain within the USAF Joint Synthetic Battlespace (JSB). JSB will be a common integration framework capable of supporting the future emerging simulation needs ranging from training and battlefield rehearsal to research, system development and acquisition in alignment with other operational requirements, such as integration of command and control, support of operations, integration of training ranges comprising real systems, etc. To this end, the study describes multiple complementary Integrated Architecture Framework approaches and shows, how the various parts must be orchestrated in order to support the vision of JSB effectively and efficiently. Topics of direct relevance include Web Services via Extensible Modeling & Simulation Framework (XMSF), the Object Management Group (OMG)’s Model Driven Architecture (MDA), XML-based resource repositories, and Web-based X3D visualization. To this end, the report shows how JSB can − Utilize Web Services throughout all components via XMSF methodologies, − Compose diverse system visualizations using Web-based X3D graphics, − Benefit from distributed modeling methods using MDA, and − Best employ resource repositories for broad and consistent composability. Furthermore, the report recommends the establishment of necessary management organizations responsible for the necessary alignment of management processes and procedures within the JSB as well as with neighbored domains. Continuous interoperability cannot be accomplished by technical standards alone. The application of technical standards targets the implementation level of the system of systems, which results in an interoperable solution valid only for the actual 2 implementation. To insure continuity, the influence of updates, upgrades and introduction of components on the system of systems must be captured in the project management procedures of the participating systems. Finally, the report proposes an exemplifying set of proof-of-capability demonstration prototypes and a five-year technical/institutional transformation plan. All key references are online available at http://www.movesinstitute.org/xmsf/xmsf.html (if not explicitly stated otherwise)

Community Core Evolution in Mobile Social Networks

Community detection in social networks attracts a lot of attention in the recent years. Existing methods always depict the relationship of two nodes using the temporary connection. However, these temporary connections cannot be fully recognized as the real relationships when the history connections among nodes are considered. For example, a casual visit in Facebook cannot be seen as an establishment of friendship. Hence, our question is the following: how to cluster the real friends in mobile social networks? In this paper, we study the problem of detecting the stable community core in mobile social networks. The cumulative stable contact is proposed to depict the relationship among nodes. The whole process is divided into timestamps. Nodes and their connections can be added or removed at each timestamp, and historical contacts are considered when detecting the community core. Also, community cores can be tracked through the incremental computing, which can help to recognize the evolving of community structure. Empirical studies on real-world social networks demonstrate that our proposed method can effectively detect stable community cores in mobile social networks