IBM press executing SOA a practical guide for the service oriented architect may 2008 ISBN 0132353741

ExecutingSOA:APracticalGuideforthe
Service-OrientedArchitect
byNorbertBieberstein;RobertG.Laird;Dr.Keith
Jones;TilakMitra
Publisher:IBMPress
PubDate:May05,2008
PrintISBN-10:0-13-235374-1
PrintISBN-13:978-0-13-235374-8
eTextISBN-10:0-13-714947-6
eTextISBN-13:978-0-13-714947-6
Pages:240
TableofContents|Index

Overview
TheExpert,PracticalGuidetoSucceedingwithSOAinthe
Enterprise
InExecutingSOA,fourexperiencedSOAimplementersshare
realistic,proven,"from-the-trenches"guidanceforsuccessfully
deliveringoneventhelargestandmostcomplexSOAinitiative.
Thisbookfollowsupwheretheauthors'best-sellingServiceOrientedArchitectureCompassleftoff,showinghowto
overcomekeyobstaclestosuccessfulSOAimplementationand
identifyingbestpracticesforallfacetsofexecution–technical,
organizational,andhuman.Amongtheissuesitaddresses:
introducingaservicesdisciplinethatsupportscollaborationand
informationprocesssharing;integratingserviceswith
preexistingtechnologyassetsandstrategies;choosingtheright
rolesfornewtools;shiftingculture,governance,and
architecture;andbringinggreateragilitytotheentire
organizationallifecycle,notjustisolatedprojects.
ExecutingSOAisanindispensableresourceforeveryenterprise
architect,technicalmanager,andITleadertaskedwithdriving

valuefromSOAincomplexenvironments.
Coverageincludes
·ImplementingSOAgovernancethatreflectstheorganization's
strategicandbusinessfocus
·RunningSOAprojectssuccessfully:practicalguidelinesand
provenmethodologiesaroundservicemodelinganddesign
·Leveragingreusableassets:makingthemostofyourSOA
repository
·Enablingthearchitecttochoosethecorrecttoolsand
productscontainingthefeaturesrequiredtoexecuteonthe
SOAmethodforservicedesignandimplementation
·Defininginformationservicestogettherightinformationto
therightpeopleattherighttime
·IntegratingSOAwithWeb2.0andotherinnovativeproducts
andsolutions
·ProvidinghighlyusablehumaninterfacesinSOA
environments
|


ExecutingSOA:APracticalGuideforthe
Service-OrientedArchitect
byNorbertBieberstein;RobertG.Laird;Dr.Keith
Jones;TilakMitra
Publisher:IBMPress
PubDate:May05,2008
PrintISBN-10:0-13-235374-1
PrintISBN-13:978-0-13-235374-8

eTextISBN-10:0-13-714947-6
eTextISBN-13:978-0-13-714947-6
Pages:240
TableofContents|Index

Copyright
IBMPress:ThedeveloperWorks®Series
Foreword
Acknowledgments
AbouttheAuthors
Chapter1.IntroducingSOA
Section1.1.SOAinRetrospect
Section1.2.NewItemstoConsider
Section1.3.WhatMakesThisBookDifferent?
Section1.4.WhoIsThisBookFor?
Section1.5.WhatIsCoveredinThisBook?
Section1.6.LinkstodeveloperWorksArticles
Section1.7.References
Endnotes
Chapter2.UnveilingtheBenefits
Section2.1.WhytheBusinessShouldCareAboutSOA
Section2.2.Architecture
Section2.3.FocusonBusinessArchitecture
Section2.4.BusinessProcess


Section2.5.BusinessComponents
Section2.6.LiftingtheVeil
Section2.7.LinktodeveloperWorksArticle
Section2.8.References

Endnotes
Chapter3.SOAGovernance
Section3.1.GovernanceoftheSOAStrategy
Section3.2.OrganizingforSOA
Section3.3.SOAGovernanceConsiderations
Section3.4.Conclusion
Section3.5.LinkstodeveloperWorksArticles
Section3.6.References
Endnotes
Chapter4.AMethodologyforServiceModelingandDesign
Section4.1.AnSOAReferenceArchitecture
Section4.2.ServiceOrientedModelingandArchitecture
Section4.3.Conclusion
Section4.4.LinkstodeveloperWorksArticles
Section4.5.References
Chapter5.LeveragingReusableAssets
Section5.1.WhatIsanAsset?
Section5.2.ServiceReuse
Section5.3.WhatMakesanSOAServiceReusable?
Section5.4.ReusablePatterns
Section5.5.MakingLegacyReusable:HarvestingReusable
ComponentsfromaLegacyMonolithicApplication
Section5.6.Conclusion
Section5.7.LinkstodeveloperWorksArticles
Section5.8.References
Chapter6.RealizationofServices
Section6.1.RealizingtheSOALifecycle
Section6.2.PremodelingActivitiesinanSOA

