This thesis is focused on service in frame of enterprise computing and composition of these services. This brings a number of issues in large spectra of perspectives and this thesis has the ambition these issues resolve. The goal of this thesis is considering the principles application of service oriented architecure and standard methodologies in composition of internally managed by process complex business service, which composes services in SAP information system and which use resources of IBM WebSphere Process Server and IBM WebSphere ESB Server. The basic presumption to goal achieve is precise identification and definition of service. Also important is the notion of composition. So what are especially logical links between services. Based on this service identification it is going to be clarified the options of its composition and it is going to be specified the importance of service definition and composition in enterprise computing area. After defining the services in computing context the thesis is going to be focused on composite business services. Composite business services are going to be analyzed from three perspectives: Engineering, Management and Governance. The benefit of thesis is answer to question if it is possible in specific environment with specific conditions to compose business services, which respect the criterions of three perspectives: Engineering, Management and Governance. If the composition of those business services will respect generally respected standards and recommendations in a defined environment. Thesis in its structure passes from general knowledge about services to knowledge about services in frame of enterprise computing. This knowledge is based on analysis and recommendations of methodologies which are focused on service oriented IT management. Knowledge of this analysis are became basis for definition of three perspectives. Principles defined in three perspectives are going to be verified in real experiment.

Esta tese tem como objetivo o projeto e implementação de uma arquitetura orientada a serviços, denominada WSARCH - Web Services Architecture, que possibilita acesso a Web Services com Qualidade de Serviço (QoS). Os atributos de QoS que devem ser considerados, visando à avaliação de desempenho deWeb services e a obtenção de QoS em uma arquitetura orientada a serviços, são identificados e discutidos. Esses atributos de QoS são mapeados para os componentes participantes de uma arquitetura orientada a serviços que incorpora qualidade de serviço. A arquitetura proposta prevê a monitoração dos provedores de serviços e um módulo que utiliza os dados obtidos para a localização do serviço apropriado. Visando a validação da arquitetura proposta e dos atributos definidos desenvolveu-se um protótipo da WSARCH. O protótipo desenvolvido permite que estudos de avaliação de desempenho sejam realizados considerando os diferentes componentes da arquitetura, algoritmos, protocolos e padrões. A proposta da WSARCH se insere em um contexto em que é importante definir como deve ser projetada uma arquitetura SOA com foco em desempenho, uma vez que a correta caracterização do que avaliar, e como avaliar, se faz necessário. Nesta tese, a avaliação de desempenho está focada nas diferentes entidades que participam de uma arquitetura orientada a serviço: cliente, provedor e os demais participantes / This thesis aims at the design and implementation of a service-oriented architecture, named WSARCH - Web Services Architecture, which allows accessing Web Services with Quality of Service (QoS). The attributes of QoS that shall be considered, aiming at evaluating the performance of Web Services in order to achieve QoS in a service-oriented architecture are identified and discussed. These QoS attributes were mapped to the components participating in a service-oriented architecture that incorporates quality of service. The proposed architecture provides the monitoring of service providers and a module that uses the data to locate the appropriate service. Aiming at the validation of the proposed architecture and the set of attributes proposed, a prototype of WSARCH was developed. The prototype allows performance evaluation studies being conducted considering the different components of the architecture, algorithms, protocols and standards. The proposal of WSARCH is inserted in a context where is important to define how a SOA architecture focusing on performance shall be designed, since the correct characterization of what to evaluate, and how to evaluate is necessary. In this thesis, the evaluation of performance is focused on the different entities participating in a service-oriented architecture: client, provider and other participants

