BPELforum.com

Business Process Execution Language (BPEL)

Similar Posts

  • Web Services
  • Service-Oriented Architecture (SOA): Concepts, Technology, and Design
  • Living With Urban Environmental Health Risks: The Case Of Ethiopia
  • Service-Oriented Architecture : Concepts, Technology, and Design
  • Test and Analysis of Web Services

A Competitive Analysis of Major Service Vendors and Their SOA Service Capabilities: Part I

May 2, 2010 by BPELforum

Product Description

This study examines the SOA competitive landscape from a services perspective by profiling and then comparing eight major service vendors on IDC’s Leadership Grid. “Each service provider has been on its own SOA journey for many years and has developed an increasingly sophisticated response to the changing market needs around SOA. The service vendors have matured significantly in their ability to provide SOA services since IDC evaluated them a few years ago, yet this maturation has not happened in the same way or at the same pace. There is still a great deal of variability among the various vendors which makes it an especially intriguing and interesting industry to watch,” states Marianne Hedin, research manager, IDC Worldwide Services Research Program.

A Competitive Analysis of Major Service Vendors and Their SOA Service Capabilities: Part I

Filed Under: SOA Books Tagged With: Analysis, Capabilities, Competitive, Competitive Analysis, Idc, Journey, Landscape, Leadership Grid, Major, Maturation, Pace, Part, Perspective, Product Description, Service, Service Capabilities, Service Provider, Service Vendors, Their, Variability, Vendors, Worldwide Services

Figthing Process Fragmentation

April 28, 2010 by BPELforum

Professionals all over the world in Information Technology are fighting the never ending battle against project creep, missed deadlines and cost overruns. The lack of success in doing so seems to indicate that there is a deeper problem that has to be solved first. After analyzing customer projects for 20 years, I may have discovered a key element of this problem. Well, it actually is not a unique discovery, because it is likely that every professional in IT has run into the same situation but has looked at the consequences and not at the cause.

It seems that process fragmentation is the root cause of most unsolved IT problems.

It starts with the meta-process of IT Change Management that requires that a business application (made up from processes, tasks and actvities itself) is first analysed, then developed, tested, integration tested, rolled out and then put into production by different IT departments that distance themselves ever more from the business user. Current Change Management has however emerged over many years because of a quality requirement that is totally unreasonable in its expecations and thus has driven IT applications off the cost scale. 99.99% availability makes sense for infrastructure but not for a business service front-end. It is also not necessary as we can see from Internet use.

Here a more human problem enters the landscape. What is it that management wants from IT? One of the interests is higher productivity, meaning that less people can achieve a certain amount of throughput. The second is ensuring the quality of the work performed independant of the people and ideally enable an untrained person to perform the work needed. People are in fact put last, and that creates the problem for IT. Putting people first – employees AND customers – would make a world of difference. People are actually seen seperated from the business when they really are the business.

The current approach to the above is to analyse the business process and encode decision making into rigid rules. The resultant simplistic 2D-flowcharts and IF/THEN rules can however not properly represent the business activity that the user needs to perform his job well and to user satisfaction. It is pretty obvious that a fragmented, rigid 2D flowchart cannot represent a 4D event-driven, dynamic world that is not fragmented. Process or application monitoring does not help, as it only tells you if the defined processes are executed as defined. Business intelligence might tell you that some expected numbers are wrong but not where to improve the process. Even if you know how to improve the process, you then need it developed, tested and put into production. This loop is long and expensive as mentioned before. The business also looses its ability to adapt to market changes.

Right here, IT Change Management has to change and consolidate with application or process development. Ideally, it would already include application or process analysis with the resultant documentation that becomes part of the application. Right here, it too becomes obvious that state-of-the-art application development using programming languages such as Cobol, Java or C++ with APIs are unable to cope. This is where the SOA concept developed that tries to create a flexible definable layer between the front-end application and the back-end service. But current SOA approaches do not deliver these aspects of Change Management and are built on either Java programming with UML modelling or jBPEL with BPM modelling. Extactly that creates another even more complex layer of fragmentation and spoils the potential benefits of SOA. Adding additional fragmentation layers such as outsourcing and governance simply does not seem the right approach to achieve shorter projects and more agility.