Section6.3.ModelingServicesinanSOA
Section6.4.AssemblingServicesinanSOA
Section6.5.DeployingServicesinanSOA
Section6.6.ManagingServicesinanSOA
Section6.7.TheSOAProgrammingModel
Section6.8.ArchitectureandDesignConsiderations
Section6.9.Conclusion
Section6.10.LinkstodeveloperWorksArticles
Section6.11.References
Chapter7.InformationServices
Section7.1.DataorInformationServices
Section7.2.Data,SOA,andLooseCoupling
Section7.3.FromDataSourcestoConsumers
Section7.4.QualitiesofData
Section7.5.DataProcesses
Section7.6.DataServiceProviderLogicPatterns
Section7.7.CompositeServiceLogic
Section7.8.SemanticInteroperability
Section7.9.Conclusion
Section7.10.LinkstodeveloperWorksArticles
Section7.11.References
Chapter8.CollaborationUnderSOA:TheHumanAspects
Section8.1.WhatDoesSOAMeantoPeople?
Section8.2.Web2.0andSOA
Section8.3.BuildingtheSOACollaborationEnvironment
Section8.4.BenefitsfromSOAtoEnterpriseOperations
Section8.5.Conclusion
Section8.6.LinkstodeveloperWorksArticles
Section8.7.References
Endnotes

Chapter9.TheFutureofSOA
Section9.1.CompositeBusinessServicesandComposite


Applications
Section9.2.StandardizationofIndustryModelsand
Industry-WideSOAEnablement
Section9.3.PackagedApplicationsMutatingtoPoint
Solutions
Section9.4.HybridArchitecturalApproachofSOAandEDA
Section9.5.SOAMethodologyEvolution
Section9.6.BusinessProcessesandSOANotWithout
People
Section9.7.SOAMetrics
Section9.8.UbiquitousSOAintheEnterprise
Section9.9.GlobalUseofSOA
Section9.10.SOAOpenstheAmateurSoftwareServices
Market
Section9.11.Conclusion
Section9.12.LinkstodeveloperWorksArticles
Section9.13.References
Endnotes
Index


Copyright
developerWorks®Series
Theauthorsandpublisherhavetakencareinthepreparationof
thisbook,butmakenoexpressedorimpliedwarrantyofany
kindandassumenoresponsibilityforerrorsoromissions.No

liabilityisassumedforincidentalorconsequentialdamagesin
connectionwithorarisingoutoftheuseoftheinformationor
programscontainedherein.
©Copyright2008byInternationalBusinessMachines
Corporation.Allrightsreserved.
NotetoU.S.GovernmentUsers:Documentationrelatedto
restrictedright.Use,duplication,ordisclosureissubjectto
restrictionssetforthinGSAADPScheduleContractwithIBM
Corporation.
IBMPressProgramManagers:TaraWoodman,ElliceUffer
Coverdesign:IBMCorporation
AssociatePublisher:GregWiegand
MarketingManager:KourtnayeSturgeon
Publicist:HeatherFox
AcquisitionsEditor:KatherineBull
DevelopmentEditor:GinnyBessMunroe
ManagingEditor:KristyHart
Designer:AlanClements
ProjectEditor:ChelseyMarti
CopyEditor:KeithCline
Indexer:BradHerriman
SeniorCompositor:GloriaSchurick
Proofreader:WaterCrestPublishing
ManufacturingBuyer:DanUhrig
PublishedbyPearsonplc
PublishingasIBMPress
IBMPressoffersexcellentdiscountsonthisbookwhenordered
inquantityforbulkpurchasesorspecialsales,whichmay

includeelectronicversionsand/orcustomcoversandcontent
particulartoyourbusiness,traininggoals,marketingfocus,and
brandinginterests.Formoreinformation,pleasecontact:
U.S.CorporateandGovernmentSales
1-800-382-3419

ForsalesoutsidetheU.S.,pleasecontact:
InternationalSales

Thefollowingtermsaretrademarksorregisteredtrademarksof
InternationalBusinessMachinesCorporationintheUnited
States,othercountries,orboth:IBM,theIBMlogo,IBMPress,
CICS,ComponentBusinessModel,DataPower,developerWorks,
IMS,Lotus,MVS,OMEGAMON,Rational,RationalUnified
Process,Redbooks,RequisitePro,RUP,Tivoli,TivoliEnterprise
Console,WebSphereandz/OS.JavaandallJava-based
trademarksaretrademarksofSunMicrosystems,Inc.inthe
UnitedStates,othercountries,orboth.Microsoft,Windows,
WindowsNT,andtheWindowslogoaretrademarksofMicrosoft
CorporationintheUnitedStates,othercountries,orboth.Linux
isaregisteredtrademarkofLinusTorvaldsintheUnitedStates,
othercountries,orboth.Othercompany,product,orservice
namesmaybetrademarksorservicemarksofothers.
LibraryofCongressCataloging-in-PublicationData

ExecutingSOA:apracticalguidefortheserviceorientedarchitect/NorbertBieberstein...[etal.].—1sted.
p.cm.
Includesindex.
ISBN0-13-235374-1
1.Webservices.2.Computernetworkarchitectures.3.Businessenterpris