Teleworking is the key to a more flexible design of working time and places of work. To reach the flexibility for working anywhere and anytime a virtual working environment is needed which is reached from any place having a browser and internet access, at home, on the road or in the office. The goal of our activities is to develop a set of technologies fitting in the web architecture in order to bring teleworking applications to their full potential. Our new concept is to combine different web services in a new integrated man-machine environment that enables access to all necessary services. So it will be easier for the teleworker to handle the different applications and techniques. The teleworking portal provides them access to various resources: office applications, multimedia objects and documents, communication tools such as email and conferences, collaboration and group work systems or educational software and training tools. In order to promote interoperability and extensibility among these applications, as well as to allow them to be combined to perform more complex operations, a standard reference architecture for such services is needed. Consequently our approach is based on the Service Oriented Architecture (SOA) and the web service technology. / Telearbeit ist der Schlüssel zu einer flexibleren Arbeitsplatz- und Arbeitszeitgestaltung und eröffnet vielfältige Möglichkeiten und ökonomische Potentiale. Nach zahlreichen Kontroversen über die Vor- und Nachteile haben vor allem die Entwicklung kostengünstiger Informations- und Kommunikationstechniken, aber auch der Handlungsdruck einer zunehmend globalisierten Wirtschaft das Thema Telearbeit in den letzten Jahren neu belebt. Im Rahmen vorangegangener Projekte wurden vielfältige Forschungen zum Thema Telearbeit durchgeführt. Bei der bisherigen Umsetzung von Telearbeit in der Praxis ergaben sich vor allem Probleme im Umgang mit den verschiedenen Arbeitsumgebungen im Büro und am Telearbeitsplatz und dem Abgleich der Arbeitsstände und -ergebnisse. Ziel der Arbeit ist die prototypische Entwicklung einer webbasierten, flexiblen und modular aufgebauten Arbeitsumgebung, die eine effektive Anpassung an die Arbeitsweise des jeweiligen Telearbeiters und Unternehmens ermöglicht. Dabei wurde neben der Definition und Anforderungsanalyse von Telearbeit ein Architekturmodell für eine integrierte Arbeitsumgebung entworfen. Durch die umgesetzte Bausteinarchitektur wird eine flexible Anpassung der Umgebung an die Bedürfnisse der Telearbeiter und der Unternehmen erreicht. Weiterhin werden im Rahmen der Arbeit existierende Ansätze zur Unterstützung von Telearbeit analysiert und klassifiziert, um die eigene Arbeit abzugrenzen. Zur praktischen Umsetzung des Konzeptes wurden vorhandene internetbasierte Protokolle auf ihre Nutzbarkeit für Telearbeitsumgebungen untersucht. Als sehr gut geeignete und innovative Technologien erwiesen sich die Web Services. Deshalb werden die Basisprotokolle und grundlegenden Technologien für Web-Service-Lösungen im Rahmen der Arbeit spezifiziert und auf ihre Nutzbarkeit im Telearbeitskontext untersucht. Abschließend erfolgte eine prototypische Umsetzung der vorgeschlagenen Lösung und eine Validierung in verschiedenen Anwendungsszenarien, um die Praxistauglichkeit des Konzeptes nachweisen zu können.

This document is especially aimed at web services technologies and testing them using fault injection methods. The work deals with Service-Oriented Architecture, used as a standard for web service implementation, and with software testing in general. Practical part of the project includes the design and realization of a tool, which is able to test the most common types of web services according to setup criteria. To demonstrate its functionality, some of the sample and public web services were tested.

Supply chains in many industries are experiencing an ever-growing complexity. They involve many actors and, similar to intra-organizational processes, visibility is an important enabler for managing supply chains in an inter-organizational setting. It is the backbone of advanced sup-ply chain (event) management solutions, which serve to detect critical incidents in time and to determine alternative actions. Due to the numerous parties involved, distributed supply chains call for a modular system architecture that aims at re-using visibility data from standardized sources. Following the wide variety of supply chain configurations in many industries there are also many options to design such services. This paper sheds light on these aspects by conduct-ing a case study on EPCIS, a global service specification for capturing and sharing visibility data. Based on three implementations, it shows the main design options for a supply chain vis-ibility service, generic operator models as well as major potentials.:1. Introduction and motivation 2. Research questions and methodology 3. Literature analysis 4. EPCIS case study 4.1. Deutsche Post DHL 4.2. ThyssenKrupp 4.3. GS1 Germany 5. Discussion and findinds 5.1.Design options 5.2. Operator models 5.3. Potentials 6. Conclusions

