IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
SDN and NFV: Transforming the Service Provider OrganizationJuniper Networks
As competition increases, service providers must be able to respond quickly to competitive pressures and rapidly evolving customer demands. Learn how NFV and SDN allows service providers to embrace a holistic approach to their business transformation and maximize existing capabilities: http://juni.pr/1JQZYOl
The document discusses the key characteristics of contemporary service-oriented architecture (SOA). It describes how contemporary SOA is based on open standards, supports vendor diversity, and increases quality of service through features like security, reliability, and performance. Contemporary SOA promotes autonomy by allowing services and messages to independently control their own logic and processing.
The document discusses the relationship between web services and primitive SOA. It defines web services as a technology framework that includes architectures, technologies, concepts and models. The key aspects of the web services framework are service descriptions using WSDL, SOAP messaging, and service registration/discovery using UDDI. Web services can take on different roles like service provider, requestor, or intermediary. The document also discusses different service models including business, utility, and controller services.
UN CEFACT Business Requirements Specification Cross Industry Invoicing ProcessFriso de Jong
The current practice of the exchange of business documents in e-business transactions presents major opportunities to improve the competitiveness of companies. Especially the Small and Medium Enterprises (SME).
Service Oriented Architecture.
SOA is a style of architecting applications in such a way that they are composed of discrete software agents that have simple, well defined interfaces and are orchestrated through a loose coupling to perform a required function.
This chapter discusses services in the context of service-oriented architecture (SOA). It defines a service as a self-contained business function that accepts requests and returns responses through a standard interface. A service should represent discrete units of work from a business perspective rather than being technically driven. The interface of a service, including message signatures and semantics, is considered its contract. Additional common attributes of services discussed include being stateless, reusable, and having quality of service guarantees.
Service-oriented Architecture with Respect to ReusabilityYazd University
This document provides an introduction to service-oriented development with a focus on reusability. It includes 4 lectures on topics like introduction to service-oriented architecture, reusability and its relation to SOA, SOA tools, and SOA case studies. The lectures are presented by group members from Shahid Bahonar University of Kerman and cover concepts such as SOA, web services, the SOA lifecycle, and SOA design patterns.
Service Level Agreements (SLAs) represent service management contracts that are processed by monitoring and measurement mechanisms for the evaluation of the signatories adherence to the agreed service levels during service execution. The paper discusses SLA data management characteristics that need to be considered in the design of data models for SLA documents. The SLA anatomy is introduced with respect to the Web Service Level Agreement (WSLA) [1] language specification. Furthermore, the paper highlights current obstacles for the integration of automated SLA management in the cloud business setting. The contributed SLA data analysis maps SLA terms to data management attributes according to their operational relevance during the SLA activity. We present an SLA digraph model for the automated SLA formulation and data handling. The SLA digraph is introduced as a programming module that sits on the application layer and communicates with backend data stores for the SLA persistence.
SDN and NFV: Transforming the Service Provider OrganizationJuniper Networks
As competition increases, service providers must be able to respond quickly to competitive pressures and rapidly evolving customer demands. Learn how NFV and SDN allows service providers to embrace a holistic approach to their business transformation and maximize existing capabilities: http://juni.pr/1JQZYOl
The document discusses the key characteristics of contemporary service-oriented architecture (SOA). It describes how contemporary SOA is based on open standards, supports vendor diversity, and increases quality of service through features like security, reliability, and performance. Contemporary SOA promotes autonomy by allowing services and messages to independently control their own logic and processing.
The document discusses the relationship between web services and primitive SOA. It defines web services as a technology framework that includes architectures, technologies, concepts and models. The key aspects of the web services framework are service descriptions using WSDL, SOAP messaging, and service registration/discovery using UDDI. Web services can take on different roles like service provider, requestor, or intermediary. The document also discusses different service models including business, utility, and controller services.
UN CEFACT Business Requirements Specification Cross Industry Invoicing ProcessFriso de Jong
The current practice of the exchange of business documents in e-business transactions presents major opportunities to improve the competitiveness of companies. Especially the Small and Medium Enterprises (SME).
Service Oriented Architecture.
SOA is a style of architecting applications in such a way that they are composed of discrete software agents that have simple, well defined interfaces and are orchestrated through a loose coupling to perform a required function.
This chapter discusses services in the context of service-oriented architecture (SOA). It defines a service as a self-contained business function that accepts requests and returns responses through a standard interface. A service should represent discrete units of work from a business perspective rather than being technically driven. The interface of a service, including message signatures and semantics, is considered its contract. Additional common attributes of services discussed include being stateless, reusable, and having quality of service guarantees.
Service-oriented Architecture with Respect to ReusabilityYazd University
This document provides an introduction to service-oriented development with a focus on reusability. It includes 4 lectures on topics like introduction to service-oriented architecture, reusability and its relation to SOA, SOA tools, and SOA case studies. The lectures are presented by group members from Shahid Bahonar University of Kerman and cover concepts such as SOA, web services, the SOA lifecycle, and SOA design patterns.
Service Level Agreements (SLAs) represent service management contracts that are processed by monitoring and measurement mechanisms for the evaluation of the signatories adherence to the agreed service levels during service execution. The paper discusses SLA data management characteristics that need to be considered in the design of data models for SLA documents. The SLA anatomy is introduced with respect to the Web Service Level Agreement (WSLA) [1] language specification. Furthermore, the paper highlights current obstacles for the integration of automated SLA management in the cloud business setting. The contributed SLA data analysis maps SLA terms to data management attributes according to their operational relevance during the SLA activity. We present an SLA digraph model for the automated SLA formulation and data handling. The SLA digraph is introduced as a programming module that sits on the application layer and communicates with backend data stores for the SLA persistence.
This document provides an overview of service-oriented architecture (SOA) fundamentals and concepts. It discusses the evolution of computing architectures from mainframes to client-server to web services. Key SOA concepts are introduced like loosely coupled services, service consumers and providers, and standards like XML, SOAP, WSDL and UDDI. The roles of the enterprise service bus, SOA registry, service broker and supervisor are described. Finally, the document presents a high-level view of how all the components work together in an SOA.
QOS OF WEB SERVICE: SURVEY ON PERFORMANCE AND SCALABILITYcsandit
In today’s scenario, most of the organizations provide the services through the web. This makes
the web service an important research area. In addition, early design and building web services,
it is necessary to concentrate on the quality of web services. Performance is an important
quality attributes that to be considered during the designing of web services. The expected
performance can be achieved by proper scheduling of resources and scalability of the system.
Scalability is a desirable attribute of a process computer system or network. Poor scalability
can result in lacking system performance. Hence, in this paper, we have reviewed the literature
available for the quality attributes of performance and scalability and identified the issues that
affect the quality attributes related to Web Services.
Service Oriented Architecture (SOA) [1/5] : Introduction to SOAIMC Institute
This document provides an introduction to service-oriented architecture (SOA). It discusses the evolution of enterprise application frameworks from single-tier mainframe systems to modern n-tier architectures with application servers. SOA is defined as using loosely coupled, reusable services to support business processes and goals. The key benefits of SOA include increased flexibility, reuse, and alignment between IT systems and business processes. The document outlines the typical layers of an SOA implementation including resources, services, and business processes. Key SOA concepts like service registries, coarse-grained services, and service composition are also explained.
TOWARDS AUTOMATION OF SOA-BASED BUSINESS PROCESSESIJCSEA Journal
This document presents the BPA-SOA methodology for automating SOA-based business processes. The methodology involves modeling the business process using a standard like BPMN, then defining how activities will be executed (e.g. via web services). It also includes detailing the business process data by associating data types and variables, and resolving any predicates. The goal is to take the high-level business process specification and transform it into an executable process that can be deployed and run on an orchestration engine.
This document discusses stateful web services and techniques for managing state in stateless web services. It begins with definitions of key concepts like web services, SOAP, WSDL, UDDI and ebXML. It then discusses the need for state management in situations that require establishing sessions between clients and services. Various techniques for managing state are described, including storing state in memory or in a database, with databases allowing state to be shared across servers but imposing more load. The document provides background on stateful web services and best practices for managing state in stateless environments.
EXTENDING WS-CDL TO SUPPORT REUSABILITY ijwscjournal
This document discusses extending the WS-CDL (Web Service Choreography Description Language) specification to better support reusability of choreographies. The authors propose adding a new "Template" element to WS-CDL that would allow abstract choreographies to be defined independently and then reused by mapping their interfaces to specific instances in other choreographies. Currently, WS-CDL's "Perform" activity does not support parameterizing or injecting variables into performed sub-choreographies, limiting its reusability. The Template element is intended to address this by allowing abstract choreographies defined in templates to expose parameterized interfaces that can be customized when reused.
Datasheet for Hosted Exchange with Windows Phone 2003Hiram Verma
Hosted Exchange 2003 enables mobile operators to offer flexible and scalable email, messaging, and collaboration services to SMBs and consumers. It provides a tested, pre-engineered solution based on Microsoft server products with management tools to ensure rapid deployment and superior service levels. Hosted Exchange offers scalability from 30,000 to millions of mailboxes and allows operators to bundle additional services to differentiate offerings and improve TCO. It provides an integrated platform for multiple services including email, collaboration, web hosting, calendaring, storage, and mobile device synchronization to address SMBs, SOHO users, consumers, and some enterprises.
The Content Assembly Mechanism specification provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements, attributes and structures. A CAM rule set and document assembly template defines the specific business context, content requirement, and transactional function of a document. A CAM template must be capable of consistently reproducing documents that can successfully carry out the specific transactional function that they were designed for. CAM also provides the foundation for creating industry libraries and dictionaries of schema elements and business document structures to support business process needs.
WDSOA'05 Whitepaper: SOA and the Future of Application DevelopmentRajesh Raheja
SOAs improve robustness by leveraging web standards and allow easier evolution of applications since services have well-defined interfaces and exchange self-describing messages rather than being tightly coupled. This represents a significant evolution from traditional distributed programming models.
The document discusses the role of the Object Management Group (OMG) and its Model Driven Architecture (MDA) standards in supporting Service Oriented Architectures (SOAs). It explains that MDA provides platform-independent modeling standards for the different layers of an SOA - from business processes to services to components. These standards, such as BPMN, UML, and SPEM, allow for complete modeling of SOA solutions and transformation between models. They provide a common foundation and approach that ensures interoperability and protects long-term investments in SOA systems.
03 Service Oriented Architecture Series - Basic SOA ArchitecturePouria Ghatrenabi
Service Oriented Architecture (SOA) is the secret sauce of many software integration and internet technologies. The SOA Series includes five presentations based on IBM SOA Associate Certificate. It gives a very concise, practical overview of SOA concepts. The third presentation discusses the characteristics of a basic SOA architecture, IBM SOA Reference Architecture, enterprise service bus (ESB), role of Web Services and messaging, and the the stages of the SOA lifecycle
Web Services-Enhanced Agile Modeling and Integrating Business ProcessesMustafa Salam
We propose a model-driven approach, based on Web services standards, for modeling and integrating agile business processes using Web services. The choice of focusing on Web services technology was not arbitrary. The large and broad adoption of this technology by enterprises will lead most business processes to be performed using Web services. Besides, the added value of Web services and their great interest to business process management are beyond doubt. Web services produce, on the one hand, loosely coupled applicative components.
On the other hand, they are the most widely used implementation technology of SOA (Service-Oriented Architecture), which is based on the large experiences of software and distributed component technologies. Being founded on the XML (eXtensible Markup Language) language, the SOAP (Simple Object Access Protocol) protocol and the UDDI (Universal Description Discovery and Integration) repository, this technology can be considered as an appropriate mean to ensure interoperability, data exchange and the publication and discovery of business processes when they can be implemented as Web services.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The project summary section provides an executive overview with objectives, scope, references, and outstanding issues. The requirements definition section outlines goals, usability requirements, security requirements, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
Service contract clauses as business rulesLibero Maesano
Service contracts between digital providers and consumers should be: (i) understood and verified by the business stakeholders, (ii) mechanically checked for consistency and (iii) automatically mapped to system implementations. This presentation sketches guidelines and templates for expressing service contract clauses as business rules, i.e. logical formulations in constrained natural language conforming to the OMG Semantics of Business Vocabulary and Business Rules (SBVR) specification.
When supported by the SBVR abstract notation, natural language business rules can be mechanically checked for consistency, and eventually processed for automated generation of technical model elements, machine-readable components, executable code and tests. The service contract clauses are established through a method that is inspired by the Design by contract™ approach: the signature of the service operation is expressed by means of a set of business vocabulary entries and its pre/post-conditions are stated as operative business rules. The method and the corresponding rule templates are included in a methodological framework for model driven engineering of services architectures (simpleSOA™), in which the service contract, as a bundle of rights and duties for service providers and consumers, is represented by a layered collection of formal models that work as a body of requirements for implementations. In this model-driven framework, the service contract vocabulary and rule-book constitute the service Computation Independent Model (CIM). We introduce the method guidelines and templates through an example and discuss the assumptions on the resulting conceptual model as well as some recommendations on the contract building enterprise.
This document discusses service-oriented architecture (SOA) and related concepts. It defines SOA as a software design pattern based on discrete software modules called services that collectively provide application functionality. SOA allows services to easily cooperate over a network through standardized communication. The document outlines the evolution of SOA from earlier paradigms like object-orientation, different types of SOA, and key SOA concepts like loose coupling and interoperability. It also discusses merits and limitations of the SOA approach.
This document provides a summary of service oriented architecture (SOA) and how it integrates with web 2.0 technologies. It discusses key aspects of SOA including requirements, a reference model, interaction models, and a generic reference architecture. The reference architecture shows how services are exposed and integrated via a service provider interface to enable consumers to access capabilities. SOA allows for shared functionality to be reused across multiple business processes and applications through this loose coupling of services.
This document evaluates the performance of the AODV and DSR routing protocols for Variable Bit Rate (VBR) multimedia traffic in mobile ad hoc networks. It conducts simulations in NS-2 to analyze four performance metrics: packet received, throughput, routing overhead, and network load. The results show that AODV outperforms DSR for packet received, throughput, and routing overhead. DSR has higher network load than AODV. Therefore, the document concludes that AODV is better suited than DSR for VBR multimedia transmission in mobile ad hoc networks.
This document summarizes a study on wall pressure distribution in a suddenly expanded flow for an area ratio of 2.56. Experiments were conducted by attaching an enlarged duct to the exit of an axisymmetric convergent-divergent nozzle. Wall pressure was measured for nozzle pressure ratios of 3-11 and Mach numbers of 1.87, 2.2, and 2.58. Microjets were used as an active control method to study their effect on wall pressure distribution. Results showed that microjets did not adversely affect the oscillatory wall pressure field for most conditions tested. At Mach 2.58 and NPR of 9, microjets significantly increased the reattachment length in the duct. In general, microjets were found
This document summarizes research on analyzing the steady-state performance of a self-excited induction generator using three optimization techniques: genetic algorithms, pattern search, and quasi-Newton methods. It provides background on induction generators and how they can operate as self-excited generators by connecting capacitors to the stator terminals. The document presents the standard steady-state equivalent circuit model and derives nonlinear equations that are solved using the three optimization techniques to determine unknown parameters. The performance of the self-excited induction generator is then evaluated based on the determined parameters.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
This document provides an overview of service-oriented architecture (SOA) fundamentals and concepts. It discusses the evolution of computing architectures from mainframes to client-server to web services. Key SOA concepts are introduced like loosely coupled services, service consumers and providers, and standards like XML, SOAP, WSDL and UDDI. The roles of the enterprise service bus, SOA registry, service broker and supervisor are described. Finally, the document presents a high-level view of how all the components work together in an SOA.
QOS OF WEB SERVICE: SURVEY ON PERFORMANCE AND SCALABILITYcsandit
In today’s scenario, most of the organizations provide the services through the web. This makes
the web service an important research area. In addition, early design and building web services,
it is necessary to concentrate on the quality of web services. Performance is an important
quality attributes that to be considered during the designing of web services. The expected
performance can be achieved by proper scheduling of resources and scalability of the system.
Scalability is a desirable attribute of a process computer system or network. Poor scalability
can result in lacking system performance. Hence, in this paper, we have reviewed the literature
available for the quality attributes of performance and scalability and identified the issues that
affect the quality attributes related to Web Services.
Service Oriented Architecture (SOA) [1/5] : Introduction to SOAIMC Institute
This document provides an introduction to service-oriented architecture (SOA). It discusses the evolution of enterprise application frameworks from single-tier mainframe systems to modern n-tier architectures with application servers. SOA is defined as using loosely coupled, reusable services to support business processes and goals. The key benefits of SOA include increased flexibility, reuse, and alignment between IT systems and business processes. The document outlines the typical layers of an SOA implementation including resources, services, and business processes. Key SOA concepts like service registries, coarse-grained services, and service composition are also explained.
TOWARDS AUTOMATION OF SOA-BASED BUSINESS PROCESSESIJCSEA Journal
This document presents the BPA-SOA methodology for automating SOA-based business processes. The methodology involves modeling the business process using a standard like BPMN, then defining how activities will be executed (e.g. via web services). It also includes detailing the business process data by associating data types and variables, and resolving any predicates. The goal is to take the high-level business process specification and transform it into an executable process that can be deployed and run on an orchestration engine.
This document discusses stateful web services and techniques for managing state in stateless web services. It begins with definitions of key concepts like web services, SOAP, WSDL, UDDI and ebXML. It then discusses the need for state management in situations that require establishing sessions between clients and services. Various techniques for managing state are described, including storing state in memory or in a database, with databases allowing state to be shared across servers but imposing more load. The document provides background on stateful web services and best practices for managing state in stateless environments.
EXTENDING WS-CDL TO SUPPORT REUSABILITY ijwscjournal
This document discusses extending the WS-CDL (Web Service Choreography Description Language) specification to better support reusability of choreographies. The authors propose adding a new "Template" element to WS-CDL that would allow abstract choreographies to be defined independently and then reused by mapping their interfaces to specific instances in other choreographies. Currently, WS-CDL's "Perform" activity does not support parameterizing or injecting variables into performed sub-choreographies, limiting its reusability. The Template element is intended to address this by allowing abstract choreographies defined in templates to expose parameterized interfaces that can be customized when reused.
Datasheet for Hosted Exchange with Windows Phone 2003Hiram Verma
Hosted Exchange 2003 enables mobile operators to offer flexible and scalable email, messaging, and collaboration services to SMBs and consumers. It provides a tested, pre-engineered solution based on Microsoft server products with management tools to ensure rapid deployment and superior service levels. Hosted Exchange offers scalability from 30,000 to millions of mailboxes and allows operators to bundle additional services to differentiate offerings and improve TCO. It provides an integrated platform for multiple services including email, collaboration, web hosting, calendaring, storage, and mobile device synchronization to address SMBs, SOHO users, consumers, and some enterprises.
The Content Assembly Mechanism specification provides an open XML based system for using business rules to define, validate and compose specific business documents from generalized schema elements, attributes and structures. A CAM rule set and document assembly template defines the specific business context, content requirement, and transactional function of a document. A CAM template must be capable of consistently reproducing documents that can successfully carry out the specific transactional function that they were designed for. CAM also provides the foundation for creating industry libraries and dictionaries of schema elements and business document structures to support business process needs.
WDSOA'05 Whitepaper: SOA and the Future of Application DevelopmentRajesh Raheja
SOAs improve robustness by leveraging web standards and allow easier evolution of applications since services have well-defined interfaces and exchange self-describing messages rather than being tightly coupled. This represents a significant evolution from traditional distributed programming models.
The document discusses the role of the Object Management Group (OMG) and its Model Driven Architecture (MDA) standards in supporting Service Oriented Architectures (SOAs). It explains that MDA provides platform-independent modeling standards for the different layers of an SOA - from business processes to services to components. These standards, such as BPMN, UML, and SPEM, allow for complete modeling of SOA solutions and transformation between models. They provide a common foundation and approach that ensures interoperability and protects long-term investments in SOA systems.
03 Service Oriented Architecture Series - Basic SOA ArchitecturePouria Ghatrenabi
Service Oriented Architecture (SOA) is the secret sauce of many software integration and internet technologies. The SOA Series includes five presentations based on IBM SOA Associate Certificate. It gives a very concise, practical overview of SOA concepts. The third presentation discusses the characteristics of a basic SOA architecture, IBM SOA Reference Architecture, enterprise service bus (ESB), role of Web Services and messaging, and the the stages of the SOA lifecycle
Web Services-Enhanced Agile Modeling and Integrating Business ProcessesMustafa Salam
We propose a model-driven approach, based on Web services standards, for modeling and integrating agile business processes using Web services. The choice of focusing on Web services technology was not arbitrary. The large and broad adoption of this technology by enterprises will lead most business processes to be performed using Web services. Besides, the added value of Web services and their great interest to business process management are beyond doubt. Web services produce, on the one hand, loosely coupled applicative components.
On the other hand, they are the most widely used implementation technology of SOA (Service-Oriented Architecture), which is based on the large experiences of software and distributed component technologies. Being founded on the XML (eXtensible Markup Language) language, the SOAP (Simple Object Access Protocol) protocol and the UDDI (Universal Description Discovery and Integration) repository, this technology can be considered as an appropriate mean to ensure interoperability, data exchange and the publication and discovery of business processes when they can be implemented as Web services.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The project summary section provides an executive overview with objectives, scope, references, and outstanding issues. The requirements definition section outlines goals, usability requirements, security requirements, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
Service contract clauses as business rulesLibero Maesano
Service contracts between digital providers and consumers should be: (i) understood and verified by the business stakeholders, (ii) mechanically checked for consistency and (iii) automatically mapped to system implementations. This presentation sketches guidelines and templates for expressing service contract clauses as business rules, i.e. logical formulations in constrained natural language conforming to the OMG Semantics of Business Vocabulary and Business Rules (SBVR) specification.
When supported by the SBVR abstract notation, natural language business rules can be mechanically checked for consistency, and eventually processed for automated generation of technical model elements, machine-readable components, executable code and tests. The service contract clauses are established through a method that is inspired by the Design by contract™ approach: the signature of the service operation is expressed by means of a set of business vocabulary entries and its pre/post-conditions are stated as operative business rules. The method and the corresponding rule templates are included in a methodological framework for model driven engineering of services architectures (simpleSOA™), in which the service contract, as a bundle of rights and duties for service providers and consumers, is represented by a layered collection of formal models that work as a body of requirements for implementations. In this model-driven framework, the service contract vocabulary and rule-book constitute the service Computation Independent Model (CIM). We introduce the method guidelines and templates through an example and discuss the assumptions on the resulting conceptual model as well as some recommendations on the contract building enterprise.
This document discusses service-oriented architecture (SOA) and related concepts. It defines SOA as a software design pattern based on discrete software modules called services that collectively provide application functionality. SOA allows services to easily cooperate over a network through standardized communication. The document outlines the evolution of SOA from earlier paradigms like object-orientation, different types of SOA, and key SOA concepts like loose coupling and interoperability. It also discusses merits and limitations of the SOA approach.
This document provides a summary of service oriented architecture (SOA) and how it integrates with web 2.0 technologies. It discusses key aspects of SOA including requirements, a reference model, interaction models, and a generic reference architecture. The reference architecture shows how services are exposed and integrated via a service provider interface to enable consumers to access capabilities. SOA allows for shared functionality to be reused across multiple business processes and applications through this loose coupling of services.
This document evaluates the performance of the AODV and DSR routing protocols for Variable Bit Rate (VBR) multimedia traffic in mobile ad hoc networks. It conducts simulations in NS-2 to analyze four performance metrics: packet received, throughput, routing overhead, and network load. The results show that AODV outperforms DSR for packet received, throughput, and routing overhead. DSR has higher network load than AODV. Therefore, the document concludes that AODV is better suited than DSR for VBR multimedia transmission in mobile ad hoc networks.
This document summarizes a study on wall pressure distribution in a suddenly expanded flow for an area ratio of 2.56. Experiments were conducted by attaching an enlarged duct to the exit of an axisymmetric convergent-divergent nozzle. Wall pressure was measured for nozzle pressure ratios of 3-11 and Mach numbers of 1.87, 2.2, and 2.58. Microjets were used as an active control method to study their effect on wall pressure distribution. Results showed that microjets did not adversely affect the oscillatory wall pressure field for most conditions tested. At Mach 2.58 and NPR of 9, microjets significantly increased the reattachment length in the duct. In general, microjets were found
This document summarizes research on analyzing the steady-state performance of a self-excited induction generator using three optimization techniques: genetic algorithms, pattern search, and quasi-Newton methods. It provides background on induction generators and how they can operate as self-excited generators by connecting capacitors to the stator terminals. The document presents the standard steady-state equivalent circuit model and derives nonlinear equations that are solved using the three optimization techniques to determine unknown parameters. The performance of the self-excited induction generator is then evaluated based on the determined parameters.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
This document presents a geometric programming model to optimize the production rate of a turning process. It develops a mathematical model to express the production time as a function of cutting parameters like cutting speed and feed rate. The objective is to minimize production time by determining the optimal cutting conditions. Experimental validation of the model shows it provides an efficient way to maximize production rate within operating constraints like maximum speed, feed rate, power requirements and surface roughness. The geometric programming technique offers advantages over other optimization methods for this application.
This document discusses sensorless vector control of induction motors. It presents the dynamic modeling of induction motors using a reference frame transformation. It then describes the principles of vector control using an inverse transformation to control stator currents. A model reference adaptive system is proposed for sensorless speed estimation, where an adaptive model estimates the rotor speed by comparing its output to a reference model. Simulation results show the sensorless control approach can accurately estimate speed with good tracking performance.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
This document summarizes a paper that proposes a new approach to feature-based 3D modeling of turned components in AutoCAD. The approach develops algorithms to model features like cylinders, tapers, holes, and grooves based on user-entered dimensions. It then stores feature information and uses it to assess similarity between components. The modeling system supports both feature-based design and recognition without needing separate feature extraction. The paper presents the algorithms for modeling different features and assessing similarity based on common features like cylinders, holes, or grooves.
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
IJERA (International journal of Engineering Research and Applications) is International online, ... peer reviewed journal. For more detail or submit your article, please visit www.ijera.com
This document summarizes a study analyzing the integrated land and watershed development of Dhobai Watershed in Dumka District, Jharkhand, India using GIS and geonomic analysis. The study aims to generate updated thematic information on natural resources to facilitate sustainable land and water management. Methodology included visual and digital interpretation of satellite imagery and topographical maps. Themes mapped included geomorphology, drainage, climate, soils, and land use/land cover. Geomorphological units identified include valleys, hills, and uplands. Drainage is dominated by the Dhobai River. Soils include Entisols, Inceptisols and Alfisols. Land use is primarily single
The document discusses the performance analysis of the MUSIC algorithm for direction of arrival (DOA) estimation using different antenna array configurations. It explores the MUSIC algorithm using a uniform linear array (ULA) and uniform circular array (UCA). Computer simulations were developed to evaluate the DOA performance of MUSIC based on ULA and UCA geometries. The performance obtained with both array configurations is analyzed through simulation results. A new proposed array geometry based on ULA is also presented and its performance is compared with ULA through simulation.
This document summarizes a research paper that proposes a new data hiding technique for hiding data in compressed video files. The technique embeds data by modifying the least significant bits of motion vectors used during video compression. Motion vectors associated with higher prediction errors are selected as candidate motion vectors to embed data. An adaptive threshold is used for each frame to minimize prediction error while maximizing data payload. The data can be extracted directly from the encoded video stream without the original video. The technique was tested on standard video sequences and was found to introduce minimal distortion and overhead.
El documento describe diferentes tipos de defectos que pueden ocurrir en pieles de animales a lo largo de los procesos de curtición, como marcas de quemaduras, picaduras de insectos, cortes y moretones. Para cada defecto, indica posibles causas y formas de repararlo, como lijar, estucar, pigmentar u otros métodos, dependiendo de la gravedad del daño.
Why Coordination And Transactions Are Key To Building An Operational SoaDavid Linthicum
The document discusses the importance of transactions and coordination in building a service-oriented architecture (SOA). Transactions have ACID properties (atomicity, consistency, isolation, durability). There are standards like WS-Coordination and WS-AtomicTransaction that help coordinate distributed services. Coordination is needed to make distributed services function as a single service and reach consistent agreement on outcomes.
Study on Use Case Model for Service Oriented Architecture Developmentijbuiiir1
The recent trends in the computer industry are the one and only thing i.e., web services. Because of the common availability and open technologies web services are relevant to all. Service-oriented architecture (SOA) helps organizations to transform their business processes for high performance by simplifying the underlying information systems. The most challenging aspect of building successful software applications is clearly understanding and specifying the requirements that an application must satisfy. Use case modeling is an increasingly popular approach for identifying and defining requirements for software applications of all types. Use cases describe the behavior of the system as its users interact with it. This approach helps to place the software requirements in the framework of a user doing some useful work with the system. This type of approach helps to map software requirements to the relevant enduser business processes, a very powerful concept. This paper presents how the relationship between use case model and Service oriented architecture
Study on Use Case Model for Service Oriented Architecture Developmentijwtiir
The recent trends in the computer industry are the one
and only thing i.e., web services. Because of the common
availability and open technologies web services are relevant to
all. Service-oriented architecture (SOA) helps organizations to
transform their business processes for high performance by
simplifying the underlying information systems. The most
challenging aspect of building successful software applications is
clearly understanding and specifying the requirements that an
application must satisfy. Use case modeling is an increasingly
popular approach for identifying and defining requirements for
software applications of all types. Use cases describe the
behavior of the system as its users interact with it. This approach
helps to place the software requirements in the framework of a
user doing some useful work with the system. This type of
approach helps to map software requirements to the relevant enduser business processes, a very powerful concept. This paper
presents how the relationship between use case model and
Service oriented architecture.
Study on Use Case Model for Service Oriented Architecture Developmentijcnes
The recent trends in the computer industry are the one and only thing i.e., web services. Because of the common availability and open technologies web services are relevant to all. Service-oriented architecture (SOA) helps organizations to transform their business processes for high performance by simplifying the underlying information systems. The most challenging aspect of building successful software applications is clearly understanding and specifying the requirements that an application must satisfy. Use case modeling is an increasingly popular approach for identifying and defining requirements for software applications of all types. Use cases describe the behavior of the system as its users interact with it. This approach helps to place the software requirements in the framework of a user doing some useful work with the system. This type of approach helps to map software requirements to the relevant endures business processes, a very powerful concept. This paper presents how the relationship between use case model and Service oriented architecture.
Evaluation of a Framework for Integrated Web ServicesIRJET Journal
This document proposes and evaluates a framework for integrating web services. It begins by discussing how users appreciate simple, on-demand access to affordable software services without needing to install or update applications themselves. The document then presents an argument for a web-based architecture that allows users to access and purchase a wide range of software applications as needed. It evaluates this framework through user surveys and examples of simulation software services to demonstrate how the integrated framework can be implemented. The surveys found that the framework reduced costs, simplified processes, and improved the user experience by combining various online components and software services.
BUSINESS SILOS INTEGRATION USING SERVICE ORIENTED ARCHITECTUREIJCSEA Journal
Agile integration satisfies the business agility and provides solutions for maintaining business changes and ensures that the enterprise survives in the current competition. Any business should be robust enough to respond to end user request. Existing traditional enterprise applications are in-capable of integrating with
different business silos lacks to improve the business agility. To address this issue, this paper is about the agile integration of different business silos using “Service Oriented Architecture” and its core technologyenables the business enterprise systems flexible, loosely coupled and improves agility. Enterprise business
systems have to adopt Service Oriented Architecture (SOA) as it promises to help them respond more rapidly to changing business requirements by composing new solutions from existing business services. Here the definition of SOA, its layers and the core technologies have been discussed.
The document discusses the Open Grid Services Architecture (OGSA). It provides definitions and explanations of key concepts in OGSA including:
- OGSA defines standard protocols and formats to build large-scale, interoperable grid systems based on services.
- The Open Grid Services Infrastructure (OGSI) provides a specification for implementing grid services as stateful web services.
- Some major goals of OGSA are identifying use cases, core platform components, and defining models and profiles for interoperable solutions.
- Security is a key challenge in grid environments due to the need for integration with existing systems, interoperability across different hosting environments, and managing dynamic trust relationships.
Ontology based dynamic business process customizationieijjournal
The document discusses ontology-based customization of dynamic business processes. It proposes using a human semantic web approach to customize processes for consumers. The framework detects customization needs by identifying discrepancies between primary and secondary business processes. It then enacts customizations automatically using rules and notifications. The approach uses ontologies, semantic web technologies like RDF, and categorization tools to map processes and overcome semantic mismatches between heterogeneous descriptions.
The aim of this paper is to propose a modeling framework, tailored to build efficient, elastic and autonomous applications from tasks and services. It includes integrated services to develop the software products, reusing on demand in-house services with specific requirements and flexible the representational state transfer (REST) services. The idea is to decouple authorization for reduced service dependency and to provide a possibility for developing the whole application by increasing the existing application flexibility. Based on the fact that there are different web application platforms that serve to offer services to users but they are not integrated; we propose a framework with high flexibility degree, especially integrating the most used services such: e-learning, administrative, and library services, as University services are concern.
The document discusses optimizing data transfer in service-oriented architectures. It proposes an approach called Promulgate that uses a hybrid orchestration and choreography model. Promulgate introduces proxy services that invoke actual web services on behalf of a centralized workflow engine. The proxies can cache and transfer data between each other to optimize transmission between services. The document evaluates Promulgate's use of data caching techniques like dynamic proxy deployment and SOAP compression to reduce redundant data transfer compared to a pure orchestration model. It describes the Promulgate architecture and actors, web service implementation using .NET and Axis, and SOAP compression using zipped SOAP. Experimental setup and configurations are also outlined to test Promulgate's performance over different network
The document discusses Service Oriented Architecture (SOA) and the Business Process Execution Language (BPEL). It defines SOA as an architectural style that allows for interoperability and flexibility. BPEL is introduced as an XML-based language used to specify business processes composed of discrete web services. Key concepts covered include the need for SOA to address heterogeneous systems and changing business needs, the role of services, and how BPEL allows the orchestration of services to create composite applications and implement business processes.
The document discusses Service Oriented Architecture (SOA) and the role of the Business Process Execution Language (BPEL). It defines SOA as an architectural style that allows components to work together through standardized interfaces. BPEL is presented as an XML-based language used to specify business processes composed of discrete web services. BPEL allows the orchestration of services by defining message sequences and processing logic. It bridges the bottom-up exposure of services and the top-down definition of business processes in SOA.
This chapter discusses situating SOA in the overall architecture context. It examines different models for visualizing SOA-based landscapes, including logical, mixed, and technical models. The chapter also addresses integrating SOA with frontends and backends, such as dividing responsibilities, multi-channel scenarios, and future task management.
1. The document discusses microservices as an emerging software architecture compared to service-oriented architectures (SOAs). Microservices break applications into independently deployable components that communicate over well-defined interfaces, allowing for improved scalability, quicker delivery, and greater autonomy compared to monolithic applications.
2. SOAs also break systems into services but take a centralized orchestration approach, while microservices emphasize decentralized coordination and independent deployment of each component service.
3. The benefits of microservices include improved scalability since each component can be scaled independently, quicker delivery through parallel development and deployment of components, and greater autonomy for teams in deploying and managing individual services.
A Novel Framework for Reliable and Fault Tolerant Web ServicesAbhishek Kumar
This document proposes a novel framework for providing reliable and fault tolerant web services. The framework uses replication and a replication manager to select a primary web service from among multiple replicas. When the primary web service fails or becomes unavailable, the replication manager switches to a new primary by updating the WSDL registration to ensure uninterrupted service for consumers. The replication manager continuously monitors the web services and can trigger recovery, reconfiguration or restart processes to maintain reliability. The proposed approach aims to achieve high performance and reliability for web services.
WEB PORTAL INTEGRATION ARCHITECTURE APPROACHESijwscjournal
This document proposes a service-oriented architecture approach for web portal integration. It begins by describing a platform-independent integration architecture based on standards like UML, MOF, and XMI. This allows modeling integration independently of specific technologies. The document then discusses using WSMO as a specific implementation, describing how the platform-independent layers map to WSMO. It also discusses integrating agents and semantic web services using model transformations. Finally, it proposes additional "X-as-a-Service" layers that could be part of the architecture, like structure-as-a-service and process-as-a-service.
WEB PORTAL INTEGRATION ARCHITECTURE APPROACHESijwscjournal
Enterprise Modelling with Web portal integration architecture requires investment of advanced architectural thinking into definition of services before any development of services or service consumers can begin. Service Oriented Architecture (SOA) is gradually replacing monolithic architecture as the premier design principle for new business applications with its inherently systematic nature and capability. Earlier efforts of notable styles of SOA such as CORBA and XATMI have failed to be adopted as main stream projects because of demanding design process requirement with sense-making activities and even have been residing with the modern SOA or Web services middleware. In this paper it is aimed to incorporate sensemaking design activities with the proposed semantic web service based architecture. This paper tries to tackle the above problem by proposing a service-oriented architecture for web data and service integration. A gen-Spec architectural pattern has been suggested and adopted in order to tackle the problem.
Firstly, it proposes a service-oriented platform independent architecture and Secondly, it presents a specific deployment of such architecture for data and service integration on the web using semantic web services implemented with the WSMO (Web Services Modeling Ontology).
IJRET : International Journal of Research in Engineering and Technology is an international peer reviewed, online journal published by eSAT Publishing House for the enhancement of research in various disciplines of Engineering and Technology. The aim and scope of the journal is to provide an academic medium and an important reference for the advancement and dissemination of research results that support high-level learning, teaching and research in the fields of Engineering and Technology. We bring together Scientists, Academician, Field Engineers, Scholars and Students of related fields of Engineering and Technology.
This document provides an overview of service oriented architecture (SOA) and directions for SOA. It introduces a conceptual framework for understanding software integration as different layers, from the communication layer to the presentation layer. It then evaluates existing SOA realization approaches like WS-* specifications, ebXML, semantic web services, and RESTful services based on this framework. The document concludes by outlining future directions in SOA to further simplify the problem of integration.
1. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
The Transaction Concept: Integrated With BPEL and WS-AT,
WS-BA Coordination Protocols
R.Soujanya (M.Tech) Guide: M.Venkateshwarlu M.Tech
Department of SE, Department of CSE,
Sri Kottam Tulasi Reddy Memorial College, Associate Professor CSE Department,
Kondair. Andhra Pradesh. Sri Kottam Tulasi Reddy Memorial College,
Kondair. Andhra Pradesh.
ABSTRACT remote operation invocation is not the revolution
Service-Oriented Computing (SOC) is brought by Service-Oriented Computing (SOC),
becoming the mainstream development paradigm
of applications over the Internet, taking though. Rather, it is the possibility of having
advantage of remote independent functionalities. programs that perform complex tasks coordinating
When the control over the communication and and reusing many loosely coupled independent
the elements of the information system is low, services.
developing solid systems is challenging. In
particular, developing reliable web service Business processes are now able to execute
compositions usually requires the integration of seamlessly across organizations and to coordinate
both composition languages, such as the Business the interaction of loosely coupled services. Often it
Process Execution Language (BPEL), and of is necessary to have transactionality for a set of
coordination protocols, such as WS-Atomic business operations,
Transaction and WS-Business Activity. But the loosely nature of such systems calls for
Unfortunately, the composition and coordination techniques and principles that go beyond traditional
of web services currently have separate languages ACID transactions.
and specifications.
The goal of this paper is twofold. First, In the present treatment, a service is a
we identify the major requirements of transaction standard XML description of an autonomous
management in Service-oriented systems and software entity, it executes in a standalone container,
survey the relevant standards. Second, we it may have one or more active instantiations, and it
propose a semiautomatic approach to integrate is made of possibly many operations that are
BPEL specifications and web service invoked asynchronously. A service composition is a
coordination protocols, that is, implementing set of operations belonging to possibly many
transaction management within service services, and a partial order relation defining the
composition processes, and thus overcoming the sequencing in which operations are to be invoked.
limitations of current technologies. Such a partial order is adequately represented as a
direct graph. A service transaction is a unit of work
Keywords: Web services, transaction comprehending two or more operations that need to
management, WS-Business Activity, WS-Atomic be invoked according to a specific transaction
Transaction, ACID properties, Service policy. The coordination of a service transaction is
composition languages, and Business process the management of the transaction according to a
execution language. given policy. A service transaction can span over
operations of one service or, more interestingly, of
1. INTRODUCTION several services.
The widespread adoption of Web services
is feeding the promises of the new field of Service One may argue that transaction
Centric Systems. As Service Centric (SC) Systems management is a well-known Technique for the new
are being increasingly adopted, new challenges and features of transactions executed by web services;
possibilities emerge. Standardized web service various web transaction specifications have been
technologies are enabling a new generation of developed. WS-Coordination [1] specification
software that relies on external services to describes an extensive framework for providing
accomplish its tasks. The remote services are usually various coordination protocols. The WS-
invoked in an asynchronous manner. They are AtomicTransaction (WS-AT) [2] and WS-Business
known by their published interfaces, and await Activity (WS-BA) specifications [3] are two typical
invocations over a possibly open network. Single web transaction protocols. They leverage WS-
Coordination by extending it to define specific
1914 | P a g e
2. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
coordination protocols for transaction processing. effects should be durable in time. Given the nature
The former is developed for simple and short-lived of Service-Oriented Systems, satisfying these
web transactions, while the latter for complex and properties is often not possible and, in the end, not
long-lived business activities. Finally, the Business necessarily desirable. In fact, some features are
Process unique to Service-Oriented Systems:
Execution Language (BPEL) [4] is a Long-lived and concurrent transactions, not
process-based composition specification language. only traditional transactions which are
In order to develop reliable web services usually short and sequential.
compositions, one needs the integration of Distributed over heterogeneous
transaction standards with composition language environments.
standards such as BPEL [5], [6]. Unfortunately, Greater range of transaction types due to
these are currently separate specifications. different types of business processes,
service types, information types, or product
This paper has a double goal: the first one is flows.
to look at the requirements of transaction Unpredictable number of participants.
management for Service-oriented systems. The Unpredictable execution length.
systematization of requirements is the starting point For example, information query and
for an analysis of current standards and technologies flight payment need 5 minutes; while e-
in the field of web services. The second goal of the shopping an hour; and a complex business
paper is to propose a framework for the integration transaction like contracting may take days.
of BPEL with transaction protocols such as WS- Greater dynamism. Computation and
AtomicTransaction and WS-Business Activity. We communication resources may change at
use a simple but representative example across the runtime.
paper, the drop-dead order (DDO) one, to illustrate
Unavailability of undo operations, most
requirements and the proposed approach. often only compensating actions that return
the system to a state that is close to the
2. The Drop Dead Order Example initial state is available.
The drop-dead order describes a scenario
Furthermore, transactions may act differently when
where a customer wants to order products from a exposed to certain conditions such as logical
distributor under the condition that the products are
expressions, events expressed in deadlines, and even
delivered before the drop-dead date (Figure). errors in case of a faulty web service. To make sure
In the scenario, the distributor tries to find a
that the integrity of data is persistent, the two
supplier that has the products available. If he finds
transaction models used are, namely, Composite and
such a supplier, he will search for a carrier that is
distributed that allow smooth recovery to a previous
able to deliver the products before the drop-dead
“safe” state.
date. If both the supplier and the carrier are able to
The set of emerging features mentioned
fulfill the demands of the customer, the distributor
earlier, which combinations of requirements are
reports to the customer that he can fulfill the order. mostly coming from the areas of databases and
After the customer has acknowledged, the distributor workflows provide the basis for identifying the most
sends a confirmation to the supplier and the carrier. relevant requirements for transactions in Service-
Oriented Systems.
FIGURE: The Drop Dead Order Example
3.1 ACID Properties
3.1.1 Atomicity
Atomicity is the property of a transaction to
either complete successfully or not at all, even in the
event of partial failures.
3.1.2 Consistency
Consistency is the property of a transaction
to begin and end in a state which is consistent with
the intended semantics of the system, i.e., not
breaking any integrity constraints.
3.1.3 Isolation
3 TRANSACTION REQUIREMENTS Isolation is the property of a transaction to
In the field of databases, transactions are perform operations isolated from all other
required to satisfy the so-called ACID properties, operations. One transaction can therefore not see the
that is, the set of operations involved in a transaction other transaction‟s data in an intermediate state.
should occur atomically, should be consistent, 3.1.4 Durability
should be isolated from other operations, and their Durability is the property of a transaction to
record the effects in a persistent way. Whenever a
1915 | P a g e
3. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
transaction notifies one participant of successful application memory by locking it in the transaction
completion, the effects must persist, even when for the entire time. While the optimistic simply
subsequent failures occur. chooses to detect collisions and then resolves the
3.2 Transaction Behaviors collision when it does occur. This scheme has better
3.2.1 Rollback performance. When two transactions are concurrent,
Rollback is the operation of returning to a they should not both claim the same supply of goods
previous state in case of a failure during a from one Supplier.
transaction. This may be necessary to enforce
consistency. TRANSACTION STANDARDS AND
3.2.2 Compensating Actions SERVICE COMPOSITION LANGUAGES
Compensating actions are executed in the WS-Transactions and Business Transaction
event of a failure during a transaction, all changes Protocol (BTP) are the two most representative
performed before the failure should be undone. standards that directly address the transaction
3.2.3 Abort management of web service-based systems, while
Abort is the returning to the initial state in for representing compositions of services, the
case of failure or if the user wishes so. Business Process Execution Language and the
3.2.4 Adding Deadlines Choreography Description Language (WS-CDL) are
Adding deadlines to transactions involves most widely known and adopted. WS-Transactions
giving timeouts to operations. consist of two coordination protocols: WS-Atomic
3.2.5 Logical Expressions Transaction and WS-Business Activity which live in
Logical expressions for specifying the WS-coordination framework. WS-AT provides
constraints are used for giving unambiguous and the coordination protocols for short-lived simple
semantically defined rules for guaranteeing operations, while WS-BA provides the coordination
consistency. protocols for long-lived complex business activities.
The WS-coordination framework is extensible and
3.3 Transaction Models incremental. That is, WS-coordination can enhance
3.3.1 Composite Transactions existing Service-Oriented Systems with transaction
Composite transactions are nested properties by wrapping them with a specific
transactions. These transactions depend on the coordination.
global outcome, that is, all three succeed or the BTP is a model for long-lived business
whole composite transaction fails. transaction structured into small atomic transactions,
3.3.2 Distributed Transactions and using cohesion to connect these atomic
Distributed transactions are transactions operations. Its motivation is to optimize the use of
between two or more parties executing on different resource involved in a long-lived transaction under
hosts. The transaction should support transactions loosely coupled web service environments and
through a network between two different hosts. avoiding the use of a central coordinator.
BPEL provides the facilities to specify
3.4 Transaction Behavior—Alternatives executable business processes with references to
3.4.1 Transaction Recovery services‟ interfaces and implementations. It does
Transaction recovery by dynamic rebinding handle some basic issues of transactions, such as
and dynamic recomposition at runtime is the compensation, fault, and exception handling, but
possibility of replacing a faulty web service when other transaction requirements are not managed.
the current service is not able to fulfill its promises. WS-CDL provides the infrastructure to describe
Dynamic recomposition is the forming of a new cross-enterprise collaborations of web services in a
composition by replacing one or several services by choreographic way.
another composition that fulfills the same function. Consider the proposed protocols that take
Imagine that the first Carrier somehow fails and is the transaction and the business perspective of
unreachable. If this happens during a transaction, Service-Oriented Systems with respect to the
then automatic rebinding with a service that offers requirements. In Table 1, we summarize the results
the same service should take place. Recomposition of the evaluation for all requirements—each row—
through rebinding with a third Carrier through the and for all protocols—each column—by denoting
Supplier is also a possibility. the satisfaction with the “⨁” symbol, the partial
satisfaction with “⨀” and no support with ”Ө”.
3.4.2 Optimistic or Pessimistic Concurrency
Control
Optimistic or pessimistic concurrency
control refers to the support of different types of
concurrency control to enforce consistency. This
control could either be optimistic or pessimistic. The
pessimistic approach prevents an entity in
1916 | P a g e
4. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
The above survey shows that there are
standardized protocols for describing transactions
and languages for describing processes in terms of
TABLE-1 Evaluation Results flows of activities. The connection among these is,
to say the least, very loose. The problem is that
processes are described in terms of activities and
roles capable of executing the activities, but
semantic dependencies among these activities are
not represented beyond message and flow control. It
may happen that several operations from a single
web service are invoked within a BPEL process, and
dependencies among these operations may exist.
Our proposal consists of making the
dependencies among the activities explicit via an
automatic procedure and performing a restructuring
step of the process, where necessary. The identified
dependencies among activities can be then identified
by the designer of the process as being transactions
or not. In case they are, the designer will decide
which kind of transactions they are and simply
annotate them. The execution framework then takes
care that transaction annotations are correctly
managed at runtime. The need for the human design
WS-AT is a traditional protocol which
decision in the process is necessary due to the lack
satisfies the basic ACID properties. WS-BA, on the
of semantic annotations of the BPEL processes.
other hand, renounces atomicity to accommodate
Only the designer can decide whether a set of
long-lived transactions. BTP has included confirm
activities that seem to have a dependency in the
sets. These confirm sets let the application element
process are to be executed transaction ally or not.
choose which operations with parties in the
transaction are to be canceled and which are to be
Fig 3 Approach to integrating transactions into
confirmed. In this way, the application element is
BPEL processes.
able to contact more services which perform the
same task and to choose the best option.
Unfortunately, BTP is not part of the WS-Stack,
which limits its compatibility with other web service
technologies. In addition, BTP does not support
long-lived transactions. There is also a difference in
granularity between the above transaction standards.
WSAT contains simple two-phase commit protocols,
WS-BA contains nonblocking protocols and BTP
consists of a Sequence of small atomic transactions.
As for security, WS-Security can be combined with
WS-Transaction as well as with BTP.
Dynamic rebinding is supported only by
BPEL, though only at the implementation level. WS-
CDL supports most requirements, while its major
disadvantage is that the large players in the field do
not support it and that no implementation is
available. Consider Fig. 3, where data transformation
WS-AT is a very conservative business goes from left to right and we distinguish three
transaction model especially with respect to layers: the data layer at the bottom, the middle
blocking. WS-BA is more appropriate for services, execution layer defining the data transformation, and
by renouncing to the concept of the two-phase the knowledge level indicating from where the
commit. BTP places itself in the middle (two-phase knowledge to transform the data comes. We start
commit is followed in a relaxed way). As for BPEL with a generic business process designed to solve
and WS-CDL, they address the business process some business goal. An automatic processing step,
perspective with limited transaction support. which we define next, identifies dependencies
among activities. These are then reviewed by an
5 PROPOSALS FOR INTEGRATING expert that decides which actually transactions are
TRANSACTIONS INTO BPEL and which not. For those who qualify, he further
decides what kind of transactions they are and
1917 | P a g e
5. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
annotates them. For instance, some may be long Figure 4: Representation of activities and the link
running while others may be atomic ones. We that connects them.
remark how this is a design step performed by an
expert who understands the domain, the specific
process, and the consequences of choosing a
transaction policy in favor of another. This step
cannot be automated unless further semantic
annotations are made on the BPEL. The restructured
and annotated process is then ready to be sent for
execution. Next the execution phase and will be
handled by the execution framework. We consider
the three phases of the approach individually.
5.1 Preprocessing
Preprocessing the BPEL specification is
performed in two steps, namely, 1) identification and
2) resolution of transaction dependencies. In order to
illustrate the two steps, we introduce an abstract
model of BPEL.
5.1.1 Abstract Model of BPEL Specifications
A BPEL process specification describes the
interaction between services in a specific composite
web service. Its abstract model, known as behavioral
interface, defines the behavior of a group of services
by specifying constraints on the order of messages to
be sent and received from a service.
A BPEL specification „S‟ is a set of
activities „A‟ and its associated links „L‟, represented
by S = (A, L). The links, which are directed, define a 5.1.2 Dependencies Identification Algorithm
partial ordering over the set of activities and are thus
well represented as a directed graph (e.g., Fig. 4). If one specifies a set of activities within a
An activity „a‟ in A having a type represented given BPEL specification S, there may exist
by Ta, has the following properties: dependencies among activities that can hinder the
- Name Na. application of transaction management as described
- Operation OPa, which is usually implemented above. Assume that
by the web service at a specific port. St = { ai│ ai is a transactional activity of a
- Input variable IVa and output variable OVa, transaction t} is a transaction t specified within the
which specify the parameters required and BPEL specification S.
produced by the OPa, respectively. For any two activities am and an where am,
- Set of source links SLa and set of target links 𝒍𝒋𝟏 𝒍𝒋𝒌
an ∈ St and am ≠ an, if there exists a path am ….
TLa, which specify the outgoing and incoming
links (transitions), respectively. an where lj1 and ljk are some links connecting
activities, we say that an is reachable from am,
A link l in S has a unique name Nl and is ∗
indirectly defined through two activities a1 and denoted as am an, and {lj1…. ljk} is a link chain of
∗ ∗
a2 which indicates not only the direction ld of am an denoted as LC { am an }. For any two
the transition, but also the conditions lc for the activities am and an in a transaction St that are
transition to take place. ∗
implemented by the same web service, if am an
Furthermore, the Customer-to-distributor ∗
link lc-d is one of the source links of the and OVam ∈ lc where l ∈ LC {am an}, then a
ReceiveOrder activity a1, namely, lc-d ∈ SLa1. transaction dependency exists between am and an.
Furthermore, lc-d ∈ TLa6, where TLa6 is the target To identify the existence of transaction dependencies
link of the CompleteDistribution activity a6. within a given BPEL specification S, we propose
Therefore, the link lc-d connects the transition Algorithm 5.1.
between a1 and a6, denoted as
𝒍𝒄−𝒅
a1 _ → a6. Fig. 4 provides an illustration of
𝒍𝒄−𝒅
a1 → a6.
_
1918 | P a g e
6. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
5.2 Declaration of Transaction Policies
Once transactions are identified and BPEL
has been accordingly restructured, one needs to
The algorithm is a standard graph algorithm define the desired transactional behavior. To this
similar to those for reachable set construction. The end, we introduce a reference transaction policy
function IdentifyDependency takes S as input and declaration schema, shown in Fig. 7.
outputs a Boolean value that represents the existence With this schema, one can declare the
of transaction dependencies. The function first transaction policy using the following elements:
creates a path p for any two activities am and an. 1. Trans ID is a nonzero integer, representing
Then, traverses the links in the link chain ls obtained transactions within a business process.
from p. When a link l is detected and its transition 2. Trans Protocol specifies a protocol for the
condition lc contains the output variable OVam of the transaction, such as WS-AtomicTransaction or WS-
first activity am, or if it contains an output variable BusinessActivity.
OVai which is identical to OVam semantically, the 3. Trans Root indicates the parent transaction
algorithm stops and returns TRUE. Otherwise, it identified by Trans_ID. The value 0 is used to
continues until all pairs of activities in St have been indicate the root transaction within the business
visited. Finally, if no transaction dependencies are process. One can specify the hierarchy of
detected, the algorithm returns FALSE. transactions by assigning appropriate Trans_IDs and
Trans_Roots.
5.1.3 Resolution of Dependencies With such a schema, one can annotate
Once transaction dependencies are constraints or preferences to a specific activity in the
identified, it is necessary to handle them. To solve BPEL specification. The annotated activity must be
this problem, we merge the dependent activities into an invoke activity. One can separately specify the
one transaction. Algorithm 5.2 resolves the desired constraints or preferences in the design-time-
transaction dependencies within a BPEL info or runtime-info sections. For transaction
specification S. It employs Algorithm 5.1 to detect management, we declare the transaction policies in
transaction dependencies and it asks the user for the section of the transinfo which is embedded
confirmation that it is indeed a transactional within the section of runtime info, since a
dependency. The output is a new transaction policy is a runtime constraint. Together
BPEL specification referred to as preprocessed with the other types of process information,
BPEL where conflicts are resolved. transaction policies are stored in an XML file for use
at runtime.
1919 | P a g e
7. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
Figure 7: A transaction policy declaration schema. T.M. happens just before the binding.
Currently,ODE and ActiveBPEL are two
BPEL engines supported by the SCENE
platform.
The Event Adapter maps the low-level
events from the BPEL engine onto the
binding-related events. The first version of
SeCSE event adapter is extended to support
the mapping of transaction-related events.
The Transaction Manager is a separate
component in the executor and deployed in
the Mule container (Mule is a messaging
platform based on ideas from Enterprise
Service Bus (ESB) architectures).
The Transaction Manager consists of the following
two transaction-specific components:
5.3 The Execution Framework - TransLog is responsible for managing the lifecycle
The proposed approach transforms a of transactions, such as creating transaction
generic business process into a restructured one in
instances, maintaining the status of transaction
which transactions are identified and annotated. instances, and destroying transaction instances.
Now, one needs an execution framework that is TransLog is also responsible for transferring the
richer than a simple BPEL engine. In fact, one needs information among the components in the executor.
to interpret the annotations, make sure that activities For example, it listens the transaction-
are executed according to the transaction conditions related events from the Event Adapter, and it is
and also that the binding among dependent activities responsible for the communication between
is consistent with the transaction semantics. To
Transaction Manager and JBoss Transaction Server.
achieve this, we rely on the Service Centric System
- PolicyOperator retrieves the transaction policies
Engineering (SeCSE) platform in the context of
from the XML file, and parses the transaction
which the current approach has been developed. policies, and then maps transaction policies onto the
Service Centric System Engineering is a
coordination context. It provides a set of APIs which
European sixth framework integrated project, whose are to be called by the TransLog.
primary goal is to create methods, tools, and
techniques for system integrators and service As for the implementation of transaction
providers and to support the cost-effective protocols, we rely on JBoss Transaction Server.
development of service-centric applications. The JBoss Transaction Server is an open source
SeCSE service composition methodology supports implementation of WS-Coordination,
the modeling of both the service interaction view
WSAtomicTransaction, and WS-BusinessActivity. It
and the service process view. A service integrator
provides a set of APIs to support the coordination
needs to design both the abstract flow logic and the services and transaction protocols. JBoss
decision logic of the process-based composition. Transaction Server is selectedfor this purpose
Therefore, the SeCSE composition language allows because it 1) is a complete, standalone, open source
the definition of a service composition in terms of a software tool, 2) has sufficient documentation and 3)
process and some rules that determine its dynamic and supports WS-Coordination and WS-Transaction.
behavior. Correspondingly, the flow logic can be
represented by a BPEL specification, while the
decision logic is defined by rules.
6. CONCLUSION:
Web services are being increasingly
Based on the architecture of the SeCSE
adopted by organizations in order to run their
platform, we built a transaction management tool
business more effectively and efficiently. However,
called DecTM4B. It consists of three modules,
current technologies lack the support often required
namely,
by such organizations. The success of web services
The Preprocessor for Transaction
lies, among other factors, in their reliability,
Management is used to identify and
especially when economic interests are involved.
eliminate transaction dependencies
One key feature is that of being able to deal
occurring in the original BPEL
transactionally with a set of operations, but this is far
specification. The output is the
from being easy, especially when the operations in
preprocessed BPEL specification. The
the transaction come from different remote service
SeCSE platform will deal with the binding
instances.
of abstract services before the BPEL engine
In this paper, we highlight the key requirements of
executes the BPEL specification. The
transaction management in Service-Oriented
preprocessing executed by Preprocessor for
Systems and propose a novel declarative transaction
1920 | P a g e
8. R.Soujanya, Guide: K.Venkateshwarlu / International Journal of Engineering Research and
Applications (IJERA) ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 5, September- October 2012, pp.1914-1921
management approach for web service compositions. Proc. 19th Int‟l Conf. Very Large Data
The key to implementing transaction management Bases, R. Agrawal, S. Baker, and D.A. Bell,
into BPEL processes is to consider the combination eds., pp. 581- 591, 1993.
of business logic with transactions, taking into 10) C. Sun and M. Aiello, “Requirements and
account the challenges that make it impossible to Evaluation of Protocols and Tools for
directly apply transaction models to all Transaction Management in Service Centric
BPEL processes. Systems,” Proc. Ann. Int‟l Computer
The proposal consists of first a Software and Applications Conf.
preprocessing of the BPEL to identify and manage (COMPSAC ‟07), pp. 461-466, 2007.
transaction dependencies among a group of 11) A. Lazovik, M. Aiello, and M. Papazoglou,
activities. Then, it proceeds with the annotation with “Planning and Monitoring the Execution of
transaction policies. Finally, the interpretations of Web Service Requests,” Int‟l J. Digital
the declared transaction policy are specified as Libraries, vol. 6, no. 3, pp. 235-246, 2006.
event-action condition rules to be processed at 12) M. Aiello and A. Lazovik, “Monitoring
runtime. Assertion-Based Business Process,” Int‟l J.
Cooperative Information Systems, vol. 15,
REFERENCES no. 3, pp. 359-390, 2006.
1) WS-C, “Web Services Coordination (WS- 13) B. Haugen and T. Fletcher, “Multi-Party
Coordination),” technical report, Arjuna Electronic Business Transactions. Version
Technologies Ltd., BEA Systems, Hitachi 1.1,” technical report, UN, 2002.
Ltd., IBM, IONA Technologies, and
Microsoft, 2007. AUTHOR BIOGRAPHIES:
2) WS-AT, “Web Services Atomic
Transaction (WS-AtomicTransaction),
Version 1.1,” technical report, Arjuna
Technologies Ltd., BEA Systems, Hitachi
Ltd., IBM, IONA Technologies, and R.Soujanya received her B.Tech,
Microsoft, 2007. Degree in Computer science and information
3) WS-BA, “Web Services Business Activity technology from G.Pulla Reddy Engineering
Framework (WSBusinessActivity), Version College, Kurnool India, in 2010. She is pursuing
1.1,” technical report, Arjuna Technologies her M.Tech in Software Engineering in Sri Kottam
Ltd., BEA Systems, Hitachi Ltd., IBM, Tulasi Reddy Memorial College, Kondair India. Her
IONA Technologies, and Microsoft, 2007. area of interest is in the field of Service oriented
4) BPEL, “Business Process Execution computing, Wireless Sensor Networks and Software
Language for Web Services Version 1.1,” Testing.
technical report, IBM, Microsoft, BEAT,
SAP, and Siebel Systems, 2003.
5) C. Sun and M. Aiello, “Requirements and
Evaluation of Protocols and Tools for
Transaction Management in Service Centric
Systems,” Proc. Ann. Int‟l Computer
Software and Applications Conf.
(COMPSAC ‟07), pp. 461-466, 2007. Mr.M.Venkateshwarlu Associate Professor,
6) A. Erradi, P. Maheshwari, and V. Tosic, completed B.Tech in Computer Science &
“Recovery Policies for Enhancing Web Engineering in Sri Kalahastheeshwara Institute of
Services Reliability,” Proc. IEEE Int‟l Technology, Sri Kalahasthi, and M.Tech in
Conf. Web Services (ICWS ‟06), pp. 189- Computer Science & Engineering in Sri Kottam
196, 2006. Tulasi Reddy Memorial College of Engg, Affiliated
7) A.Portilla, “Providing Transactional to JNTU Hyderabad. His interested areas are
Behavior to Services Coordination,” Proc. Wireless Sensor Networks, Artificial Intelligence.
Very Large Data Bases (VLDB) PhD He attended two international conferences on
Workshop, vol. 170, 2006. MANET`s and one national level conference on
8) S. Loecher, “Model-Based Transaction Networks. He attended Mission 10x program
Service Configuration for Component- conducted by Wipro. Presently he was acting as The
Based Development,” Component-Based Convener of R&D cell in SKTRMCE. Kondair,
Software Eng., pp. 302-309, 2004. Mahaboob Nagar (Dt). He had total 07 years of
9) P.W.P.J. Grefen, “Combining Theory and teaching experience. Currently he was working as
Practice in Integrity Control: A Declarative Associate Professor in CSE Department in KTM
Approach to the Specification of a College of Engineering,
Transaction Modification Subsystem,”
1921 | P a g e