—
Computernetworks.4.Computerarchitecture.I.Bieberstein,Norbert.


TK5105.88813.E962008
004.6'5—dc22
2008006598
Allrightsreserved.Thispublicationisprotectedbycopyright,
andpermissionmustbeobtainedfromthepublisherpriorto
anyprohibitedreproduction,storageinaretrievalsystem,or
transmissioninanyformorbyanymeans,electronic,
mechanical,photocopying,recording,orlikewise.For
informationregardingpermissions,writeto:
PearsonEducation,Inc
RightsandContractsDepartment
501BoylstonStreet,Suite900
Boston,MA02116
Fax(617)6713447
ISBN-13:978-0-13-235374-8
TextprintedintheUnitedStatesonrecycledpaperatR.R.
DonnelleyinCrawfordsville,Indiana.
FirstprintingMay2008

Dedication
Tomyfamily,mymother,mywife,Joanna,andmy
daughters,Katherina,Caroline,andJulia.
—NorbertBieberstein
I'dliketodedicatethisbooktoAmyLaird,mywife,who
wasveryinsightfulinprovidingthefirstlevelofreviewand
wassupportivethroughout.Tomysons,ThomasandJack,

whodidn'tgettoplaywiththeirdadquitesomuchwhilehe
waswriting.
—RobertG.Laird


Tomywife,Gillian,andmysons,SimonandPhilip.
—Dr.KeithJones
Tomyveryspecialwife,Tania,myfather,Dibakar,andmy
mom,Manjusree,withoutwhosecontinuoussupportthis
wouldnothavebeenpossible.Idedicatethisbooktomy
greatgrandfather,thelateNarendranathMitra,arenowned
Bengalinovelistparexcellence,whohasbeenmy
inspirationtotakeupthepen.
—TilakMitra


IBMPress:ThedeveloperWorks®Series
TheIBMPressdeveloperWorksSeriesrepresentsaunique
undertakinginwhichprintbooksandtheWebaremutually
supportive.Thepublicationsinthisseriesarecomplementedby
theirassociationwithresourcesavailableatthedeveloperWorks
Websiteonibm.com.Theseresourcesincludearticles,tutorials,
forums,software,andmuchmore.
Throughtheuseoficons,readerswillbeabletoimmediately
identifyaresourceondeveloperWorkswhichrelatestothat
pointofthetext.Asummaryoflinksappearsattheendofeach
chapter.Additionally,youwillbeabletoaccessanelectronic
guideofthedeveloperWorkslinksandresourcesthrough
ibm.com/developerworks/dwbooksthatreference
developerWorksSeriespublications,deepeningthereader's

experiences.
AdeveloperWorksbookoffersreaderstheabilitytoquickly
extendtheirinformationbasebeyondthebookbyusingthe
deepresourcesofdeveloperWorksandatthesametime
enablesdeveloperWorksreaderstodeepentheirtechnical
knowledgeandskills.
ForafulllistingofdeveloperWorksSeriespublications,please
visit:ibmpressbooks.com/dwseries.


Foreword
Service-orientedarchitecture(SOA)isnolongernew.Indeed,it
suffersfromsomeretrenchmentandbacklashasthe"hype
curve"settles,withmanypointingtoexamplesoffailed
attempts.Whyisthat?Ifthisdirectionwassocompelling,why
aresometurningtoadegreeofskepticismandoutright
cynicism?Themajorreasonliesinourcollectivefailureto
understandthatthiskindoftransitionisdifficultandrequires
discipline,in-depthunderstanding,andactiveinvolvementfrom
thebusinessaswellastheITinfrastructure.Disciplineis
neededincollaborativealignmentandcross-groupprocesses
thatwetendtoassociatewithbroaderorganizationalthinking—
notindividual,localized"quickfixes"orsilos.Asaresult,many
initialattemptsfailforavarietyofgoodreasons:
Afailuretoestablisheffectivegovernanceorevenrealize
thatgovernancemustchangetoestablishenduringbenefits
indeliveringshared,useful,andeffectiveservices.
Anattempttointroduceaservicesdisciplineinto
organizationalsiloswithoutdrasticallyalteringthecultureof
collaborationandinformation-processsharing.This

oversightabsolutelyresultsinfailure.
Afailuretounderstandhowtointegratenewthinking
aroundservicesintopreexistingtechnologyassetsand
directions.
Believingthatasingletechnologyortoolwilldeliverthe
desiredresults.
Believingthatspeedcomesfromagility,whereagility
equatestoasimplisticviewof"deliveringquickly"on
isolated,individualprojectswithoutregardtoorganizational
lifecycle.Thisisotherwiseknownasunstructuredchaos.
Inmyview,thefundamentalmotivationorreasontopursuean
SOAismoreprevalenttodaythaneverbefore.Thepressureto