Integrationsprojekte sind ein wichtiger Bestandteil einer anpassungsfähigen Informationstechnologie und für einen flexiblen Geschäftsbetrieb unumgänglich. Gerade im Großrechnerbereich besteht ein wachsender Bedarf an Modernisierungsmöglichkeiten für Altanwendungen. Dieser Artikel beleuchtet einen von IBM verfolgten Ansatz zur Modernisierung von Legacy-Anwendungen und diskutiert die nötigen Schritte, um Altanwendungen auf den neusten Stand zu bringen. Das Service Flow Feature (SFF) bietet einen interessanten Ansatz zur Modernisierung von Legacy CICS-Anwendungen (CICS: Customer Information Control System), weil bereits laufende Anwendungen weiterverwendet und in vorhandene Architekturen integriert werden können. Zudem werden bessere Modernisierungsmöglichkeiten bereitgestellt als lediglich die Anpassung der Oberfläche. Hinzu kommt, dass mehrere CICS-Anwendungen aggregiert werden können und die damit erzeugten Geschäftsprozesse über offene Schnittstellen erreichbar sind. Gleichzeitig findet eine Entkopplung der Präsentationslogik von der Anwendungslogik statt. Letzteres bietet dem Entwickler die Möglichkeit, modernere Methoden der Präsentationslogik wie z.B. mittels JSP zu implementieren. Über den Einsatz des CICS SFF in der Entwicklungsumgebung RDz besteht für Firmen kurz- bis mittelfristig die Chance, ihr Reservoire an Legacy CICS-Anwendungen mit relativ wenig Aufwand den modernen IT-Anforderungen anzupassen. / Integration projects are importent elements of a flexible information technology and essential for a flexible business concern. Current discussions show that even in the field of mainframe computing, an increasing need of modernisation possibilities for Legacy applications exist. This article highlights an IBM pursued method to modernize such applications and discusses the necessary steps to make them up-to-date again. The Service Flow Feature delivers an interesting modernization method for Legacy CICS (Customer Information Control System) applications because it reuses and integrates existing applications in available architectures. Furthermore it delivers more possibilities than only modernizing the user interface. In addition, it can aggregate multiple CICS applications, which forms business processes, that are accessible via open interfaces. At the same time, an uncoupling of the presentation logic from the application logic takes place.

Die Strukturierung und Nutzung von unternehmensinternen IT-Infrastrukturen auf Grundlage dienstorientierter Architekturen (SOA) und etablierter XML-Technologien ist in den vergangenen Jahren stetig gewachsen. Lag der Fokus anfänglicher SOA-Realisierungen auf der flexiblen Ausführung klassischer, unternehmensrelevanter Geschäftsprozesse, so bilden heutzutage zeitnahe Datenanalysen sowie die Überwachung von geschäftsrelevanten Ereignissen weitere wichtige Anwendungsklassen, um sowohl kurzfristig Probleme des Geschäftsablaufes zu identifizieren als auch um mittel- und langfristige Veränderungen im Markt zu erkennen und die Geschäftsprozesse des Unternehmens flexibel darauf anzupassen. Aufgrund der geschichtlich bedingten, voneinander unabhängigen Entwicklung der drei Anwendungsklassen, werden die jeweiligen Anwendungsprozesse gegenwärtig in eigenständigen Systemen modelliert und ausgeführt. Daraus resultiert jedoch eine Reihe von Nachteilen, welche diese Arbeit aufzeigt und ausführlich diskutiert. Vor diesem Hintergrund beschäftigte sich die vorliegende Arbeit mit der Ableitung einer konsolidierten Ausführungsplattform, die es ermöglicht, Prozesse aller drei Anwendungsklassen gemeinsam zu modellieren und in einer SOA-basierten Infrastruktur effizient auszuführen. Die vorliegende Arbeit adressiert die Probleme einer solchen konsolidierten Ausführungsplattform auf den drei Ebenen der Dienstkommunikation, der Prozessausführung und der optimalen Verteilung von SOA-Komponenten in einer Infrastruktur.

