面向服務(wù)架構(gòu)的企業(yè)整合本科畢業(yè)論文

本科畢業(yè)設(shè)計(jì)外文文獻(xiàn)及譯文文獻(xiàn)、資料題目：Service-OrientedArchitecture—AFieldGuidetointegratingXMLandWebServices文獻(xiàn)、資料來(lái)源：著作文獻(xiàn)、資料發(fā)表（出版）日期：2004.10.22院（部）：專業(yè)：班級(jí)：姓名：學(xué)號(hào)：指導(dǎo)教師：翻譯日期：15-外文文獻(xiàn)：Service-orientedarchitecturesforenterpriseintegrationWiththebroadacceptanceandpopularityofXMLandWebservicesasaEAIasastrategicremodelingofbusinessinfrastructureplatform,andstructure,it'shardtosayhowtheserespectivetrendsaffectedeachotherastheyemerged.XMLOnecouldarguethattheEAIinitiativewasrejuvenatedwiththeinfusionofenabledtechnologiesandservice-orientedarchitectures,astheintroductionofthesecomplementaryplatformsresultedinanoverhaulofEAIarchitectures.Asaresult,thequalityandsophisticationofEAIproductshasneverbeenbetter.Ontheotherhand,themomentumbehindtheEAItrendcouldverywellhavebeenaandespeciallytoWebservices.TheincreasmajorcontributortothepopularityofXML,andespeciallytoWebservices.Theincreasingneedtoreducethecostsofintegratingdisparateenvironmentsledtotheubiquitousrequirementforastandarddatasharingplatform,independentoftiestovendorsandprovidedastandarddatatransportwhichempoweredWebexistingtechnologies.XMLserviceswiththeabilitytoeffectivelyabstractproprietaryplatformsinsupportofutilizingthistransportstandardtocommunicateoverpreviouslynon-standardboundaries.andreally,it'snotofmuchconsequenceanymore.XMLPerhapsbothclaimsaretrue,andWebserviceshavebecomekeyenablingtechnologieswithintheworldofEAI,andEAIproductsarebeingbuiltfromthegroundupinsupportoftheXMLandWebservicestechnologyplatforms.1.ServicemodelsforenterpriseintegrationarchitecturesTheprocess-orientednatureofEAIsolutionshasdriventherequirementforservicemodelsthatcanexecuteandmanagevariousaspectsofenterprisebusiness.EAImiddlewareistypicallyinvolvedwiththecreationandhostingoftheseservices;however,itisnotuncommonforcustom-developedintegrationsolutionstoprovidethesetypesofservicesindependently.Eitherway,anunderstandingoftheirrolesandunderlyingtechnologiesisvitalwhendesigninganenterpriseintegrationarchitecture.ThefollowingXWIFservicemodelsaredistinctiveofsenrice-orientedEAIenvironments.Whencoordinatingthemessageexchangepatterninvolvedintheexecutionofabusi-nesstask,itisoftennecessarytoencapsulatetheinteractionbetweenWebservicesintoadedicatedbusinessprocess.Thisprovidesacentralsourceofbusinesslogicthatdeterminestherules,conditions,andexceptionsrelatingtotheworkflowscenariosthatcanoccurwithinasolution.Anumberofbusinessprocessdialectshaveemerged;however,theBPEL4WSspecifi-cationhasreceivedthebroadestindustrysupport.ItiscomplementedbytheWS-CoordinationandWS-Transactionstandardstoprovideaframeworkforbuildingsophisticatedandfullymanagedbusinessworkflows.ABPEL4WSprocessserviceexistsasaWebservicecomposedfromnumer-ouslanguageconstructsthatcanfacilitatemosttraditionalworkflowrequirements.ThedocumeiltrepresentingtheBPEL4WSprocesscontainsinterfaces(orportTypes)WSDLfortheprocessserviceitself,aswellasanyadditionalservicesinvolvedwiththeexecu-tionoftheprocess.UnlikeregularWSDLdocuments,however,theservicedefinitionforaBPEL4WSprocessprovidesnobindinginformation.Itisintentionallyimplementation-neutralsothattheprocesscanremainmobile,reusable,andindependentfromchangestothetechnicaldeploymentenvironment.WS-CoordinationiscloselyassociatedwiththeWS-Transactionspecification,whichdefinestwodistinctcoordinationtypes,bothofwhicharerelevanttoenterpriseintegrationenvironments.Thefirst,atomictransactions,enablesthemanagementofACIDliketransactions.TheservicemodelforatomictransactioncoordinatorsisestablishedinChapter9;itisthemostcommontypeofcoordinationserviceusedinlegacyintegrationarchitectures.Thesecondcoordinationtypeprovidesaniodelforlongrunningtransactions,andisrepresentedaspartofthecoordinationservicemodel(forbusinessactivities)BusinessprocessintegrationisatypicalcharacteristicofEAIsolutions,whichiswhycoordinationservicesforbusinessactivitiesareutilizedexclusivelyforthemanagementoflongrunningbusinessactivities.Thisservicemodelisgenerallyusedinconjunctionwithprocessservicesasameansofhandlingsuccessandfailureconditionsrelatedtotheexecutionoftheoverallprocessactivity.TheWS-Coordinationspecificationprovidesanassemblyofserviceswithpredefinedinterfacesthatsupportthemanagementofacoordinationcontext.Specifically,thiscollectionofservicesprovidesseparateoperationsforthecreationofacontext,theregistrationforacontext,andtheselectionofaprotocol.2.Fundamentalenterpriseintegrationarchitecturecomponents:EAIsolutionscentralizeinter-applicationcommunicationandautomatenewprocesseswiththehelpoftwocorecomponents:thebrokercomponentandtheorchestrntionengine.ThefrundamentalfunctionsenabledbythesecomponentsestablishthebasicEAIarchitectureTodemonstratehowthesecomponentsfunction,basicdataexchangescenariosareprovidedinthissection.Eventhoughtheseexainplesmightseemsimplistic,theyexplainkeyEAIconcepts.Mostenterpriseintegrationproblemsaresollvedthroughtheuseofthesetwocorecomponents.Incidentally,thesetwointegrationscenariosareequallycommoninB2BenvironmentsThebrokercomponentiscapableofperformingawidevarietyofruntimefunctions,suchas:●sopliisticateddatatransformations●mergingdocumentsfroindifferentsources●supplementingreceiveddatafromoneapplicationwithadditionalinformationfromanotherTheprimaryfunctionofanintegrationbrokercomponent,however,istoensurethatdatareceivedfromonesourceisalwaysintheforinatexpectedbythedestinationThefollowingfive-stepprocessdemonstratestheretrievalofdatabyapplicationB,inresponsetoarequestfromapplicationA(HowtherequestissenttoapplicationBisnotrelevanttothisexample.)Figure10.7providesanoverviewoftheprocessstepsStep1:retrieverequesteddatafromthesourcedatabase(Figure10.8)ApplicationAinitiatesarequestfordatathatistransmittedtoapplicationB.ApplicationBprocessesthisrequestandretrievesthedataStep2:validatesourcedatausingsourceschema(Figure10.9)Atsomepoint,theretrieveddataisvalidatedagainstaschemarepresentingthedatamodelofthemessagedocumentthatwillbeusedtotransportthedataoutsideoftheapplicationboundaryThisstepmayoccurnativelywithinthedatabase,oritmaybeexecutedwithinapplicationB'slogic.Thelattercaseismorelikelyifthedataisretrievedfrommultipledatasources,inwhichcaseauniqueschemaforthisspecificrepresentationmayexist.Step3:brokerthedataformat(Figure10.10)Finally,here'swhereourbrokercomponentkicksin.Itwillalreadyhaveschemasfrombothapplications,aswellasadatamapthatwillallowittotransformtheretrieveddataintothedataformatrequiredbyapplicationAAlso,inthisexample,itperformsadynamiclookupfromanexternaldatasourceinordertosupplementthereceiveddatawithadditionalinformation.Thetransformationalsofiltersoutsomeuiulecessarydata(notshown).Step4:validatetargetdatausingtargetschema(Figure10.11),ApplicationAreceivesandvalidatesthedatacontainedwithintheresponsetoitsoriginalrequest.Step5:insertdataintotargetdatabase(Figure10.12)Oncesuccessfullyvalidated,applicationAprocessesandtheninsertsthedatainitsdatabase.3.Webservicesandenterpriseintegrationarchitectures： Integrationarchitecturesdesignedfortheenterprisereachbeyondcross-applicationcommunicationconcerns.Primarilydrivenbybusinessprocessautomation,thesesolutionscanbeextremelybroadinbothfunctionalandarchitecturalscopesNumerousEAIsolutionvendorshaveprovidedsophisticatedenvironmentstoaccommodateever-changingbusinessprocesses.Thetwofundamentalintegrationcomponentsexplainedintheprevioussectionarekeyplayersintheseenvironments,becausetheysupporttheintroductionofnewbusinessprocessesbyunifyingdisparateapplicationstocollaborateonafcinctionallevelMostEAIsolutionsrelyonasynchronousmessaging-basedcommunicationframeworks,andthereforeopenuptheinteractionoptionsbetweentheintegratedparticipants.XML,isanaturalfitforthisframework,andhasestablisheditselfasitsstandarddatarepresentationtechnology.WebserviceshavealsomfiltratedtraditionalEAIenvironments,andtheirsupporthasreachedthepointwherevendorsarebuildingpureservice-orientedenterpriseintegrationproductsThisleadsustoacommonproblemwithtraditionalEAI:interoperabilitybetweenvendorplatforms.Towardtheendofthissectionweexplorehowthisverysignificantissueisbeingaddressedthroughacontemporaryservice-orientedEAImodel.4.Hubandspoke：ThemostpopularofthetraditionalEAImodels,thisarchitecturepromotescentralizedprocessingthrouhahubthatisprovidedbyproprietarymiddleware.AcentrallylocatedserverhoststheintegrationlogicthatcontrolstheorchestrationandbrokeringThroughaseriesofadapters,awidevarietyofdisparateclientapplicationscanparticipateindataexchangeaswellastheorcliestrationworkflowthatresideswithinthehublogic.Onceanapplicationisconnectedtothehub,itmaynotevenncedtobcawareofotherapplicationsitendsupindirectlyinteractingwithFigure10.21showshowintegratedapplicationsessentiallycreatepoint-to-pointconnectionswiththehubitself.Byhidingthesolutionparticipantsfromeachother,alevel.of"logicautonomy"isestablishedFacilitatedbybrokertransformationfeatures,orchestration-enabledroutingcansuportone-to-one,one-to-many,andmany-to-manydataexchangepatterns.Thislevelofflexibilitycanleadtoavarietyofcreativeintegrationscenarios.Thefactthatallofthedataflowsthroughacentrallocationreducesthepotentialofredundantdatare-entryandprocessing,andalsomakesthemonitoringofcommunicationmucheasierInadditiontosimplifyinganumberofadministrationtasks,thisdesigncentralizesthemaintenanceoftheprocesslogic,andevenpromotesreusewithintheapplicationcomponentsthatimplementthecentralizedorchestrationworkflowThismodel,however,doesintroducesomerisks.Asthebusiestandmostpopularpartofanintegrationarchitecture,thehubenvironmentcanbecomeapotentialprocessinghazard.Bottlenecksituationsareaconstantdanger,uiilessscalabilityiscarefullyplannedanddesignedintothehubinfrastructure.Also,thehubcanestablishasinglepointoffailureforaverylargeamountofautomation.Imaginetwelvedifferentapplicationsworkingtogethertosupportautomatedprocessesforfivedivisionsofanorganization.Nowimaginetheonepointthroughwhichalldatamustflowgoingdown.Notaprettypicture.Thoughmeasurescanbetaken,suchasreplicatioandclustering,thecostofputtingtogetherafullyscalablchub-and-spokeenvironmentwithfullfail-oversupportmaybeprohibitive.Ithasbeentheorizedthatoneofthemajorreasonsthismodelhasbeensoheavilypromotedisthatitbenefitsthevendorsmorethanyou.Onceyourenterprisecommitstoafull-scaleEAIsolution,itfillcreateagreatnumberofdependenciesonaproprietarytechnology.Thesolutionwillbeexpensivetopurchase,expensivetobuildupon,andextremelyexpensetorcpldce.Acentralizedhubthatintroducesavendor-specificproducttocontrolallcommunicationbetweenyourintcgratedapplicationswillbecomedeeplyentrenchedinyourorganization.Forbetterorforworse.5.EnterpriseServiceBus(ESB)：Ifyoubuiltapureservice-orientedarchitecturefromscratch,youcoulddesignitinsuchawaythatyouwouldavoidmanyoftheproblemsthathaveplaguedproprietaryEAIsolutions.YouronlyrealchallengewouldbethetimeandexpenserequiredEAIsolutions.Youronlyrealchallengewouldbethetimeandexpenserequiredtobuildanenterprise-gradeintegrationarchitecturedrivenbyanarmyofstandardizedWebservices.Whatif,though,sonleonebuiltaplatformsupportingsuchanarchitectureforyou.Theunderlyingtechnologywouldstillbeproprietary,butwouldnotlockyouin.EverycomponentofthesolutionwouldexistasaWebservice,allowingyoutoexchangeallowingyoutoexchangeorupgradeitasyouplease.Urn...doyoudeliver?ESBisarefreshingdeparturefromtheproprietarystigmaoftenassociatedwithtraditionalEAIproducts.Someyendorshaverecognizedanopportunitytocombinethebestofbothworlds,whileliberatingproductownersfromvendordependencies.TypicalESBarchitecturesestablishanintegrationplatformthatactsasadynamichostingenvironmentforintelligentserviceintermediaries.SerliicecontainerscanhostavarietyofservicecomponentsEventhoughthecontainersmaybeproprietary,theservicestheyhostarenot.Inadditiontosupportinginterchangeableservices,italsoallowsfortheunderlyinghostingenvironmenttobereplacedwhilepreservingthelogicalreadyencapsulatedbytheseservices.Oneofthemostsignificantbenefitsofthisarchitectureisitsabilitytotranscendthemanyobstaclesoftraditionalinter-EAI-integration.IftwoESBsolutionswereimplementedwithdifferentveiidorplatforms,theopeninterfacepolicyofthismodelwouldmakeanydisparityintheservicehostingenvironmentsalmostirrelevant.

