Resilient Critical Infrastructure Management using Service Oriented Architecture

Abstract—The SERSCIS project aims to support the use of interconnected systems of services in Critical Infrastructure (CI) applications. The problem of system interconnectedness is aptly demonstrated by ‘Airport Collaborative Decision Making’ (ACDM). Failure or underperformance of any of the interlinked ICT systems may compromise the ability of airports to plan their use of resources to sustain high levels of air traffic, or to provide accurate aircraft movement forecasts to the wider European air traffic management systems. The proposed solution is to introduce further SERSCIS ICT components to manage dependability and interdependency. These use semantic models of the critical infrastructure, including its ICT services, to identify faults and potential risks and to increase human awareness of them. Semantics allows information and services to be described in such a way that makes them understandable to computers. Thus when a failure (or a threat of failure) is detected, SERSCIS components can take action to manage the consequences, including changing the interdependency relationships between services. In some cases, the components will be able to take action autonomously — e.g. to manage ‘local’ issues such as the allocation of CPU time to maintain service performance, or the selection of services where there are redundant sources available. In other cases the components will alert human operators so they can take action instead. The goal of this paper is to describe a Service Oriented Architecture (SOA) that can be used to address the management of ICT components and interdependencies in critical infrastructure systems. Index Terms—resilience; QoS; SOA; critical infrastructure, SLA

Combining SLA prediction and cross layer adaptation for preventing SLA violations

Abstract. Service-based Applications (SBA) are deployed in highly dy-namic and distributed settings, where various parts of the constituent components- services and their infrastructure- are controlled by dif-ferent third parties. In such a loosely coupled environment, adaptation capabilities are needed to manage deviations and unforeseen situations which might lead to negative consequences (e.g. contractual penalties). Current approaches either focus on cross-layer-adaptation or the pre-vention of SLA violations. In contrast to this, the approach presented in this paper combines both. The paper presents an architecture as a generic framework for the management of arising problems during ser-vice execution. Multiple adaptation mechanisms are available to react on adaptation needs, acting on different layers of the SBA (including e.g. the composition layer and the infrastructure layer). The final goal of the cross-layer adaptation capability is to avoid the violation of agreed Service Level (in SLAs) and thus ensure the benefits of SBAs for both customers and providers.

Fault management of web services

The use of service-oriented (SO) distributed systems is increasing. Within service orientation web services (WS) are the de facto standard for implementing service-oriented systems. The consumers of WS want to get uninterrupted and reliable service from the service providers. But WS providers cannot always provide services in the expected level due to faults and failures in the system. As a result the fault management of these systems is becoming crucial. This work presents a distributed event-driven architecture for fault management of Web Services. According to the architecture the managed WS report different events to the event databases. From event databases these events are sent to the event processors. The event processors are distributed over the network. They process the events, detect fault scenarios in the event stream and manage faults in the WS

When Is an Enterprise Service Bus (Esb) the Right Choice for an Integrated Technology Solution?

The Enterprise Service Bus (ESB) is an important systems integration technology often closely associated with Service Oriented Architecture (SOA). Some maintain that an ESB should not be used apart from SOA. Others see the ESB simply as the next generation of middleware, incorporating the best of its predecessors, Enterprise Application Integration (EAI) and Message Oriented Middleware (MOM), and a candidate for any integration requirement. Is the ESB a one-size-fits-all solution to be trusted for any integration requirement, or must its use be carefully considered with proper due diligence based on application complexity and/or the presence or absence of a defined SOA? This thesis probes these questions in an analysis of a world-wide survey of 230 industry SOA and middleware professionals conducted via the LinkedIn Professional Network during a six week period in November and December of 2010. In addition, the thesis applies a review of the survey results and current SOA and ESB literature to an architectural decision being made within the Systems Engineering and Application Development (SEAD) Practicum in the Master of Science program in Computer Information Systems at Regis University in Denver, which provides support for the University\u27s Academic Research Network (ARN). An ESB has been proposed as a new architectural component for the ARN infrastructure and this paper reviews the merit of this proposal. This thesis employs an interpretivist epistemology, understanding that there may be more than one acceptable answer to the question, When is an Enterprise Service Bus an appropriate component of an integrated technology solution

An Enhanced Architecture for LARIISA: An Intelligent System for Decision Making and Service Provision for e-Health using the cloud

International audienceHealth care services can be scarce and expensive in some countries and especially in isolated regions. The lack of information can degrade health care services, for example, by ineffective resource allocation or failure in epidemiological prediction. This paper proposes an architecture for system of decision making and service provisioning in the health care context. It encompasses and integrates data produced by environmental sensors installed in the assisted homes, medical data sets, domain-specific and semantic enriched data sets, and all data generated and collected in applications installed on mobile phones, wearable devices, desktops, web servers, and smart television. LARIISA architecture is presented as a platform to manage, provide and launch services that monitor and analyze data to supply relevant information to decision makers and health care actors that participate in the health care supply chain

Assessing open source communities' health using Service Oriented Computing concepts

© 2014 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes,creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.The quality of Open Source Software products is directly related to its community's health. To date, health analysis is made accessing available data repositories or using software management tools that are often too static or ad hoc. To address this issue, we propose to adopt principles and methods from the Service Oriented Computing field. Particularly, we propose to adapt the concepts of quality service and service level agreement, and propose to reuse the existing body of knowledge and techniques from SOC monitoring. To demonstrate the feasibility of the approach, we use a service monitoring framework called SALMonOSS as a proof of concept to realize the implementation of the proposal.Peer ReviewedPostprint (author's final draft