Throughout history, humans have proven to develop and improve their quality of life constantly. Incorporating mechanical principles into otherwise manual labor was one such aspect. Today, introducing mechanization to the industry and steam power is regarded as the first industrial revolution. Since then, a second and a third have followed, introducing concepts such as electricity, automation, computers, and computerization. Finally, in 2011 the fourth industrial revolution was introduced as Industry 4.0 by a project started in Germany, which considers digitalization. Industry 4.0 uses concepts such as Cyber-Physical Systems (CPS), the Internet of Things (IoT), and cloud computing. The goal of these concepts is to be able to further the capabilities of automation in the industry, creating smart factories. A problem experienced today when making changes to the production line is that an immense amount of hard coding is required for the Programmable Logic Controller (PLC) controlling the system as well as for the system controlling the factory. The Eclipse Arrowhead Framework addresses these issues by applying a particular set of parameters to all systems within the IT infrastructure. The Arrowheadframework offers parameters such as orchestrator, authorization, and a service registry to each system incorporated within the framework. By applying this, the System of Systems (SoS) and the parameters provided by the Arrowhead framework create a local cloud. In doing so, each system within a factory belongs to its local cloud, building a factory made of a cluster of local clouds. By applying the ideas of Industry 4.0, a proof of concept is created, showing that today’s industry would benefit from using the concepts stated above with digital twins. The thesis explores and proves that, with the help of digital twins, today’s industry can cut down on manufacturing process development. In addition, it reduces the time it takes to apply changes to the production line by enabling machine learning to facilitate human interaction. A model factory created by fischertechnik is used, together with a PLC, as the physical twin in this master thesis. In addition, using Siemens Computer-Aided Design (CAD) software NX, a digital twin is created; this digital twin will communicate with the physical twin to simulate the behavior of the physical twin in real-time. A server has been created and is acting as a hub of communication for both of the twins. The use of the digital twin to communicate with the physical twin will enable tremendous advances in automation regarding industry 4.0.

Mina meddelanden (English: My Messages) is a secure electronic mail service provided by seven Swedish public authorities, which may be used by the Swedish population to electronically receive mail from the public sector. The IT infrastructure of this mail service is primarily developed and maintained by the Swedish Tax Agency. It is built on Web Services and the principles of Service-Oriented Architecture (SOA). This allows external stakeholders to connect to the system as subsystems: Senders, Postal Services or Mailbox Operators, each designed to either send, mediate or receive mail using Web Services. Used in this way, Web Services allow for a loosely coupled system, however, system upgrades must be deployed in an orderly fashion so as to prevent breakdowns. The main research areas of this literature review, conducted with an iterative search process, include versioning of Web Services, SOA strategies, design patterns and frameworks. Based on the findings of this research, two theoretical approaches are suggested for Mina meddelanden: (i) a gradual change between two strictly controlled versions with a unified repository to store relevant Web service artifacts and documentations, and (ii) more generally to implement an integration platform that includes a service bus to mediate messages to the most suitable version. Mina meddelanden is a government project, and there are strict IT regulations and directives that must be followed. Therefore, the first approach is the most suitable at the time of writing, since there is already a working version of the system that follows these rules. Future implementation of an integration platform requires further study to ensure legal requirements are met. / Mina meddelanden är en säker digital posttjänst som tillhandahålls av sju svenska myndigheter och kan användas av den svenska befolkningen för att ta emot post elektroniskt från den offentliga sektorn. IT-infrastrukturen av denna posttjänst utvecklas och underhålls främst av Skatteverket. Den är byggd på webbtjänster och principerna av en tjänsteorienterad arkitektur (SOA). Detta gör det möjligt för externa aktörer att ansluta till systemet som delsystemen: Avsändare, Förmedlare eller Brevlådeoperatörer som är utformade för att antingen skicka, förmedla eller ta emot e-post med hjälp av webbtjänster. Webbtjänster gör det möjligt för delsystemen att samarbeta med varandra, men uppdateringar utav ett sådant system måste ske på ett metodiskt sätt för att förhindra haverier. Det huvudsakliga undersökningsområdet av denna litteraturstudie, genomfördes med en iterativ sökprocess, omfattas av versionshantering av webbtjänster, SOA strategier, designmallar och ramverk. Baserat på litteraturstudien förslås två teoretiska tillvägagångssätt för Mina meddelanden: (i) en succesiv förändring mellan två strikta och kontrollerade versioner med ett enat förvar för att lagra relevanta webbtjänster artefakter och dokumentationer och (ii) en mer generell lösning att implementera en integrationsplattform som inkluderar en tjänstebuss för att förmedla meddelanden till den mest passande versionen. Mina meddelanden är ett statligt projekt och måste därför följa strikta IT direktiv och riktlinjer, så det första tillvägagångssättet är den bäst kvalificerad i skrivande stund på grund av att det redan finns en fungerande version av systemet som följer dessa regler. Framtida implementationer av en integrationsplattform kräver ytterligare studier för att säkerställa att juridiska krav är uppnådda.