中文譯文：面向服務(wù)架構(gòu)的企業(yè)整合XML和Web服務(wù)將EAI作為一種戰(zhàn)略重構(gòu)的業(yè)務(wù)基礎(chǔ)平臺(tái)，得到廣泛的應(yīng)用和普及，由于這項(xiàng)技術(shù)的出現(xiàn)，很難說(shuō)XML和Web服務(wù)今后的發(fā)展趨勢(shì)會(huì)是怎樣?XML將EAI技重新植入面向服務(wù)架構(gòu)，使其互補(bǔ)平臺(tái)全面實(shí)現(xiàn)EAI架構(gòu)，結(jié)果證明，EAI產(chǎn)品的質(zhì)量和復(fù)雜度比以往任何時(shí)候都要好。 至于另一方面：隨著EAI的不斷發(fā)展，EAI很有可能成為一個(gè)特別的Web服務(wù)，EAI在XML和Web服務(wù)越來(lái)越廣泛的應(yīng)用。隨著EAI的不斷發(fā)展，可以使不同的環(huán)境在一個(gè)標(biāo)準(zhǔn)的數(shù)據(jù)共享平臺(tái)運(yùn)行，并提供一個(gè)標(biāo)準(zhǔn)的數(shù)據(jù)傳輸?shù)氖跈?quán)網(wǎng)絡(luò)平臺(tái)，XML的服務(wù)盡可能的去掉自己專用平臺(tái)，以支持利用這一運(yùn)輸標(biāo)準(zhǔn)比以前的溝通非標(biāo)準(zhǔn)界限好的平臺(tái)。現(xiàn)在這個(gè)已經(jīng)沒(méi)有多大的問(wèn)題了。在EAI從底層向上層的產(chǎn)品都支持XML和Web服務(wù)的技術(shù)平臺(tái)，已經(jīng)成為XML和Web服務(wù)技術(shù)的重要平臺(tái)。服務(wù)模式成為企業(yè)集成架構(gòu):這一過(guò)程為導(dǎo)向性質(zhì)的EAI解決方案，推動(dòng)了需求的服務(wù)模式，可以執(zhí)行和管理各個(gè)方面的企業(yè)業(yè)務(wù)。EAI的中間件通常是參與建立和維護(hù)這些服務(wù)，但是提供這類(lèi)獨(dú)立的服務(wù)，并非是定制開(kāi)發(fā)集成解決方案。無(wú)論哪種方式，它們的作用和技術(shù)對(duì)企業(yè)在設(shè)計(jì)集成架構(gòu)都是是非常重要的。以下XWIF服務(wù)模式是以服務(wù)為導(dǎo)向企業(yè)獨(dú)特的應(yīng)用集成環(huán)境。當(dāng)協(xié)調(diào)消息交換模式參與執(zhí)行商業(yè)任務(wù)時(shí)，通常需要封裝他們之間相互作用的網(wǎng)絡(luò)服務(wù)，然后進(jìn)入一個(gè)專門(mén)的業(yè)務(wù)流程。這個(gè)業(yè)務(wù)流程提供了一個(gè)集中的業(yè)務(wù)邏輯來(lái)源規(guī)則，條件和有關(guān)的工作情況，這時(shí)將提供一個(gè)解決方案。近年來(lái)，像這樣業(yè)務(wù)流程的越來(lái)越多，但是BPEL4WS的規(guī)范得到了最廣大的行業(yè)支持。BPEL4WS提供一個(gè)框架補(bǔ)充了WS-協(xié)調(diào)和WS-交易標(biāo)準(zhǔn)，并建立了先進(jìn)的和全面的管理業(yè)務(wù)流程。BPEL4WS進(jìn)程服務(wù)是為Web服務(wù)的數(shù)值組成而存在的，該進(jìn)程符合最傳統(tǒng)的工作流程要求。BPEL4WS的代表進(jìn)程服務(wù)包含文件（或portTypes）接口。WSDL文件既是本身的進(jìn)程服務(wù)也是參與任何額外執(zhí)行化進(jìn)程的服務(wù)。BPEL4WS服務(wù)與平常的WSDL文件相同，但是BPEL4WS服務(wù)定義了沒(méi)有約束力processprovides進(jìn)程。這個(gè)進(jìn)程是中立的并且可以重復(fù)使用，也可以獨(dú)立改變環(huán)境的技術(shù)部署。WS-協(xié)調(diào)是密切的WS-交易規(guī)范，它定義兩個(gè)不同類(lèi)型的協(xié)調(diào)，這兩者都是企業(yè)集成環(huán)境。第一種類(lèi)型，原子交易，使管理的ACID一樣交易，這樣的話就需要建立原子事務(wù)協(xié)調(diào)的服務(wù)模式，這是最常見(jiàn)協(xié)調(diào)服務(wù)中的傳統(tǒng)一體化架構(gòu)。第二種類(lèi)型提供了一個(gè)長(zhǎng)期運(yùn)行的事務(wù)模式，是具有代表性的協(xié)調(diào)服務(wù)模式。一體化業(yè)務(wù)流程是一個(gè)典型的特征的EAI解決方案，這就是為什么協(xié)調(diào)服務(wù)是專門(mén)管理長(zhǎng)時(shí)間運(yùn)行商業(yè)服務(wù)的原因。這種服務(wù)模式通常是使用過(guò)程服務(wù)中的一種結(jié)合手段，也是處理成功或失敗的有關(guān)情況進(jìn)程的總體活動(dòng)。而WS-協(xié)調(diào)提供了一個(gè)規(guī)范服務(wù)支持與管理的預(yù)定接口。2.企業(yè)集成架構(gòu)的基本出城部分：在新技術(shù)的幫助下，EAI建立了溝通和自動(dòng)化應(yīng)用解決方案，這個(gè)方案包括兩個(gè)核心部分：中間組件和精確引擎。為了說(shuō)明這些組成部分的功能，我們對(duì)基本數(shù)據(jù)交換環(huán)境進(jìn)行了規(guī)定。雖然explainkey看似簡(jiǎn)單，但關(guān)鍵的還是EAI的概念解釋。大多數(shù)企業(yè)集成問(wèn)題都是通過(guò)使用這兩個(gè)核心組件解決的，再順便說(shuō)一句，這兩個(gè)兩個(gè)核心組件也同樣應(yīng)用在B2B環(huán)境。該部分能夠進(jìn)行多種運(yùn)行功能，如:sopliisticated數(shù)據(jù)轉(zhuǎn)換.合并不同來(lái)源的froin文件.補(bǔ)充收一個(gè)應(yīng)用程序的更多信息培養(yǎng)箱的主要功能集成中間件組成部分，是確保收到的數(shù)據(jù)從一個(gè)源始終周期里得到培養(yǎng)的預(yù)期目標(biāo)，以下五個(gè)步驟的過(guò)程表明，檢索數(shù)據(jù)乙，從應(yīng)用層響應(yīng)請(qǐng)求（如何將請(qǐng)求發(fā)送到應(yīng)用B的例子）圖10.7概述了這一過(guò)程的步驟:第1步：獲取要求的數(shù)據(jù)從源數(shù)據(jù)庫(kù)（圖10.8）啟動(dòng)請(qǐng)求的數(shù)據(jù)取出，傳送至應(yīng)用B.申請(qǐng)乙進(jìn)程這一請(qǐng)求，并檢索數(shù)據(jù).第二步：假設(shè)驗(yàn)證的源數(shù)據(jù)源架構(gòu)（圖10.9）在某一點(diǎn)上，檢索數(shù)據(jù)驗(yàn)證架構(gòu)代表數(shù)據(jù)模型的信息文件，將被用來(lái)運(yùn)輸應(yīng)用邊界以外的數(shù)據(jù),這一步可能會(huì)出現(xiàn)在本地的數(shù)據(jù)庫(kù)，也可以申請(qǐng)執(zhí)行邏輯B。后一種情況，假設(shè)數(shù)據(jù)來(lái)自多個(gè)數(shù)據(jù)源，在這種情況下為解決這種代表性的問(wèn)題，可能存在一種特殊的架構(gòu)模式。第3步：中間件的數(shù)據(jù)格式（圖10.10），在此我們將中間件組件傳送到