Book Image

SOA Cookbook

By : Michael Havey
Book Image

SOA Cookbook

By: Michael Havey

Overview of this book

<p>SOA Cookbook covers process-oriented SOA. BPEL is the best-known language in this area, and this book presents numerous BPEL examples. It also studies proprietary vendor process languages such as TIBCO's BusinessWorks and BEA's Weblogic Integration. If you are building SOA processes in the field, chances are you are using one of the languages discussed in SOA Cookbook. The book assumes that the reader is comfortable with XML and web services.<br /><br />Author Michael Havey works with SOA in the field for TIBCO (and previously for IBM, BEA, and Chordiant). SOA Cookbook is Michael's second book. Essential Business Process Modeling, his first book, was published in 2005.</p>

Related Content you might be interested in

Current Title:

Small book image
SOA Cookbook
Michael Havey
Sep, 2008 | 268 pages
No titles found
Table of Contents (14 chapters)
SOA Cookbook
SOA Cookbook
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
Preface
Preface
Free Chapter
1
SOA Survival Guide
SOA Survival Guide
SOA from 184 Billion Feet
The Model Stack
The Secret They Couldn't Hide—SOA is Process-Oriented
Summary
2
Drawing SOA Architecture
Drawing SOA Architecture
The 4+1 Structure of an SOA Architecture Document
Using ARIS Methodology to Organize the Logical View
Example—Competitive Enrollment
Data and Service Interfaces for Retailer Enrollment
BPMN Processes for Retailer Enrollment
Service Composition of Retailer Enrollment Using SCA
On Modeling Tools
Summary
3
Separating BPM and SOA Processes
Separating BPM and SOA Processes
The Model Stack
Design Tips on Separating BPM and SOA
Example—Process for Handling Credit Card Disputes
Disputes on the Model Stack
BPM-Oriented Disputes with TIBCO
SOA-Oriented Disputes with BEA
About the Examples
Summary
4
Modeling Orchestration and Choreography
Modeling Orchestration and Choreography
Choreography versus Orchestration
Examples—Energy Enrollment, Email Bank Transfer
Modeling Choreography in BPMN
The Invisible Hub in BPEL
Choreography in WS-CDL with Pi4SOA
Tips on Modeling Orchestration
About the Examples
Summary
5
Short and Long-Running Processes
Short and Long-Running Processes
Process Duration—the Long and Short of It
How to Keep Long-Running State
Combining Short-Running Processes with State in TIBCO's BusinessWorks
Fast Short-Running BPEL
About the Examples
Summary
6
Flat Form
Flat Form
Our Use Case: Credit Card Disputes
Disputes in BPEL—Naïve Form
Disputes in BPEL—Flat State Machine
Disputes in BPEL: Flat Event Loop
Disputes in BPEL: Flat Control Flow
Flat Concurrency
Advantages and Disadvantages of Flat Form
About the Examples
Summary
7
Dynamic Processes and the Change Problem
Dynamic Processes and the Change Problem
The Change Problem
Process-Oriented Methods
Rule-Oriented Methods
Goal-Oriented Methods
About the Examples
Summary
8
Simulating SOA
Simulating SOA
Simulation, and Why it Suits SOA
The Ideal SOA Simulator
BPEL Simulation Examples
Interpreting the Results of a Simulation
About the Examples
Summary
9
Measuring SOA Complexity
Measuring SOA Complexity
Applying McCabe's Formula for BPEL and TIBCO BusinessWorks
A Better Formula for BPEL
About the Examples
Further Reading
Summary

The 4+1 Structure of an SOA Architecture Document

Few accounts of architectural methodology are as succinct as Phillippe Kruchten's 15-page paper Architectural Blueprints: The "4+1" View Model of Software Architecture. Kruchten (IEEE Software, 12 (6) 42-50, November 1995) published the paper in 1995 while helping to develop the Rational Unified Process. Software architectures at the time, Kruchten notes, were poorly structured, and manifested this poor structure by cramming too much varied detail into a single diagram. In too many diagrams it is difficult, Kruchten argues, to decide which boxes are machines and which are logical software modules, or which arrows mean control flow and which mean data flow.

Kruchten proposes that architecture be presented as four separate 'technical' views:

  • Logical: The conceptual object model.

  • Development: The organization of the software in the development environment. ...

Previous Section
End of Section 2
Next Section