The application solution is to see business process not as step-by-step fragments but as a collection of business services that do not much more than bundle and hold the case related business communication and information content. The content is state/event driven and implicitly creates the progression of the business case to its completion. Business professionals must be able to interactively define the business services they need (I propose by recording or training) without the use of flowchart analysis tools that are completely abstract to a business user and do mostly require later use of programming tools anyway.

The current IT process segment of defining and testing such services (processes) must not be seen as a programming effort but as part of normal business activity. The business department must be agile enough to provide the input to the power users defining services and be willing to test and fine-tune such applications. A gradual and interactive development approach like that it not really new but was first suggested in 1990 as Extreme Programming using programming languages. The difficulty of achieving reasonable system stability with compiled languages ended that approach. The project benefits of Extreme Programming can however be achieved with an application platform that includes analysis tools, deployment and monitoring/tuning as part of it‘s Change Management.

In short, what IT needs is a defragmented approach to Change Management and a defragmented approach to creating business services (a.k.a. as processes). In fact, that implies that a much further reaching consolidation of user frontend processes is necessary, and that includes BPM, CRM , ECM and SOA.

Max J. Pucher is the founder and current Chief Architect of ISIS Papyrus Software, a globally operating company that specializes in Arificial Intelligence for Business Process and Communication. He has written several books, frequently speaks and writes on IT and holds several patents.

Filed Under: BPEL News Tagged With: Business Application, Business Service, Business User, Consequences, Customer Projects, Discovery, Figthing, Fragmentation, Information Technology, Infrastructure, Internet Use, Landscape, Meta, Overruns, Process, Productivity, Quality Requirement, Root Cause, Scale 99, Seperated, Throughput, Untrained Person

Perl and XML

April 28, 2010 by BPELforum

Product Description
Perl & XML is aimed at Perl programmers who need to work with XML documents and data. The book covers all the major modules for XML processing in Perl. But this book is more than just a listing of modules; it gives a complete, comprehensive tour of the landscape of Perl and XML, making sense of the myriad of modules, terminology, and techniques.This book covers:

    parsing XML documents and writing them out again

    working with event streams and SAX

    tree processing and the Document Object Model

    advanced tree processing with XPath and XSLT

Most valuably, the last two chapters of Perl & XML give complete examples of XML applications, pulling together all the tools at your disposal. All together, Perl and XML is the single book that gives you a solid grounding in XML processing with Perl.

Perl and XML

Filed Under: XML Books Tagged With: Book Covers, Book Writing, Chapters, Document Object Model, Landscape, Myriad, Perl, Perl Examples, Perl Programmers, Perl Xml, Product Description, Sax, Streams, Xml Applications, Xml Data, Xml Documents, Xml Examples, Xpath, XSLT

Beginning XML, 4th Edition

April 27, 2010 by BPELforum

  • ISBN13: 9780470114872
  • Condition: NEW
  • Notes: Brand New from Publisher. No Remainder Mark.

Product Description

When the first edition of this book was written, XML was a relatively new language but already gaining ground fast and becoming more and more widely used in a vast range of applications. By the time of the second edition, XML had already proven itself to be more than a passing fad, and was in fact being used throughout the industry for an incredibly wide range of uses. With the third edition, it was clear that XML was a mature technology, but more important, it became evident that the XML landscape was dividing into several areas of expertise. Now in this edition, we needed to categorize the increasing number of specifications surrounding XML, which either use XML or provide functionality in addition to the XML core specification.