competewithgreaterspeedandinnovationasabusinessmodel
remains.Thepressureonenterprises,ecosystems,andsupply
chainstoglobalizeisaccelerating.ThedependencyonIT
systemstoscalebusinessesconstantlygrows,andtechnology
continuestopervadeallfacetsofcommerceandofeveryday
life.
Manyofthescaleissuesinanyshiftinbusinessmodelscomes
fromthegrowingreachandchoiceaffordedbytheevermore
ubiquitousInternet.TheInternetischangingandevolving.
Bandwidthcontinuestoincrease,andtheresultingnetwork
effectsareprovidingopportunityfornewbusinessesand
businessmodelswhilealsowreakinghavocontheexisting
ones.Allwehavetodoislooktoeverydayexamplesinthe
musicindustry(indeed,inentertainmentasawhole).Telecom
serviceproviders(TSPs)areclassicexampleswherevertical
integrationofindustryandthebillingmodelshavebeentorn

asunderbytheintroductionofpervasiveIP-basedservicesand
devices.Theinteractionofthetwo(entertainmentandTSPs)is
evenmoredramaticandhasdownstreameffectsonconsumer
electronics,automotive,andsoon.Thegrowingchoicesand
resultingshiftsinglobalsupplychainsandsourcingaffect
everythingfrommanufacturedgoodstointellectualproperty
andtalent.Thereisnoplacetohide.
ITsystemsareforcedtoenableortoleadthistrend;ifnot,the
associatedbusinesseswillfailtocompeteandfadeinto
irrelevance.Keytoenablingflexibilityandscalearethetenets
ofservice-orientedarchitectures.Ashasbeensaidbefore,there
isnomagicinSOA.Inmanyways,itistheevolutionofthe
ever-presentandoldconceptof"modularity"andstructural
decompositionappliedtobetteralignmentofITandbusinessat
aglobal,openscale.Howevertherawscaleissuesof
modularityandsharinginsuccessfulservices-based
architecturestobedeployedontheInternetinsupportoftruly
globalizedbusinesshasneverbeforebeenattempted.
IexperiencedthisscaleissueintransformingRational®in


IBM®.IembarkedontryingtouseSOAtoeffectbothacultural
andatechnicalevolutioninRational'sbusinessandRational's
technology.TheJazzdirectionandarchitectureareprime
examplesofashiftinstrategythatstemsnotjustfroman
Internet-basedarchitecturebutfromarethinkingofboththe
businessandthetechnologyunderlyingdevelopmenttoolsand
platforms.Itputsusinapositiontogeneratenewproducts,
evolvefromexistingones,andtakeadvantageofemerging
businessmodels(pricingandpackaging)indeliveringvalueto

ourcustomers.Inlinewiththebook,itrequiredashiftin
culture,ashiftingovernancemodels—organization,technology
assumptions,informationarchitectures,andcollaboration
services.Itrequiredrethinkingthebusinessofsoftware
developmentandmodelingitasaseriesofbusinessprocesses
thatneedtoestablishandreportthroughdynamicmonitoring
ofmetricswithservicesthatcanbedeliveredoninternetsina
globallydistributedmodel.Thejuryisoutyetonwhetherwe
haveturnedvisionintoexecution,butIamconvincednow,
morethanever,thatitwastherightthingtodo.
Inthatspirit,Iencourageyoutoviewthisbookasanupdate
thatimpartsthebenefitofextensiveexperienceinSOA-based
engagementswithourselvesandourcustomersoverthepast
fouryears.Thefirsteditionsetthestageandbroughtoutmany
ofthekeyissuesandthinking.Thisversiondelvesdeeplyinto
keyissuessuchasgovernance,managementofservices,and
especiallythechallengesoflifecycle.Itaddressesmanyofthe
failureissuesIhighlightedinthebeginningoftheForeword.
Theteamthatputittogetherisexperiencedandhasboiled
downbestpracticesanddeliveredapracticalandthoughtful
roadmaptoimplementingsuccessfulSOAtransformations.
Enjoytheride.Afterall,ifitwereeasy,anyonecoulddoit!
DanielSabbah
GM,RationalSoftware
IBMSoftwareGroup


Acknowledgments
WethanktheIBMmanagementteamforallowingusthetime
necessarytowritethisbook.AllbookswrittenatIBMget

supportfrommanagement.Weacknowledgethissupportand
theabilitytoaccessthenecessaryresourcestowritethebook.
ThankyoutoourexecutivesponsorsatIBMSoftwareGroup
andIBMGlobalServices,especiallyRobertLeBlanc,GM,IBM
GlobalConsultingServices,andSOA.
WethankthepeopleatIBMPressandPearsonEducation,the
publishersandstaffwhohavehelpedmarketandcompletethe
productionworkthatgoesintopublishingabooklikethis.At
IBMPress,wethankTaraWoodmanandherteam.AtPearson
Education,wewanttothankGregWiegand,whohelpedus
duringtheproposalphase,andKatherineBull,whoactedinthe
roleofsenioreditortogetourworkinlineandmeetthe
standards.WethankdevelopmenteditorGinnyBessMunroe
andcopyeditorKeithClinefortheireyeoncomprehensiveness
andforhelpingusexpressourselvesbetter,andwethankSue
Outtersonforhertechnicalreviewandforfinding
inconsistencies.Wealsothanktheproductionandmarketing
teamsatPearsonwhohelpedmakethebookreal.
Wealsowanttothankalltheamazinglytalentedpeoplewho
maketheeffortandtakethetimetowritethemyriadarticles
publishedinthepublicdomainonIBMdeveloperWorks
(www.ibm.com/developerworks)andIBMRedbooks®
(www.ibm.com/redbooks).InthecaseofChapter5,
"LeveragingReusableAssets,"thisincludesAlanBrown,Mikko
Kontio,Dr.TracyGardner,LarryYusuf,JohnLord,EoinLane,
CliveGee,JohnMedicke,Feng-WeiChen,MargieMago,Scott
Linehan,KevinWilliams,JohnGanci,AmitAcharya,Jonathan
Adams,PaulaDiazdeEusebio,GurdeepRahi,DianeStrachan,
KanakoUtsumi,NoritoshiWashio,andGrantLarsen.
Finally,wewanttothankthemanyindividualswhocontributed

