The main subject of this master thesis is the Service-Oriented Architecture (SOA). It shows a complete overview of Web Services in terms of realisation of a SOA. The thesis mentions what is already done and what else remains to ful ll the basic SOA principles. Then, it reviews Java EE platform tools used to deal with the Web Services. Next, it introduces the Java Management Extensions (JMX) technology as a solution of the web service's area - SOA governance. Moreover, it examinates the possible usage of JMX for the web service's management and monitoring issues. Finally, it implements an exemplary web services management and monitoring application on GlassFish server for testing purposes.

<p>Service-Oriented Architecture (SOA) focuses on dividing the enterprise application layer of an enterprise system into components (as services) that have direct relationships with the business functionality of the enterprise. Web services, which are based on message exchanges, are the most widely adopted SOA technology. Web services provide web-accessible programs and devices that have been widely promoted for cloud computing environments. However, different types of web services are required to model actual services in the business domain. Particularly, enterprises (business providers such as banks, health care, and insurance companies) usually send their agents or other personnel (e.g., representatives, installers, maintainers, and trainers) to client sides to perform required services. An enterprise agent can be modeled as a software agent - a computer program that cannot be transmitted efficiently by communication messages. Lacking an efficient way to model the transmission of enterprise agents in traditional message based technologies restricts the application and usage of service-oriented architectures. The central problem addressed in this thesis is the need to develop an efficient SOA model for enterprise agents that will enable service providers to process client data locally at the client side.</p> <p>To address the research problem, the thesis proposes to model enterprise agents in SOA with a generic software agent called the Service Representative. This is a generic software agent which stays at the client side and can be customized by different service providers to process client data locally. Moreover, to employ a service representative, the thesis proposes a new type of web services called Task Services. While a traditional web service, called Data Service, processes client data completely at the server side, a task service is a web service with the capability of processing client data and resources partially or completely at the client side, using a Service Representative. Each task service assigns a task with three components to the generic service representative: task model, task knowledge, and task data. The task components are mapped to business components such as business process models, business rules and actions, and business data, where they can be efficiently transmitted by service messages.</p> <p>The combination of a service representative and task services provides an executable platform for service providers at the client side. Moreover, the client does not need to reveal its data, and hence privacy and security are maintained. Large volume client data is processed locally, causing less network traffic. Finally, real-time and event-triggered web services can be developed, based on the proposed approach.</p> <p>The main contributions and novelty of this research are: i) a domain independent computational model of enterprise agents in SOA to support a wide variety of client-processing tasks, ii) client- side web services which are compatible with typical server-side web services and comparable to other client-side processing technologies, iii) extensions of the SOA architecture by adding novel generic components including the service representative, the competition desk, and the service composition certifier, iv) provision of a formal model of client-side and server-side web services based on their construction of business components, v) empirical evaluations of the web service model in a number of different applications, using a prototype system, and vi) the application of the developed model to a number of target domains including the healthcare field. Furthermore, because client-side and server-side web services are complementary, a decision support model is provided that will assist service developers to decide upon the best service type for a web service.</p> / Doctor of Science (PhD)

<p>This thesis is concerned with two separate subjects; (i) Defect localization using tree mining and tree matching, and (ii) Quality-of-service-aware service selection; it is divided into these parts accordingly.</p> / <p>This thesis is concerned with two separate subjects; (i) Defect localization using tree mining and tree matching, and (ii) Quality-of-service-aware service selection; it is divided into these parts accordingly.</p> <p>In the first part of this thesis we present a novel technique for defect localization which is able to localize call-graph-affecting defects using tree mining and tree matching techniques. In this approach, given a set of successful executions and a failing execution and by following a series of analyses we generate an extended report of suspicious method calls. The proposed defect localization technique is implemented as a prototype and evaluated using four subject programs of various sizes, developed in Java or C. Our experiments show comparable results to similar defect localization tools, but unlike most of its counterparts, we do not require the availability of multiple failing executions to localize the defects. We believe that this is a major advantage, since it is often the case that we have only a single failing execution to work with. Potential risks of the proposed technique are also investigated.</p> <p>In the second part of this thesis we present an alternative strategy for service selection in service oriented architecture, which provides better quality services for less cost. The proposed Request Replication technique replicates a client’s request over a number of cheap, low quality services to gain the required quality of service. Following this approach, we also present a number of recommendations about how service providers should advertise non-functional properties of their services.</p> / Doctor of Philosophy (PhD)

