ServiceTechMag.com > Archive > Issue LXXV, August 2013
Download Issue
Download Full Service Technology Magazine PDF




Evolution of About Fusion Middleware Practices in Manufacturing Domain: Adoption of SOA

Sadia Tahseen

Sadia Tahseen

This article discusses the evolution of integration in the manufacturing sector, highlighting the pros and cons of the various approaches that have been successively adopted before selecting SOA as the most effective choice. This article also discusses the implementation of governance initiatives when applying SOA-based solutions to achieve overall Integration success. Nowadays, manufacturing companies are facing challenges to become more flexible and agile as business models change. There has been a great deal of concern regarding speed deployment with reduced ongoing maintenance and support costs. The ability of companies to quickly adapt to a changing business environment depends on the agility of their corporate culture, flexibility of the business processes they incorporate, and the interoperability they employ. Enterprises are required to support open industry standards (SLA) and integrations that are easy to maintain and less risky to evolve, in addition to withstanding the necessary upgrades. Another driver of business change is the increasing number of regulations that the government and other agencies have imposed on manufacturing companies. Companies must trace not only the main products through their entire lifecycles until they reach the consumer, but also the secondary products that are derived from the core manufacturing process. To tackle these issues, service-oriented architecture has been used to leverage industry standards that allow for complete, integrated, best-of-breed, and plug-and-play types of architecture for IT systems...


Understanding Service Compensation

Jürgen Kress, Berthold Maier, Hajo Normann, Danilo Schmiedel, Guido Schmutz, Bernd Trops, Clemens Utschig-Utschig, Torsten Winterberg

Jürgen Kress Berthold Maier Hajo Normann
Danilo Schmiedel Guido Schmutz Bernd Trops Clemens Utschig-Utschig Torsten Winterberg

Some of the most important SOA design patterns that we have successfully applied in projects will be described in this article. These include the Compensation pattern and the UI mediator pattern, the Common Data Format pattern and the Data Access pattern. All of these patterns are included in Thomas Erl's book, "SOA Design Patterns", and are presented here in detail, together with our practical experiences. We begin our "best of" SOA pattern collection with the Compensation pattern. Compensation is required in error situations in an SOA, as multiple atomic service operations cannot generally be linked with classic transactions this would violate the principle of loose coupling. An error situation of this sort will occur, particularly if service operations are combined into processes or new services during orchestration or by applying the Composite pattern, and the transaction bracket has to be expanded as a result. We need mechanisms to undo the effects of individual services (the status changes in the overall system) and to ensure that a consistent system state is maintained at all times, so as to preserve system integrity. For the Compensation pattern, we would like to address the following questions: Why is compensation important in relation to SOA? How is the topic of compensation linked with the topic of transactions? What are the challenges with regard to compensation...


Mobile OS Architecture Trends - Part I

Kerry Jiang, Xiao-Feng Li, Bingwei Liu, Yong Wang, Weihua Jackie Wu

The world is flat, because it becomes increasingly mobile, fast, connected, and secure. People expect to move around easily with their mobile devices, keeping close communications with their partners and family, enjoying the versatile usage models and infinite contents, and without worrying about the device and data management. These all put requirements on the mobile devices, of which the mobile OS is the soul. Based on our years of experience in mobile OS design and an extensive survey of current industry situation, we believe there are several commonalities in future mobile OS architecture, such as user experience, power management, security design, cloud support, and openness design. We develop an analysis model to guide our investigation. In this article, we describe our investigations in the trends of mobile OS architecture over the next decade by focusing on the major commonalities. Based on the findings, we also review the characteristics of today's mobile operating systems from the perspective of architecture trends. Mobile OS design has experienced a three-phase evolution: from the PC- based OS to an embedded OS to the current smartphone-oriented OS in the past decade. Throughout the process, mobile OS architecture has gone from complex to simple to something in-between. The evolution process is naturally driven by the technology advancements in hardware, software, and the Internet. Hardware. The industry has been reducing the factor size of microprocessors and peripherals to design actual mobile devices. Before the form factor size was reduced enough, the mobile...


SLA - Aware Enterprise Service Computing - Part II

Longji Tang, Jing Dong, Yajing Zhao

Longji Tang

As is the case for everything else, SOA assets are subject to the passage of time and can't be fully analyzed without a deeper understanding of their lifecycles, stages and transitions. Take almost any practice in IT and the "SMART" acronym is applicable, of which the letter "T" for time-bound is of particular importance. A complete view of the past to future is necessary to truly govern SOA. Channels of communication not only need to encompass what was executed and decided, but also what the current situation or landscape is and what is planned for the future. A false premise of the impact analysis of current governance tools is that an assessment that is based solely on a snapshot taken from a single point in time can be performed. By correlating common project management practices with service lifecycle stages, we can provide a comprehensive view of the past, present and future states of projects and the services they impact. This comprehensiveness is critical, since projects experience service production, reuse, retirement and change that can affect the entire organization's service-oriented architecture. In Figure 1, two scenarios depicting project portfolio management through SOA governance show how different kinds of actions performed on services from each project have an impact on decision-making. Actions can range from promoting future service reuse and...


2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006