tochaptersinthebook.CliveGee,fromIBMUK,hasbeen


workingwithcustomersforyearsregardinggovernance.His
keeninsightintowhatworksandmakessensecontributedto
ourworkonSOAgovernanceandorganizingforSOA.Randy
Langel,fromIBMU.S.,taughtusaboutthebusinessaspectsof
SOAgovernanceandthesubsetofSOAgovernance.Bruce
Hawken,fromIBMAustralia,showedhisinsightfulnessand
dedicationtomakingSOAgovernancerealandinspiring.We
thankallthreefortheircontributiontoourworkonSOA
governance.WealsothankDr.AliArsanjani,IBMDistinguished
Engineer,forthenumerousdiscussionswehadaboutSOMA
overthepastcoupleofyearsandforwhatwelearnedfromhim
onthissubject.WealsothankPatrickHaren,IBMExecutive
Architect,whosecriticalreviewsandsuggestionshelpedus"run
thelastmile"whenwritingChapter4,"AMethodologyfor
ServiceModelingandDesign."WethankMarcFiammante,IBM
DistinguishedEngineer,who,nomatterhowbusy,somehow
madetimeforthoseofuswhoneededhisinsightand
leadership.WethankRosalindRadcliffe,STSMfromIBMTivoli®,
forprovidingkeyinsightsintosomeoftheSOAinfrastructure
products,andwethankSankarSingha,IBMSeniorArchitect,
whohelpedbringallthepiecestogetherwhenwewerewriting
Chapter6,"RealizationofServices."Lastbutnotleast,weare
verythankfultoThomasSchaeck,IBMDistinguishedEngineer,
Lotus®Quickr,andWebSphere®PortalWeb2.0Development.
Hegaveusagreatinsighttothecollaborativesolutionsthat
helptotakebroadadvantagefromSOA-basedITinthe
enterprise.

AbouttheAuthors
NorbertBiebersteinworksforIBM'sSOAAdvanced
Technologiesorganizationsupportingworldwidepublicationand
communicationofSOA-relatedtopics.Hegainedfirsthand
experiencesfromcustomerprojectsinvariousindustries
strivingtomigratetoSOA-basedsolutions.Norbertpublished
severalarticlesonSOA-relatedtopics,coordinatedtheIBM
SystemsJournalissue44-4onSOA,andwastheleadauthorof
Service-OrientedArchitectureCompass(IBMPress,2005).In
2007,thebookSOAforProfitwaspublished,forwhichNorbert
actedasoneofthethreeleadauthors.Healsoco-authoredtwo
IBMRedbooks:IntroductiontoGridComputingwithGlobusand
EnablingApplicationsforGridComputingwithGlobus.In1993,
hepublishedhisfirstbook,CASE-Tools.NorbertjoinedIBM
softwaredevelopmentlabsasasoftwareengineeringconsultant
in1989.Intotal,hehasmorethan27yearsofexperiencein
informationtechnologyandcomputersciences.Inhiscareer,he
workedasanapplicationdeveloperatasmallersoftware
vendorandasascientificprogrammeratAachenUniversityof
Technology(RWTH),wherehereceivedhisMaster'sdegreein
MathematicsandGeography.In2006,hegraduatedfroma
corporateMBAprogramatHenleyManagementCollegein
Henley,UnitedKingdom.
RobertG.LairdisanITArchitectwithIBMintheSOA
AdvancedTechnologiesgroup,performingworldwideconsulting
forIBMcustomersintheareaofSOAgovernanceandSOA
architecturesinceMay2006.Heisamemberoftheindustry
TOGAF(TheOpenGroupArchitectureFramework)SOA

Governanceworkinggroup.
Roberthasmorethan20yearsexperienceinthetelecom
industryatMCIandVerizonBusiness.HewastheMCIchief
architect,leadingtheenterprisearchitecturegroupandworking
acrosstheentireorder-to-cashsuiteofapplications.Heledthe
developmentoftheSOA-basedsingle-stackstrategytosimplify
themultiplenetworkandapplicationssilos.Bobhasdriventhe