According to the service orientation design paradigm there are business (BS) and electronic services (ES). BS encapsulate business concerns. ES encapsulate computing systems, information systems and software applications. In environments with a high number of BS and ES the decision on which ES provides the most suitable support for a certain BS is not a trivial task. The objective of the thesis is to provide models, methods, and techniques for preselection of ES for a given BS. Preselection is about reducing the large amount of ES to a significant smaller amount under the consideration of a particular BS.

According to the service orientation design paradigm there are business (BS) and electronic services (ES). BS encapsulate business concerns. ES encapsulate computing systems, information systems and software applications. In environments with a high number of BS and ES the decision on which ES provides the most suitable support for a certain BS is not a trivial task. The objective of the thesis is to provide models, methods, and techniques for preselection of ES for a given BS. Preselection is about reducing the large amount of ES to a significant smaller amount under the consideration of a particular BS.

Indiana University-Purdue University Indianapolis (IUPUI) / The emergence of information exchange and act of offering features through external interfaces is a vast but immensely valuable challenge, and essential elements of learning environments cannot be excluded. Nowadays, there are a lot of different service providers working in the learning systems market and each of them has their own advantages. On that premise, in today's world even large learning management systems are trying to cooperate with each other in order to be best. For instance, Instructure is a substantial company and can easily employ a dedicated team tasked with the development of a video conferencing functionality, but it chooses to use an open source alternative instead: The BigBlueButton. Unfortunately, different learning system manufacturers are using different technologies for various reasons, making integration that much harder. Standards in learning environments have come to resolve problems regarding exchanging information, providing and consuming functionalities externally and simultaneously minimizing the amount of effort needed to integrate systems. In addition to defining and simplifying these standards, careful consideration is essential when designing new, comprehensive and useful systems, as well as adding interoperability to existing systems, all which subsequently took part in this research. In this research I have reviewed most of the standards and protocols for integration in learning environments and proposed a revised approach for app stores in learning environments. Finally, as a case study, a learning tool has been developed to avail essential functionalities of a social educational learning management system integrated with other learning management systems. This tool supports the dominant and most popular standards for interoperability and can be added to learning management systems within seconds.

More and more enterprises plan to switch their legacy system to service-oriented architecture (SOA). SOA, the focus of recent software-engineering, modulizes the IT components as “services” which could be re-jointed with each other flexibly and reused to avoid building parts repeatedly. This methodology also yields network externalities (Katz and Shapiro 1986; Markus 1987) as a number of services are integrated. An enterprise could increase the number of services to earn network externalities but such benefits come with risks. / This study aims to evaluate the investment of SOA and justifies the switch of current systems to SOA. Since SOA investment is usually a long-term and risky project for most enterprises, uncertainty becomes an important evaluation factor of an SOA project. This research applies the real option approach to evaluate an SOA switching project which majorly justifies the uncertainties, and use Monte-Carlo simulation to do the option pricing work. We consider three components of uncertainty in the model– risk, exercise time and number of connecting services for reusing- and evaluate how the uncertainty relates to the value of an SOA project. Finally, this research deduces the investment strategies under uncertainties, and describes what advantages for real option SOA has which are SOA could reduce the investment friction.

