ESB主要产品比较图文.docx
- 文档编号:12096672
- 上传时间:2023-04-17
- 格式:DOCX
- 页数:51
- 大小:1.48MB
ESB主要产品比较图文.docx
《ESB主要产品比较图文.docx》由会员分享,可在线阅读,更多相关《ESB主要产品比较图文.docx(51页珍藏版)》请在冰豆网上搜索。
ESB主要产品比较图文
EnterpriseServiceBus(ESBProductEvaluationComparisons
PreparedbyRobertWoolley
October18,2006
UTAHDEPARTMENTOFTECHNOLOGYSERVICESOfficeoftheChiefTechnologyOfficer
1StateOfficeBuilding,6thFloor
SaltLakeCity,Utah84114
October18,2006
Copyright©2006StateofUtah
AllRightsReserve
CONTENTS
ExecutiveSummary(5
Introduction(6
Problem(9
Premise(9
ESBCharacteristics(10
KeyESBBenefits(11
SOA/ESBGovernance(13
Reality(14
AlternativeSolutions(15
EvaluationScopeandArchitecturalPremise(17
ProductComparisonInformation(20
VendorProfiles(22
ArchitecturePremiseAlignment(25
DepartmentofTechnologyServicesESBComparisons(27
FinancialAnalysisandCostRecovery(32
Conclusions(34
Appendix1:
Scenario/UseCaseBasedProductComparisons(35
CriteriaandCapabilities(36
IntegrationScenarioEvaluation(37
Design,Development,andDeploymentEvaluation(40
ManagementandMonitoringEvaluation(41
ArchitectureEvaluation(43
ProductViability(46
CompanyViability(48
Definitions(50
References(56
EnterpriseServiceBus:
ProductEvaluationComparisons
ENTERPRISESERVICEBUS:
PRODUCTEVALUATIONCOMPARISONS
EXECUTIVESUMMARY
PreparedbyRobertWoolley
October18,2006
企业服务总线(ESB是一种有效的基础组件
服务导向架构(SOA。
ESB提供了一个互操作性和安全应用程序之间的信息传输服务,使用了Web服务和品种相关技术。
结果是一个松散的耦合,业务互通集
可开发的一次,很容易在国有企业内共享服务。
传统的开发方法,把重点放在了应用创造
筒仓内各机构的资产,并努力创造大量裁员类似
在服务领域,如安全和数据访问。
国家发展趋势
为摆脱对建立和服务部署筒仓导向
应用资产。
超过90%的受访公司在这一运动项目
方向和其他一些国家和市政府的积极的ESB
项目进行中。
从财务和管理的角度看,国家需要设法减少
在应用开发和集成的复杂性,通过更有效
资源消耗。
机构要求它更积极的回应
改变以较低的成本业务需求,更及时地。
正因为如此,经济局执行是一个重要商业价值的国家。
ESB的应用基础结构可以从厂商的广泛,包括
商业和开源替代品。
ESB的服务可以部署
在现有的机构完成的应用框架和基础设施和
为所有有关机构的中央服务。
但是,也有具体要求
治理和机构间合作所需要的ESB和作出相关
服务可用的和有效的。
对供应商的产品比较表明,有
对ESB和SOA基础架构能够满足需要的多个备选方案
国家与国家的移动*S本期开发环境走向更现代化
研究方法,在各机构的重大利益。
这项研究建议的概念,至少有三个评价形式证明
供应商的产品,包括开源和商业替代品,使用情况
为基础的方法。
选择供应商可基于比较信息
本报告内提出。
5
INTRODUCTION
AnEnterpriseServiceBus(ESBischaracterizedbymanyanalystsasthefoundationofasuccessfulServiceOrientedArchitecture(SOA.DefinedasmiddlewarethatprovidessecureinteroperabilityandmessagetransportservicesbetweenapplicationswithinaSOA,anESBusesXML,Webservicesinterfaces,messagingadopters,andrules-basedroutingtocreatealooselycoupled,interoperablesetofbusinessservicesthatcanbeeasilysharedwithinandbetweenenterprises.1,2SuchaserviceorientedarchitectureimplementationispresentedinFigure1,illustratingwheretheStateistoday,withmanyapplicationassetsilosmigratingtoserviceorientedapplicationassets.
Figure1.SOAVision:
EvolvingtoaServicesOrientation
ThearchitectureandsomeofthepossibleservicecomponentsofanESB,fromalogicalperspective,areillustratedinFigure2.
1EnterpriseServiceBusandSOAMiddleware,Boston:
AberdeenGroup,June2006,p.1.
2BEAOverview,PowerPointPresentationpreparedbyTonyGalindo,October10,2006.
Figure2.BasicESBArchitecture:
LooseCouplingtoDataandSharedServices
InthisservicemodelanESBcanbedeployedtosupportbothautonomousandfederatedhubandspokeintegrationrequirements.FortheStateofUtahthisrepresentsanimportantlevelofarchitecturalanddeploymentadvantage.
AberdeensplitESBandSOAusersintothreecategories:
3
•SOALite:
Thiscategoryfocusesprimarilyonusersthatworkwith.NETandJavawithopensourceSOAsoftwareusingEclipseintegrateddevelopment
environments,UDDIregistry,SOAP,Ajax,andWS-*standards.
•EnterpriseSOA:
ThiscategoryfocusesonlargeenterprisesthathaveusedSOAformorethanayear,withhighstandardsforuptimeandavailability,and
complexintegrationandlegacycomputingenvironments.
•SOAERP:
ThiscategoryfocusesonusersofSAPandOracleapplicationsthatusethoseplatforms’ESBcapabilitiesastheirprimaryESBenvironment.
Fromacomplexityperspective,theStateofUtahisclearlyanEnterpriseSOAenvironment,but,fromanimplementationandadoptionperspective,fromwithintheagencies,theStateismostaccuratelycategorizedasSOALite.CurrentdevelopmentanduseofSOAfunctionalityismuchmorepronouncedattheedgeatcustomersitesthanasanykindoflarge,central,singleESBconsumedbyeveryone.
3EnterpriseServiceBusandSOAMiddleware,Boston:
AberdeenGroup,June2006,p.18-19
AberdeenalsoprovidesthefollowinggeneralresearchfindingsregardingtheESB:
Issues:
4
•“Existingapplicationintegrationtechnologyistoocomplex,resource-consuming,andslow-to-implementtokeepupwithbusinessprocesschanges.”
•“SOAtechnologyfrombothapplicationISVsanddevelopment/middlewarecompaniesisthepreferredtechnologybaseforsolvingtheapplicationintegrationproblem.”
•“ESBisnotthefirstofmanysuccessiveSOAproductstobedeployed.ItisoftendeployedwithasuiteofSOAmiddlewareproducts.”
KeyBusinessValueFindings:
5
•“Morethan90%ofrespondentsarerapidlyscalingtheSOAadoptioncurvein2006.”
•“ESBtechnologyiscomplementing,notreplacing,EAItechnology.”
•“EnterpriseESBissuesrelatedtointegrationwithregistry/repositoryandscalingtohighvolumesarethegreatestchallengesESBpractitionersface.”
ImplicationsandAnalysis:
6
•“ThemarketisbifurcatingintothosewhoareusingopenstandardsbutnotSOAmiddlewareproducts,andthosemostlylargecompanieswhoareseekingheavy-dutySOAmiddlewareformission-criticalapplications.”
•“SOAmiddlewareisnotareplacementforEAIorothertechnologies,butratherasupplement.”
•“Easeofintegrationflexibilitywithcurrentandplannedapplicationsisthemostfrequently-mentionedbuyingcriteria.”
Recommendations:
7
•“DeliberatelychoosetheSOApathyourorganizationshouldtake:
SOALite,SOAERPorEnterpriseSOA.”
•“ESBtechnologyisoftenpackagedinanESBsuite,incorporatingusefulfeaturesforprocessmanagementandorchestration,SOAgovernance,security,and
messageadaptationacrosslegacyapplications.”
•“SOALiteisnotalong-term,best-practicesapproachtomaximizingbusinessvalue.”
•“Third-partySOAservicesareameanstoboostthelearningcurve.”
4Ibid,p.1
5Ibid,p.5
6Ibid,p.11
Ibid,p.18
EnterpriseServiceBus:
ProductEvaluationComparisons
PROBLEM
TheStateofUtahrepresentsaconfederationof“smallcompanies”carryingouttheirrespectiveITmissions.Sharedserviceshavebeensuccessfulasadeliverymodelforutilitybasedservicessuchasnetworkaccess,telephony,andsomeaspectsofapplicationhosting.
DiverseapplicationdevelopmentovertimehasfosteredacomplexandverycostlyenvironmentforapplicationdevelopmentinStategovernment.Thisenvironmentischaracterizedby:
•highredundanciesthroughisolated“stovepipe”solutions;
•missedbusinessopportunitiesthroughlackingorinconsistentinformation,littleexchange,andsometimesdataownershipandsharingissues;and,•highcostsofmaintenancemodificationandextensionthroughunmanaged“spaghetti”interfaces.
AberdeenidentifiedthestumblingblockslistedinFigure3asprimaryissuesintheirsurveythatcauseorganizationstolooktowardSAOandESBimplementation.
Figure3.ApplicationIntegrationStumblingBlocks8
TheseissuesappeartorepresentsimilarconcernswithintheStateofUtah.
PREMISE
ThepremiseofaServiceOrientedArchitecture(SOAisthatmodularservicescanbeassembledlikeLego®piecesintonewapplicationsthatleverageexistingapplicationandinfrastructureinvestments.Theprinciplechallengeisthatchangestobusinessprocessesandbusinessrules,sometimescalledtheprocessarchitecture,influenceapplicationsandthetechnicalarchitectureinwhichtheyreside.
AnESBisfundamentallyamessaginginfrastructurethatprovidesanabstractionlayerontopofenterprisemessagingsystemstoexploitthevalueofmessagingwithout
8Ibid,p.2
writingcode.TheESBprovidesanarchitecturethatfacilitatesthetaskofintegrationofenterpriseapplicationsandservicesbuiltonJ2EE,.NET,C/C++,andotherlegacyenvironmentswithinthereachofITstaff,usinganevent-drivenservice-orientedarchitecture.
TheESBisasoftwarearchitectureconstruct,implementedbytechnologiesfoundinacategoryofmiddlewareinfrastructureproductsusuallybasedonWebservicesstandards,whichprovidesfoundationalservicesformorecomplexservice-orientedarchitecturesviaanevent-drivenandXML-basedmessagingengine(thebus.
TheESBfacilitatestheabilityofintegrationarchitectsanddeveloperstoexploitthevalueofmessagingwithoutwritingcode.ThefoundationofanESBisbuiltonbasefunctionsbrokenupintotheirconstituentparts,withdistributeddeploymentwhereneeded,asopposedtothemoretraditionalEAIhubandspokepattern.
ESBCHARACTERISTICS
ESBcharacteristicsinclude:
9,10
•ESBisbaseduponopenstandardsforboththeESBsolutioncomponentsandthemechanismsforintegratedapplicationstoparticipateonthebus.
•Messagebased,ESBusesstandardmessagenotation,protocols,andtransports.
•ESBcanbedistributedacrossanetworkforpurposesofqualityofserviceandotherconsiderations.
•Routing,mediation,andinvocationarethebasicfunctionsofanESB.
•ESBfacilitatesinteractionofresourcesandprovidestransactionalsupport.
•AnESBmustbereliableandguaranteemessagedelivery.
•ESBrequirestheclearseparationofmessageheadersandmessagebody.
•AnESBisusuallyoperatingsystemandlanguageindependent;itshouldworkbetweenJavaand.Netapplications,C++,andotherlegacyenvironments.
•ESBoftenusesXMLandWebservicestotransportmessages.
•ESBincludesadapterstandards(suchasJ2C/JCAforincorporatingexistingapplicationsintothebus.
•ESBincludessupportforasynchronousprocessing.
•ESBinclud
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ESB 主要产品 比较 图文