From service-oriented architecture to service-oriented enterprise

Service-Oriented Architecture (SOA) was originally motivated by enterprise demands for better business-technology alignment and higher flexibility and reuse. SOA evolved from an initial set of ideas and principles to Web services (WS) standards now widely accepted by industry. The next phase of SOA development is concerned with a scalable, reliable and secure infrastructure based on these standards, and guidelines, methods and techniques for developing and maintaining service delivery in dynamic enterprise settings. In this paper we discuss the principles and main elements of SOA. We then present an overview of WS standards. And finally we come back to the original motivation for SOA, and how these can be realized

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

INTEGRATION VERSUS DEDICATION IN ROMANIAN MANAGEMENT SUPPORT SYSTEMS

The technologies supporting future business must be intuitive from a user standpoint, flexible from design standpoint and highly productive. As an answer to many requirements, analysts recommend the inclusion of SOA and ESB in the IT management strategies, since these tend to become mainstream, overcoming their abstract vision status in the last decade. In this paper, we provide a study regarding the attitude of companies from north-western Romania with respect to this transition and the SOA&ESB models. Our analysis targets attributes such as: level of understanding, knowledge and concern in adopting such technologies, the management involvement in the company IT strategy, the added value of the new technologies and risk factors for the migration towards an SOA&ESB architecture.integration,enterprise applications,web applications,SOA,ESB,framework