So what is XML? It’s a markup language, used to describe the structure of data in meaningful ways. Anywhere that data is input/output, stored, or transmitted from one place to another, is a potential fit for XML’s capabilities. Perhaps the most well-known applications are web-related (especially with the latest developments in handheld web access—for which some of the technology is XML-based). However, there are many other non-web-based applications for which XML is useful—for example, as a replacement for (or to complement) traditional databases, or for the transfer of financial information between businesses. News organizations, along with individuals, have also been using XML to distribute syndicated news stories and blog entries.

This book aims to teach you all you need to know about XML—what it is, how it works, what technologies surround it, and how it can best be used in a variety of situations, from simple data transfer to using XML in your web pages. It answers the fundamental questions:

* What is XML?

* How do you use XML?

* How does it work?

* What can you use it for, anyway?

This book is for people who know that it would be a pretty good idea to learn XML but aren’t 100 percent sure why. You’ve heard the hype but haven’t seen enough substance to figure out what XML is and what it can do. You may be using development tools that try to hide the XML behind user interfaces and scripts, but you want to know what is really happening behind the scenes. You may already be somehow involved in web development and probably even know the basics of HTML, although neither of these qualifications is absolutely necessary for this book.

What you don’t need is knowledge of markup languages in general. This book assumes that you’re new to the concept of markup languages, and we have structured it in a way that should make sense to the beginner and yet quickly bring you to XML expert status.

The word “Beginning” in the title refers to the style of the book, rather than the reader’s experience level. There are two types of beginner for whom this book is ideal:

* Programmers who are already familiar with some web programming or data exchange techniques. Programmers in this category will already understand some of the concepts discussed here, but you will learn how you can incorporate XML technologies to enhance those solutions you currently develop.

* Those working in a programming environment but with no substantial knowledge or experience of web development or data exchange applications. In addition to learning how XML technologies can be applied to such applications, you will be introduced to some new concepts to help you understand how such systems work.

The subjects covered in this book are arranged to take you from novice to expert in as logical a manner as we could. This Fourth Edition is structured in sections based on various areas of XML expertise. Unless you are already using XML, you should start by reading the introduction to XML in Part I. From there, you can quickly jump into specific areas of expertise, or, if you prefer, you can read through the book in order. Keep in mind that there is quite a lot of overlap in XML, and that some of the sections make use of techniques described elsewhere in the book.

* The book begins by explaining what exactly XML is and why the industry felt that a language like this was needed.

* After covering the why, the next logical step is the how, so it shows you how to create well-formed XML.

* Once you understand the whys and hows of XML, you’ll go on to some more advanced things you can do when creating your XML documents, to make them not only well formed, but valid. (And you’ll learn what “valid” really means.)

* After you’re comfortable with XML and have seen it in action, the book unleashes the programmer within and looks at an XML-based programming language that you can use to transform XML documents from one format to another.

* Eventually, you will need to store and retrieve XML information from databases. At this point, you will learn not only the state of the art for XML and databases, but also how to query XML information using an SQL-like syntax called XQuery.

* XML wouldn’t really be useful unless you could write programs to read the data in XML documents and create new XML documents, so we’ll get back to programming and look at a couple of ways that you can do that.

* Understanding how to program and use XML within your own business is one thing, but sending that information to a business partner or publishing it to the Internet is another. You’ll learn about technologies that use XML that enable you to send messages across the Internet, publish information, and discover services that provide information.

* Since you have all of this data in XML format, it would be great if you could easily display it to people, and it turns out you can. You’ll see an XML version of HTML called XHTML. You’ll also look at a technology you may already be using in conjunction with HTML documents called CSS. CSS enables you to add visual styles to your XML documents. In addition, you’ll learn how to design stunning graphics and make interactive forms using XML.

* Finally, the book ends with a case study, which should help to give you ideas about how XML can be used in real-life situations, and which could be used in your own applications.

This book builds on the strengths of the earlier editions, and provides new material to reflect the changes in the XML landscape—notably XQuery, RSS and Atom, and AJAX. Updates have been made to reflect the most recent versions of specifications and best practices throughout the book. In addition to the many changes, each chapter has a set of exercise questions to test your understanding of the material. Possible solutions to these questions appear in Appendix A.