strategy,planning,andexecutionofMCI'sproductdevelopment
intheareaofcontactcenters,IP/VPN,VoIP,IMS™,and
managedservices.ForOSS,hehasledsuccessful
implementationstoautomatenetworkprovisioning,network
restoration,andnetworkmanagement.
BeforejoiningMCI,RobertworkedasaconsultantforAmerican
ManagementSystems(AMS)andIdeation,Inc.Hehasa
Master'sdegreeandaBachelordegreeinComputerScience
fromPurdueUniversityandhasbeengrantedtwopatentsinthe
areaoftelephony.Hehasspokenatvariousindustryforums,
writtenfortheSOAMagazine,andbeenquotedinCIOInsight,
Telecommunications,InfoWorld,andComputerworld.
Dr.KeithJonesiscurrentlyanexecutiveITarchitectwithIBM
intheSOAAdvancedTechnologiesteamwherehefocuseson
thedefinitionandimplementationofservice-oriented
architectureswithleading-edgecustomers.Hehas30years
experienceintheITindustryasasystemsengineer,software
architect,strategist,andauthorofmanymiddleware
publications.Keith'sprofessionalinterestscenteronbuilding
transactional,message-orientedandservice-oriented
middlewareinfrastructuresinsupportofbusinessprocessesina

widerangeofenterpriseenvironments.Mostrecently,these
haveincludedinfrastructuresatmajorfinancialservices,retail
services,automotivemanufacturing,onlinemedia,andauction
enterprises.KeithhasaPhDinChemistryandliveswithhis
familyinBoulder,Colorado,UnitedStates.
TilakMitraisaCertifiedExecutiveITArchitectwithIBMGlobal
BusinessServices,performingglobalconsultingforIBMinthe
areasofenterprisearchitecture,helpingclientsrealizetheir
adoptionofSOAfromitsvisionthroughitsdesignand
implementation.
Tilakhasmorethan10yearsofindustryexperienceinretail,
banking,mediaandentertainment,health-care,and
transportationindustries,whereinhehasworkedinvarious
leadershipcapacities,rangingfrombusinesstoIT


transformations,leadingintosolutionimplementationand
delivery.TilakworkscloselywiththeIBMSOACenterof
Excellence,inwhichcapacityhecontributestothedevelopment
ofvariousIBMSOAofferingsandauthorswhitepapersand
techniquepapersonIBMSOAassets.Hiscurrentfocusison
buildingassetsandtechniquesthatfosteraradical
simplificationofthedevelopmentofSOA-basedcomposite
applicationsthatareexecutableonvariousvendorplatforms
(forexample,IBMWebSphereandSAPNetWeaver).
TilakhasaMasterofEngineeringdegreeinElectrical
EngineeringfromIndianInstituteofScience(IISc),India,anda
BachelorofSciencedegreeinPhysicsfromPresidencyCollege,
India.HeisacontributingeditoroftheJavaDevelopersJournal
(JDJ)andisafrequentauthorinIBMdeveloperWorksandin

JDJandWebSphereDeveloper'sJournal(bothfromSYS-CON
Publications).HealsospeaksatvariousU.S.universitieson
topicsthatcoverthegamutofSOA.
SOAisthearchitecturalstyleofchoice.However,the
implementationofanSOAhasanavalancheofconsequences,
someofwhicharenotyetdiscovered.Thereisnotjustone
methodologythatleadstoanSOA.Wehavetolearnfromdoing
andbuildonexperiencesandbestpractices.Thisbookprovides
valuableinsightsintotheconsequencesofapplyingSOA.It
offersapproaches,principles,andguidelinesforthefullservice
lifecyclebasedonexperiences.Thebookisamustreadfor
everyenterprisearchitect.
MartinvandenBergLeadEnterpriseArchitect
SogetiNetherlands
Manycurrentpublicationsonservice-orientedarchitecture
(SOA)focusontechnologyandtoolsonly.ExecutingSOA:A
PracticalGuidefortheService-OrientedArchitecttakesa
broaderview.Onewholechaptereachisdedicatedtothe
businessimplicationsofSOA,thegovernanceofSOA,anda
methodologyfortheSOAarchitect.


Someofthekeystatements:
1. SOAprimarilyfocusesonbusinessagilityandnotonIT.
2. SOAisanarchitecturalstyleandisnottobeequatedwith
technologiessuchasWebServices.
3. TheprinciplesofSOAarenotnewandwerenotinventedin
themomenttheacronymcameup.
Weneedmorepublicationsthatareheadedinthisdirection!
Prof.Dr.BernhardHumm

AthoroughandpracticalbookIfoundvaluableforitsin-depth
descriptionsofSOAgovernanceandthecompleteviewof
services,fromthearchitecturalviewthroughtoactual
realization.Thisbookisusefultoanyenterprisearchitect
lookingtoaddressthehardpartsinSOA.Thechaptersonhow
toapproachassetreuse,thehumanaspectsofSOA,andthe
descriptionsofwheretoolingfitsinmakeitabookwellworth
readingandusing.Throughtheextensivereferencestoother
materialsavailable,itcanalsoserveasaguidetofurther
readingonline
ErikvanOmmeren
DirectorofInnovation
SogetiUSALLC/VINT
WashingtonD.C.,USA