隨著雲端運算基礎架構的發展，如何結合企業資訊服務與外部雲端運算資源，是當前重要的研究課題。目前市面上一些主要的資服業者，如Google、IBM以及HP等，大力推動並提供強大雲端運算能力與完善的應用服務環境；然而目前雲端運算架構多需將整體應用與資料放置於外部平台，引發企業導入雲端運算時控制權移轉與資訊安全的疑慮。為解決雲端運算所衍生出內外部資源有效配置的問題，與企業導入上的資安疑慮，本研究結合雲端運算與服務導向架構，發展出雲端運算服務導向架構運作機制，包含服務串接、資源配置、資料控管與管理機制，並依照這些運算機制建構出以服務介面層、中心控管層、服務供應層與基礎架構層組成的『雲端運算服務導向架構平台』。 服務串接機制負責連接服務需求方、服務元件商與服務套餐業者；資源配置機制具備負載平衡、平行運算與容錯機制等功能；資料控管機制利用部分授權的方式讓資料以片段的方式存在，避免有心人士竊取的風險，對於資料運算的安全性，讓服務供應方只能取得經授權的必須資料，關鍵資訊僅掌握在資料擁有人手中，以確保資料安全性；管理機制實作了AAA協定，認證機制決定服務使用者的身份與服務範圍。 而服務平台中的應用介面層利用開放平台的優勢，降低服務介面開發的負擔；中心控管層連接服務供應方與服務需求方，掌控完整的服務流程，以及使用外部雲端運算與資料中心之資源；服務供應層結合各式應用服務與資料來源，藉由將運算與資料分離的方式，讓服務需求者保持對資料的控管權力，以解決企業導入雲端架構時對資安的疑慮；基礎架構層可連結雲端運算資源，未來可利用各雲端業者所提出的服務架構、運算能力以及儲存資源，並依照個別平台的優勢與特性，充分發揮雲端運算架構的效益。 最後本研究藉由發展金融發票融資之應用，以說明本服務平台之可行性與整合外部雲端運算服務的優越性，以及未來研究方向。 / Cloud Computing heralds an evolution of business, this creates a research question on how to integrate enterprise information service and external Cloud Computing resource. Information service big players like Google, IBM and HP, providing powerful Cloud Computing ability and application environment. However, when enterprises adopt Cloud Computing architectures proposed recently, and transfer applications and data to external platform arouses the problems of management authority shifting and information security. We proposed a 4-layer service platform and related operation mechanism that incorporates Google Cloud Computing environment and Service Oriented Architecture in a sense to provide new paradigm of system development. Service Combination Mechanism connects service consumer, service provider and service menu. Resource Allocation Mechanism provides loading balance, parallel processing and fault-tolerant features. Data Control Mechanism only authorizes the necessary part of data to avoid the risk of information security. Management Mechanism implements AAA protocol. Service Interface Layer utilizes the advantage of open platform and reduces the burden of interface development. Control Center Layer connect service providers and service requesters, while handling service flow and using the resource of external cloud computing and data center. Service Provider Layer reserves the management authority and ownership of the data resources. Infrastructure Layer assemble service framework, computing ability and storage resource that are provided by Cloud Computing providers. We believed that with the 4-layers service platform proposed in this paper, one can leverage the advantages and merits of Cloud Computing architecture. Finally, by developing a invoice financing case based on proposed platform, we are able to justify the service platform’s feasibility and its advantage with the use of cloud computing.

(略) / Service-oriented Architecture (SOA) paradigm is an emerging architectural blueprint which enables flexible process-oriented application systems. While more and more enterprises plan to adopt SOA to increase reusability and flexibility of their business processes, the readiness of this technology becomes important to enterprises. However, previous SOA studies focus mainly on the technical issues but ignore the organizational or managerial issues. To fill this gap, this research aims to explore the factors of adopting SOA. Developed upon institutional theory and diffusion of innovation theory, we not only consider the technical factors with SOA adoption, but also pay attention to factors related with organizations and IT innovations. Furthermore, a content analysis of online Webs, blogs, and forums is taken to verify our research framework, and research findings indicate the relative advantage of SOA, compatibility of SOA, the characteristics of decision makers, culture, IT capability, and SOA socioeconomic characteristics are the most important drivers for SOA adoption. The contribution is summarized in two folds: (1) enterprises can use this framework as a reference to diagnose their organization conditions and then make a decision to adopting SOA; and (2) researchers can develop their study upon the constructs of this framework.