Part I: Introduction: The introduction is where most readers should begin. The first three chapters introduce some of the goals of XML as well as the specific rules for constructing XML. Once you have read this part you should be able to read and create your own XML documents.

Chapter 1: What Is XML?: This chapter cover some basic concepts, introducing the fact that XML is a markup language (a bit like HTML) whereby you can define your own elements, tags, and attributes (known as a vocabulary). You’ll see that tags have no presentation meaning—they’re just a way to describe the structure of the data.

Chapter 2: Well-Formed XML: In addition to explaining what well-formed XML is, we offer a look at the rules that exist (the XML 1.0 and 1.1 Recommendations) for naming and structuring elements—you need to comply with these rules in order to produce well-formed XML.

Chapter 3: XML Namespaces: Because tags can be made up, you need to avoid name conflicts when sharing documents. Namespaces provide a way to uniquely identify a group of tags, using a URI. This chapter explains how to use namespaces.

Part II: Validation: In addition to the well-formedness rules you learn in Part I, you will most likely want to learn how to create and use different XML vocabularies. This Part introduces you to DTDs, XML Schemas, and RELAX NG: three languages that define custom XML vocabularies. It also shows you how to utilize these definitions to validate your XML documents.

Chapter 4: Document Type Definitions: You can specify how an XML document should be structured, and even provide default values, using Document Type Definitions (DTDs). If XML conforms to the associated DTD, it is known as valid XML. This chapter covers the basics of using DTDs.

Chapter 5: XML Schemas: XML Schemas, like DTDs, enable you to define how a document should be structured. In additio…Amazon.com Review
Beginning XML provides a complete course in the Extensible Markup Language (XML) with an unusually gradual learning curve. In fact, the introduction states that the book is “for people who know that it would be a pretty good idea to learn the language, but aren’t 100 percent sure why.” Despite its recognition of the fuzziness of readers’ understanding of the technology, the book delivers a rather comprehensive study of XML.

Very little space is wasted detailing the history of XML and its relation to SGML, as is the case in many other titles. The argument for the importance of XML is made quickly, and the basics of well-formed syntax are tackled right off. One notable distinction of this book is its excellent coverage of related technologies, such as cascading style sheets (CSS) and relational databases.

In addition to discussing the crucial companion standards to the core XML language (DTDs, XSL, and XSLT), the book adds a nice perspective to the broad range of applications in which XML can play a role. One section, “Other Uses for XML,” illustrates how XML can be used to serialize object models, creating stateless objects and utilizing the Resource Description Framework (RDF). Case studies on–among other things–how XML can be used to build discussion groups, and provide B2B data transfer, round out the text. This book is perfect for Web programmers who are turning their attention to XML for the first time. It imparts a solid understanding of the XML forest and XML trees. –Stephen W. Plain

Topics covered:

  • Well-formed XML
  • Cascading style sheets (CSS)
  • XSLT and Xpath
  • Document Object Model (DOM)
  • Simple API for XML (SAX)
  • XML/database integration schemas
  • Document Type Definitions (DTDs)
  • Namespaces
  • B2B data-transfer applications
  • Discussion group applications

Beginning XML, 4th Edition

Filed Under: XML Books Tagged With: Beginning, Capabilities, Core Specification, Edition, Fad, Financial Information, Functionality, Fundamental Questions, Handheld Web, Input Output, Landscape, Markup Language, Mature Technology, New Language, News Stories, Product Description, Remainder Mark, Syndicated News, Traditional Databases, Web Access, Web Pages, Xml Core

RSS BPELpros.com

  • BizTalk Server
  • IBM
  • OpenLink Software
  • SAP AG

Return to top of page

Copyright © 2012 · Delicious Theme on Genesis Framework · WordPress · Log in