Chapter1.IntroducingSOA
"Yetanotherbookonservice-orientedarchitecture(SOA),"you
mightthink.Hundredsoftitlesarealreadyforsaleat
bookstores.Afterfourgoodyearsinuse,theacronymSOAhas
developedsuchastrongmarketvaluethatyoucanbuyalmost
anythingas"SOA-something."Marketersquicklydetectedthe
strongdriveandsorenamedordescribedproductsasSOA
compliant,madewithSOA,builtforSOA,andSOAwhatever.
AndevenwiththevastnumberofbooksthatcoverSOA,a
numberofissueshaveyettobecovered.So,inthisbook,we
discussthe"missingitems."
TheprinciplesofSOAarenotnewandwerenotinvented
concurrentlywiththeacronym,andmanyvendors"feel

justified"claiminganSOAbasisfortheirproducts.Sure,when
youexamineITsolutions,youcanfindSOAprinciplesthatwere
implementeddecadesago.Forexample,somehomegrown
mainframe-basedsolutionsrunningatITshopsoffinancial
servicecompanieshavebeenwiselybuiltwiththepurposeof
futurereuseandchangerequests,inaloosecouplingapproach.
Insomecases,anarchitecturalstructurethatwenowcallan
enterpriseservicebus(ESB)isused;thoseunitsarenotbeing
identifiedassuch,buttheydooperateaccordingtoSOA
requirements.Architectureprincipleswerenotinvented
recently,andyoucanconsiderthemthefoundationofSOA.
Beforewedelveintothedetails,let'stakeacloselookatthe
historyofSOA.WheredidSOAcomefrom?Theanswertothis
questionquicklyshowsthekeyelementsforsuccessfully
executingSOA.However,historyisn'tenough;service-oriented
architectswholeadthetransformationtowardSOAmustalso
addressanumberofnewissues.

1.1.SOAinRetrospect
ThestrongadoptionofSOAprobablystemsfromitslink
betweenITandbusiness.Itpromisestobridgethechasmthat


dividesthetwocamps.Theinvolvedpartiesatanenterprise
wanttobreakdownthewalloverwhichtherequirementshave
beenthrownandbehindwhichanITorganizationtriestofigure
outwhatthebusinesspeoplewant.
WhenITwasnewinthe1950sand1960s,itwaspeopledby
specialistswhospokeasecretlanguageandknewhowto
operatemagicalbusinessmachines.Thosemachines(withtheir

firstapplications)enabledthequickercalculationofinterest/tax
andautomatedcertainbusinessprocesses.Ateamofhighly
paidexpertscouldeasilyunderstandsimplebusiness
requirementsandthenrealizethemassoftwareprogramson
thosemachines.Withthedawnofthepersonalcomputer,the
knowledgeabouthowtoprogram,andnotjusthowtoenter
dataingivenfieldsongreenscreens,createdamorecomputersavvycommunityofuserswhounderstoodhowtoarticulate
moresophisticateddemandsonITshops.Inthe1970s,more
andmoresoftwarevendorsappearedonthemarketoffering
operationautomationformanyindustries.
Themarketenabledenterprisestocompareandevaluate
alternativesoftwaresolutions,oftenagainsttheirownin-house
ITshop.Subsequently,companiesbeganlookingatoutsourcing
IT,asitbecametoocomplicated,andasin-houseteamsfailed
tomasterthebacklogofrequirementsthatrequiredurgent
implementationtobeatthecompetition.Strategicoutsourcing
becameasignificantmarketintheITindustry;often,infact,
thewholeITorganizationwasacquiredbyanITservice
companythatofferedfixedlevelsofserviceandpromisedto
takeawayallIT"worries"fromthecompany.Concentrationon
thecorebusinesssoonbecamethemottooftheday.
InsteadofgainingspeedandflexibilityviathistakeoverofITby
"experts"whoensuredservicelevels,escalationprocesses,
termsandconditions,andsoon,theseoutsourcedservices
ultimatelydriftedfurtherawayfromthedailybusinessofthe
enterprisethanwhenIThadbeenin-house.Theservice
providershadbeenaskedbytheircustomersandforcedby


competitiontoofferthelowestpossiblecostforthesakeof