The way the structure of systems and programs are designed is very important. When working with smaller groups of systems, the chosen architecture does not affect the performance and efficiency greatly, but as these systems increase in size and complexity, the choice of architecture becomes a very important one. Problems that can arise when the complexity of software scales up are waiting for data accesses, long sequential executions and potential loss of data. There is no single, optimal software architecture, as there are countless different ways to design programs, but it is interesting to look at which architectures perform the best in terms of execution time when handling multiple bigger systems and large amounts of data. In this thesis, a case called "The Income Deduction" will be implemented in a monolithic and an event-driven architectural style and then be put through three different scenarios. The monolithic architecture was chosen due to its simplicity and popularity when constructing simpler programs and systems, while the event-driven architecture was chosen due to its theoretical benefits of removing sequential communicating between systems and thus reduce the time systems spend waiting for each other to respond. The main research question to answer is what the main benefits and drawbacks are when building larger systems with an event-driven architectural style. Additional research questions include how the architecture affects the organisation’s efficiency and cooperation between different teams, as well as how the security of data is handled. The two implementations where put through three different scenarios within the case, measuring execution time, number of HTTP requests sent, database accesses and events emitted. The results show that the event-driven architecture performed 9.4% slower in the first scenario and 0.5% slower in the second scenario. In the third scenario the event-driven architecture performed 49.0% faster than the monolithic implementation, finishing the scenario in less than half the amount of time. The monolithic implementation generally performed well in the simpler scenarios 1 and 2, where the systems had fewer integrations to each other. In these cases it is the preferred solution since it is easier to design and implement. The event-driven solution did perform much better in the more complex scenario 3, where a lot of systems and integrations were involved, since it could remove certain connections between systems. Lastly, this thesis also discusses the sustainability and ethics of the study, as well as the limitations of the research and potential future work. / Strukturen som system och program designas efter är väldigt viktigt. När en arbetar med mindre grupper av system så kommer den valda arkitekturen inte att påverka prestandan mycket. Men när dessa system växter i storlek och komplexitet så kommer valet av arkitektur vara väldigt viktigt. Problem som kan uppstå när mjukvarukomplexiteten ökar är väntandet på dataaccesser, långa sekventiella exekveringar och potentiell förlust av data. Det finns ingen optimal mjukvaruarkitektur, det finns oräkneligt många sätt att designa program. Det är intressant att kolla på vilka arkitekturer som preseterar bäst sätt till exekveringstid när en hanterar ett flertal större system och stora mängder data. I den här avhandlingen kommer ett fall, kallat "Ingångsavdraget", att implementeras i en monolitisk och en event-driven arkitekturell stil och sedan köras igenom tre olika scenarion. Den monolitiska arkitekturen var vald på grund av dess enkelhet och populäritet vid utveckling av enklar program och system. Den event-drivna arkitekturen valdes på grund av vissa teoretiska fördelar, så som att kunna undvika sekventiell kommunikation mellan systemen och därmed reducera tiden som systemen väntar på svar från varandra. Den huvudsakliga forskningsfrågan som ska besvaras är vad de största fördelarna och nackdelarna är när man bygger större system med en event-driven arkitekturell stil. Andra forskningsfrågor inkludera hur arkitekturen påverkar effektiviteten hos en organisation och samarbetet mellan olika team, samt hur datasäkerheten hanteras. De två implementationerna sattes igång tre olika scenarion inom fallet, där exekveringstid, antal HTTP-anrop skickade, databasaccesser och event skickad mättes. Resultaten visar att den event-drivna arkitekturen presterade 9.4% långsamare i det första scenariot och 0.5% långsamare i det andra scenariot. I det tredje scenariot presterade den event-drivna lösningen 49.0% snabbare än den monolitiska lösningen och avslutade därmed scenariot under hälften av tiden. Den monolitiska implementationen presterade generellt väl under de simplare scenarion 1 och 2, där systemen hade färre integrationer till varandra. I dessa fallen så är den den föredragna lösningen eftersom det är lättare att designa och implementera. Den event-drivna lösningen presterade mycket bättre i det mer komplexa scenario 3, där många system och integrationer var inblandade, eftersom den kunde ta bort vissa kopplingar mellan system. Slutligen så diskuteras även hållbarhet och etik i studien, samt begränsningarna av forskningen och potentiellt framtida arbete.