Pour faire face aux contraintes économiques (demande de plus en plus importante pour de la personnalisation de masse, globalisation et réduction des coûts…), le développement de stratégies de production « Juste À Temps », ou « Lean Manufacturing » impose la réorganisation de l’entreprise sur les activités génératrices de valeur en suivant une logique de chaîne de valeur pour éviter tout gaspillage. Cette stratégie conduit de fait à un recentrage métier et une extension de la chaîne de valeur. L’entreprise est donc amenée à développer des stratégies de collaboration (Bare et Cox, 2008 ; Davis, 1987) et doit disposer d’un SI Lean (réponse au plus juste), agile pour réagir aux fluctuations et aléas, ouvert pour assurer un partenariat avec ses fournisseurs, ses clients et ses partenaires et, enfin, interopérable pour faciliter la communication entre les différents systèmes et concilier ces différentes facettes métiers. Or, le SI de l’entreprise est constitué d’une multiplicité de logiciels (l’ERP (Enterprise Resource Planning), le MES (Manufacturing Execution System), le PLM (Product Life-cycle Management), le SCM (Supply Chain Management)…). Chaque système vise à répondre à un objectif donné pour une facette métier, et est développé selon des spécifications métier propres échappant le plus souvent à toute standardisation. Ceci engendre une redondance, une hétérogénéité et une augmentation du volume d’information, d’où des risques d’incohérence, de rigidité du SI et notamment une grande difficulté de communication dans le cadre de collaboration interentreprises. Pour répondre à ces aléas, il importe de définir un SI agile et interopérable et de réorganiser les processus pour supporter la chaîne de valeur de l’entreprise. C’est dans cet objectif que nous proposons de développer un Lean ESB (Enterprise Service Bus), socle d’une Architecture Orientée Services, doté d’une couche sémantique métier. Nous avons défini quatre modules du Lean ESB : • Le module de médiation définit les échanges d’information entre les différents métiers et entre le métier et la technologie pour assurer le fonctionnement des autres modules. • Le module de chorégraphie dynamique permet de composer les services industriels pour définir les processus selon les besoins de production spécifiés par le client. • Le module de routage intelligent organise les ressources de l’atelier pour définir des processus en flux tirés. • Le module de monitoring et gouvernance permet de contrôler la performance de la production et la qualité des produits. / To meet the economic constraints (growth of mass customization demands, globalization and cost reducing), the development of new strategies forms as a “Just In Time” production strategy or “Lean Manufacturing” needs to reorganize the enterprise taking into account the activities which generates value (following the value-chain logic) in order to avoid wastefulness. This strategy leads to a business refocusing and a value-chain extension. The enterprise has to develop collaboration strategies (Bare and Cox, 2008 ; Davis, 1987) and has to have a Lean (just in time response) Information Systems (IS), agile IS to react fluctuations, open IS to support a partnership with suppliers, customers and partners and interoperable IS to make easier the communication between systems and business views. However, the enterprise IS contains multiple systems: ERP (Enterprise Resource Planning), MES (Manufacturing Execution System), PLM (Product Life-cycle Management), SCM (Supply Chain Management)…Each system is designed to meet a particular business view, and is developed according to specific business requirementswithout any standardization which cause redundancy, heterogeneity and increase the volume of information including an inconsistency, a rigidity of the IS and a difficulty of inter-enterprise collaboration. To face theses disadvantages we have to define an agile and interoperable IS and to reorganize processes to support the enterprise value-chain. Therefore, we propose to develop a Lean ESB (Enterprise Service Bus) which is a Service Oriented Architecture middleware, improved by a business semantic layer. We defined four modules of Lean ESB:• The mediation module defines information exchange between a business layers and IS and insures other modules operating. • The dynamic choreography module enables industrial services composition to define processes in accordance with customer demands. • The intelligent routing module organizes workshop resources in order to reorganize processes in a pull flow strategy. • The monitoring and governance module enables the control of production performance and products quality.