long-termcontractsthatmeantsecuredincomestreams.As
onewaytoachievethis,providersstandardizedandreused
existingITinfrastructureandsolutions.
Mergersandacquisitionsoccurredinincreasinglylarger
dimensionsinthe1990s,sothatseveralincompatible
enterpriseITsolutionsneededtobeintegrated.Forexample,
theseenlargedcompanieshadtoalignvariousassetsand
demands;operationsbecameaproblem.Standardizedsoftware
packagesrepresentedonesolutiontothisissue;however,
existingenterpriseresourceplanning(ERP)systemshadbeen
heavilycustomized,andinsomecasesERPsolutionproviders
hadtakenovertheircompetitorsandneededtointegratetheir
packagesthemselves.Insomecases,softwarevendors
releasedseveralstreamsofsoftwaresolutionsthattargeted
specificneedsofindividualoperationalunitsincertain
industries,notcaringforintegrationinthefirstplace.Thelack
ofindustrybusinessmodelsasacceptedstandardsforthose
systemsaddeditssharetothedilemma.
Theseso-calledsilosolutionseachfocusedonaspecific
businesssubjectanddataset(andaccordingly,functions
operatingonthisdata).Drivenbytheseparationofbusiness
concernsinthevariousenterpriseunits,thesesilosexemplified
thementalityofoptimizedoperationwithineachunit.The
overallviewgotlostasoptimizingthebusinessmostefficiently
meantconcentratingontheinneroperationsofthebusiness
units.
Asmentionedpreviously,onedriverforintegrationbetweenthe
unitswasmergersandacquisitions,withtheresultingentity
needingtoachievetheenvisionedsavingsfromreusingunits
suchasHR,invoicing,procurement,andsalesadministration.

Thefirstattemptwastocreateintegrationautomationbetween
dedicatedapplications,sothatausercouldenterthesamedata
justonetimetobeappliedinvarioussystems;alternatively,a
batchprocesstransferredinformationfromonesystemto


another.Enterpriseapplicationintegration(EIA)systems
appearedthatofferedsophisticatedsupporttoestablishpointto-pointintegrationofdedicatedapplications.
Toautomatetheintegration,variousmediationlanguagesand
adaptersweredeveloped;often,standardsoftwareproviders
offeredsetsofapplicationprogramminginterfaces(APIs)to
betterintegratetheirsolutionswithothersbuiltfordifferent
purposes.Thesefirstattemptstomaphorizontalinformation
flowsandbusinessprocessesacrosstheenterprisegenerated
anintegrationsoftwareandservicemarket,butstillthe
languagesandtransformationruleshadindividualdefinitions,
andtheyhadbeentailoredtoaspecificuseinagivenbusiness
process.
A.1.1

TheneedforthequickerintegrationofITsystemsinan
enterprise,theincreasinglyspecificbusinessunitrequirements
notyetaddressedbystandardsoftwarepackages,andthe
necessityofcooperationamongInternet-basednewbusinesses
(ofteninteroperatingacrossborders)drovetheneedforIT
industrystandards.Underthenameofwebservices,[1]the
largesoftwarevendorsandtheever-growingcrowdofsmallIT
providersaroundtheworlddefinedandsupportedasetof
standards.
Withthesedefinitions,thefirstinteroperabilitytermswereset.

ItwaswellacceptedthatanyserviceofferedviatheWorldWide
Webcouldbedescribed(howitcouldbefound,howitcouldbe
invoked,whatthestandardformatswere,andsoon).However,
thisdidnotyetmeananITarchitecturedefinition,exceptfor
thefundamentalconceptofaprovider-consumerregistrythat
wasdefinedtostandardizehowwebservicescouldbepublicly
found,propagated,andaccessedbyconsumingunits.
Thehub-and-spokearchitecturepredominantinmostEAI


systemsinspiredanothersteptowardanSOA.Thesesystems
providedacentralcontrollingunitthatensuredtheinvocationof
theproperfunctionofaregisteredapplication,dealingin
additiontoissuessuchasaccessrights,formatconversion,
assureddelivery,andsoon.Abstractingthisideaand
generalizingitforenterprise-wideutilization,theconceptofan
ESBwasborn.TheIBM®referencearchitectureforSOAwas
createdtoillustratethisapproach.InBiebersteinetal.(2006),
youcanfindanin-depthdiscussionaboutESBandhowit
supportsIBM'sSOAreferencearchitecture.
Thoseservices,requiringhumaninteraction,canbeconfigured
sothatthewholesystemoperatesaccordingtoimmediate
customerneeds.TheSOAreferencearchitecturethusbecomes
aclearframeworkforanyenterpriseoperation.Thisframework
canfinallyprovideabasisforend-user-builtfrontendsand
applicationsbuiltaccordingtoweb2.0servicedefinitions,such
asmashups,andthequickdeploymentofuser-oriented
applicationswritteninAJAXorsimilaron-the-glass
developmenttools.
SOAwasseenasthewayoutofthebacklogatITshops,asit

wasarchitecturethatcouldservevariousneedsofbusinessand
ofIT.Inthefirstbookofthisseries,Service-Oriented
Architecture(SOA)Compass,byBiebersteinetal.(2006),we
lookedatvariousdefinitionsofSOAasitwasusedinthose
earlydaysjustaftertheturnofthemillennium.Finally,a
definitionwasprovidedthatturnedouttobestfitthe
understandinganduseofSOAthenandtoday.Thedefinition
readsasfollows:
Aservice-orientedarchitectureisaframeworkfor
integratingbusinessprocessesandsupportingIT
infrastructureassecure,standardizedcomponents—
services—thatcanbereusedandcombinedto
addresschangingbusinesspriorities.
Severalauthorshaveadoptedthisdefinition,andthedefinition