文獻(xiàn)翻譯----面向服務(wù)架構(gòu)的企業(yè)整合_第1頁
文獻(xiàn)翻譯----面向服務(wù)架構(gòu)的企業(yè)整合_第2頁
文獻(xiàn)翻譯----面向服務(wù)架構(gòu)的企業(yè)整合_第3頁
文獻(xiàn)翻譯----面向服務(wù)架構(gòu)的企業(yè)整合_第4頁
文獻(xiàn)翻譯----面向服務(wù)架構(gòu)的企業(yè)整合_第5頁
已閱讀5頁,還剩10頁未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡介

1、本科畢業(yè)設(shè)計(jì)文獻(xiàn)、資料題目:外文文獻(xiàn)及譯文Service-OrientedArchitecture一AFieldGuidetointegratingXMLandWebServices文獻(xiàn)、資料來源:著作文獻(xiàn)、資料發(fā)表(出版)日期:2004.10.22院(部)專業(yè)班級姓名學(xué)號指導(dǎo)教師翻譯日期- -外文文獻(xiàn):Service-orientedarchitecturesforenterpriseintegrationWiththebroadacceptanceandpopularityofXMLandWebservicesasaEAIasastrategicremodelingofbusinessin

2、frastructureplatform,andstructure,itshardtosayhowtheserespectivetrendsaffectedeachotherastheyemerged.XMLOnecouldarguethattheEAIinitiativewasrejuvenatedwiththeinfusionofenabledtechnologiesandservice-orientedarchitectures,astheintroductionofthesecomplementaryplatformsresultedinanoverhaulofEAIarchitect

3、ures.Asaresult,thequalityandsophisticationofEAIproductshasneverbeenbetter.Ontheotherhand,themomentumbehindtheEAItrendcouldverywellhavebeenaandespeciallytoWebservices.TheincreasmajorcontributortothepopularityofXML,andespeciallytoWebservices.Theincreasingneedtoreducethecostsofintegratingdisparateenvir

4、onmentsledtotheubiquitousrequirementforastandarddatasharingplatform,independentoftiestovendorsandprovidedastandarddatatransportwhichempoweredWebexistingtechnologies.XMLserviceswiththeabilitytoeffectivelyabstractproprietaryplatformsinsupportofutilizingthistransportstandardtocommunicateoverpreviouslyn

5、on-standardboundaries.andreally,itsnotofmuchconsequenceanymore.XMLPerhapsbothclaimsaretrue,andWebserviceshavebecomekeyenablingtechnologieswithintheworldofEAI,andEAIproductsarebeingbuiltfromthegroundupinsupportoftheXMLandWebservicestechnologyplatforms.Servicemodelsforenterpriseintegrationarchitecture

6、sTheprocess-orientednatureofEAIsolutionshasdriventherequirementforservicemodelsthatcanexecuteandmanagevariousaspectsofenterprisebusiness.EAImiddlewareistypicallyinvolvedwiththecreationandhostingoftheseservices;however,itisnotuncommonforcustom-developedintegrationsolutionstoprovidethesetypesofservice

7、sindependently.Eitherway,anunderstandingoftheirrolesandunderlyingtechnologiesisvitalwhendesigninganenterpriseintegrationarchitecture.ThefollowingXWIFservicemodelsaredistinctiveofsenrice-orientedEAIenvironments.Whencoordinatingthemessageexchangepatterninvolvedintheexecutionofabusi-nesstask,itisoftenn

8、ecessarytoencapsulatetheinteractionbetweenWebservicesintoadedicatedbusinessprocess.Thisprovidesacentralsourceofbusinesslogicthatdeterminestherules,conditions,andexceptionsrelatingtotheworkflowscenariosthatcanoccurwithinasolution.Anumberofbusinessprocessdialectshaveemerged;however,theBPEL4WSspecifi-c

9、ationhasreceivedthebroadestindustrysupport.ItiscomplementedbytheWS-CoordinationandWS-Transactionstandardstoprovideaframeworkforbuildingsophisticatedandfullymanagedbusinessworkflows.ABPEL4WSprocessserviceexistsasaWebservicecomposedfromnumer-ouslanguageconstructsthatcanfacilitatemosttraditionalworkflo

10、wrequirements.ThedocumeiltrepresentingtheBPEL4WSprocesscontainsinterfaces(orportTypes)WSDLfortheprocessserviceitself,aswellasanyadditionalservicesinvolvedwiththeexecu-tionoftheprocess.UnlikeregularWSDLdocuments,however,theservicedefinitionforaBPEL4WSprocessprovidesnobindinginformation.Itisintentiona

11、llyimplementation-neutralsothattheprocesscanremainmobile,reusable,andindependentfromchangestothetechnicaldeploymentenvironment.WS-CoordinationiscloselyassociatedwiththeWS-Transactionspecification,whichdefinestwodistinctcoordinationtypes,bothofwhicharerelevanttoenterpriseintegrationenvironments.Thefi

12、rst,atomictransactions,enablesthemanagementofACIDliketransactions.TheservicemodelforatomictransactioncoordinatorsisestablishedinChapter9;itisthemostcommontypeofcoordinationserviceusedinlegacyintegrationarchitectures.Thesecondcoordinationtypeprovidesaniodelforlongrunningtransactions,andisrepresenteda

13、spartofthecoordinationservicemodel(forbusinessactivities)BusinessprocessintegrationisatypicalcharacteristicofEAIsolutions,whichiswhycoordinationservicesforbusinessactivitiesareutilizedexclusivelyforthemanagementoflongrunningbusinessactivities.Thisservicemodelisgenerallyusedinconjunctionwithprocessse

14、rvicesasameansofhandlingsuccessandfailureconditionsrelatedtotheexecutionoftheoverallprocessactivity.TheWS-Coordinationspecificationprovidesanassemblyofserviceswithpredefinedinterfacesthatsupportthemanagementofacoordinationcontext.Specifically,thiscollectionofservicesprovidesseparateoperationsforthec

15、reationofacontext,theregistrationforacontext,andtheselectionofaprotocol.Fundamentalenterpriseintegrationarchitecturecomponents:EAIsolutionscentralizeinter-applicationcommunicationandautomatenewprocesseswiththehelpoftwocorecomponents:thebrokercomponentandtheorchestrntionengine.Thefrundamentalfunction

16、senabledbythesecomponentsestablishthebasicEAIarchitectureTodemonstratehowthesecomponentsfunction,basicdataexchangescenariosareprovidedinthissection.Eventhoughtheseexainplesmightseemsimplistic,theyexplainkeyEAIconcepts.Mostenterpriseintegrationproblemsaresollvedthroughtheuseofthesetwocorecomponents.I

17、ncidentally,thesetwointegrationscenariosareequallycommoninB2BenvironmentsThebrokercomponentiscapableofperformingawidevarietyofruntimefunctions,suchas:sopliisticateddatatransformationsmergingdocumentsfroindifferentsourcessupplementingreceiveddatafromoneapplicationwithadditionalinformationfromanotherT

18、heprimaryfunctionofanintegrationbrokercomponent,however,istoensurethatdatareceivedfromonesourceisalwaysintheforinatexpectedbythedestinationThefollowingfive-stepprocessdemonstratestheretrievalofdatabyapplicationB,inresponsetoarequestfromapplicationA(HowtherequestissenttoapplicationBisnotrelevanttothi

19、sexample.)Figure10.7providesanoverviewoftheprocessstepsbrokerapplicationAapplicationBFigure10.7Thekeycomponentsinvolvedin自simpledataexchangeseenariawithanintegrationbroke匚NOTEAsindicatedbythedifferentshadingappliedtotherespectiveapplicationsymbols,itisassumedthatdatabetweendisparateapplicationsisbei

20、ngexchanged.Step1:retrieverequesteddatafromthesourcedatabase(Figure10.8)ApplicationAapplicBtiDnEinitiatesarequestfordatathatistransmittedtoapplicationB.ApplicationBprocessesthisrequestandretrievesthedatalogicdataEpplic&tionAFigure10.8TherequestfordstaisreceivedbyapplicationBStep2:validatesourcedatau

21、singsourceschema(Figure10.9)Atsomepoint,theretrieveddataisvalidatedagainstaschemarepresentingthedatamodelofthemessagedocumentthatwillbeusedtotransportthedataoutsideoftheapplicationboundaryThisstepmayoccurnativelywithinthedatabase,oritmaybeexecutedwithinapplicationBslogic.Thelattercaseismorelikelyift

22、hedataisretrievedfrommultipledatasources,inwhichcaseauniqueschemaforthisspecificrepresentationmayexist.Step3:brokerthedataformat(Figure10.10)Finally,hereswhereourbrokercomponentkicksin.Itwillalreadyhaveschemasfrombothapplications,aswellasadatamapthatwillallowittotransformtheretrieveddataintothedataf

23、ormatrequiredbyapplicationAAlso,inthisexample,itperformsadynamiclookupfromanexternaldatasourceinordertosupplementthereceiveddatawithadditionalinformation.Thetransformationalsofiltersoutsomeuiulecessarydata(notshown).applicationAapplicationsFigure10.10Thebrokerservicetransforms,filters,andaddstothere

24、ceived2atainordertoproduceanesponseacDEDtabletotherELiestincaddIication.Step4:validatetargetdatausingtargetschema(Figure10.11),ApplicationAreceivesandvalidatesthedatacontainedwithintheresponsetoitsoriginalrequest.brokerdataapplicatiDnAapplicationsFigure10.11Thstransformeddat&issenttoapplicatiDnA,vhe

25、reitisvalidated.Step5:insertdataintotargetdatabase(Figure10.12)Oncesuccessfullyvalidated,applicationAprocessesandtheninsertsthedatainitsdatabase.appliDationAapplicationsFigure10.11Thstr&nsformEdd&taissenttoapplicationA.whereitinvalidated.Webservicesandenterpriseintegrationarchitectures:Integrationar

26、chitecturesdesignedfortheenterprisereachbeyondcross-applicationcommunicationconcerns.Primarilydrivenbybusinessprocessautomation,thesesolutionscanbeextremelybroadinbothfunctionalandarchitecturalscopesNumerousEAIsolutionvendorshaveprovidedsophisticatedenvironmentstoaccommodateever-changingbusinessproc

27、esses.Thetwofundamentalintegrationcomponentsexplainedintheprevioussectionarekeyplayersintheseenvironments,becausetheysupporttheintroductionofnewbusinessprocessesbyunifyingdisparateapplicationstocollaborateonafcinctionallevelMostEAIsolutionsrelyonasynchronousmessaging-basedcommunicationframeworks,and

28、thereforeopenuptheinteractionoptionsbetweentheintegratedparticipants.XML,isanaturalfitforthisframework,andhasestablisheditselfasitsstandarddatarepresentationtechnology.WebserviceshavealsomfiltratedtraditionalEAIenvironments,andtheirsupporthasreachedthepointwherevendorsarebuildingpureservice-oriented

29、enterpriseintegrationproductsThisleadsustoacommonproblemwithtraditionalEAI:interoperabilitybetweenvendorplatforms.Towardtheendofthissectionweexplorehowthisverysignificantissueisbeingaddressedthroughacontemporaryservice-orientedEAImodel.Hubandspoke:ThemostpopularofthetraditionalEAImodels,thisarchitec

30、turepromotescentralizedprocessingthrouhahubthatisprovidedbyproprietarymiddleware.AcentrallylocatedserverhoststheintegrationlogicthatcontrolstheorchestrationandbrokeringThroughaseriesofadapters,awidevarietyofdisparateclientapplicationscanparticipateindataexchangeaswellastheorcliestrationworkflowthatr

31、esideswithinthehublogic.Onceanapplicationisconnectedtothehub,itmaynotevenncedtobcawareofotherapplicationsitendsupindirectlyinteractingwithFigure10.21showshowintegratedapplicationsessentiallycreatepoint-to-pointconnectionswiththehubitself.Byhidingthesolutionparticipantsfromeachother,alevel.oflogicaut

32、onomyisestablishedFacilitatedbybrokertransformationfeatures,orchestration-enabledroutingcansuportone-to-one,one-to-many,andmany-to-manydataexchangepatterns.Thislevelofflexibilitycanleadtoavarietyofcreativeintegrationscenarios.Thefactthatallofthedataflowsthroughacentrallocationreducesthepotentialofre

33、dundantdatare-entryandprocessing,andalsomakesthemonitoringofcommunicationmucheasierInadditiontosimplifyinganumberofadministrationtasks,thisdesigncentralizesthemaintenanceoftheprocesslogic,andevenpromotesreusewithintheapplicationcomponentsthatimplementthecentralizedorchestrationworkflowThismodel,howe

34、ver,doesintroducesomerisks.Asthebusiestandmostpopularpartofanintegrationarchitecture,thehubenvironmentcanbecomeapotentialprocessinghazard.Bottlenecksituationsareaconstantdanger,uiilessscalabilityiscarefullyplannedanddesignedintothehubinfrastructure.Also,thehubcanestablishasinglepointoffailureforaver

35、ylargeamountofautomation.Imaginetwelvedifferentapplicationsworkingtogethertosupportautomatedprocessesforfivedivisionsofanorganization.Nowimaginetheonepointthroughwhichalldatamustflowgoingdown.Notaprettypicture.Thoughmeasurescanbetaken,suchasreplicatioandclustering,thecostofputtingtogetherafullyscala

36、blchub-and-spokeenvironmentwithfullfail-oversupportmaybeprohibitive.Ithasbeentheorizedthatoneofthemajorreasonsthismodelhasbeensoheavilypromotedisthatitbenefitsthevendorsmorethanyou.Onceyourenterprisecommitstoafull-scaleEAIsolution,itfillcreateagreatnumberofdependenciesonaproprietarytechnology.Thesol

37、utionwillbeexpensivetopurchase,expensivetobuildupon,andextremelyexpensetorcpldce.Acentralizedhubthatintroducesavendor-specificproducttocontrolallcommunicationbetweenyourintcgratedapplicationswillbecomedeeplyentrenchedinyourorganization.Forbetterorforworse.止ire7tltlEMuhi5.EnterpriseServiceBusiIfyoubu

38、ilt|apure(ESB):service-orientedarchitecturefromscratch,youcoulddesignitinsuchawaythatyouwoufdGavpidmanyoftheproblemsthathaveplaguedproprietaryEAIsolutions.YouronlyrealchallengewouldbethetimeandexpenserequiredEAIsolutions.Youronlyrealchallengewouldbethetimeandexpenserequiredtobuildanenterprise-gradei

39、ntegrationarchitecturedrivenbyanarmyofstandardizedWebservices.Whatif,though,sonleonebuiltaplatformsupportingsuchanarchitectureforyou.Theunderlyingtechnologywouldstillbeproprietary,butwouldnotlockyouin.EverycomponentofthesolutionwouldexistasaWebservice,allowingyoutoexchangeallowingyoutoexchangeorupgr

40、adeitasyouplease.Urn.doyoudeliver?ESBisarefreshingdeparturefromtheproprietarystigmaoftenassociatedwithtraditionalEAIproducts.Someyendorshaverecognizedanopportunitytocombinethebestofbothworlds,whileliberatingproductownersfromvendordependencies.TypicalESBarchitecturesestablishanintegrationplatformthat

41、actsasadynamichostingenvironmentforintelligentserviceintermediaries.SerliicecontainerscanhostavarietyofservicecomponentsEventhoughthecontainersmaybeproprietary,theservicestheyhostarenot.Inadditiontosupportinginterchangeableservices,italsoallowsfortheunderlyinghostingenvironmenttobereplacedwhileprese

42、rvingthelogicalreadyencapsulatedbytheseservices.Oneofthemostsignificantbenefitsofthisarchitectureisitsabilitytotranscendthemanyobstaclesoftraditionalinter-EAI-integration.IftwoESBsolutionswereimplementedwithdifferentveiidorplatforms,theopeninterfacepolicyofthismodelwouldmakeanydisparityintheserviceh

43、ostingenvironmentsalmostirrelevant.中文譯文:面向服務(wù)架構(gòu)的企業(yè)整合XML和Web服務(wù)將EAI作為一種戰(zhàn)略重構(gòu)的業(yè)務(wù)基礎(chǔ)平臺,得到廣泛的應(yīng)用和普及,由于這項(xiàng)技術(shù)的出現(xiàn),很難說XML和Web服務(wù)今后的發(fā)展趨勢會是怎樣?XML將EAI技重新植入面向服務(wù)架構(gòu),使其互補(bǔ)平臺全面實(shí)現(xiàn)EAI架構(gòu),結(jié)果證明,EAI產(chǎn)品的質(zhì)量和復(fù)雜度比以往任何時(shí)候都要好。至于另一方面:隨著EAI的不斷發(fā)展,EAI很有可能成為一個(gè)特別的Web服務(wù),EAI在XML和Web服務(wù)越來越廣泛的應(yīng)用。隨著EAI的不斷發(fā)展,可以使不同的環(huán)境在一個(gè)標(biāo)準(zhǔn)的數(shù)據(jù)共享平臺運(yùn)行,并提供一個(gè)標(biāo)準(zhǔn)的數(shù)據(jù)傳輸?shù)氖跈?quán)網(wǎng)絡(luò)平

44、臺,XML的服務(wù)盡可能的去掉自己專用平臺,以支持利用這一運(yùn)輸標(biāo)準(zhǔn)比以前的溝通非標(biāo)準(zhǔn)界限好的平臺?,F(xiàn)在這個(gè)已經(jīng)沒有多大的問題了。在EAI從底層向上層的產(chǎn)品都支持XML和Web服務(wù)的技術(shù)平臺,已經(jīng)成為XML和Web服務(wù)技術(shù)的重要平臺。服務(wù)模式成為企業(yè)集成架構(gòu):這一過程為導(dǎo)向性質(zhì)的EAI解決方案,推動了需求的服務(wù)模式,可以執(zhí)行和管理各個(gè)方面的企業(yè)業(yè)務(wù)。EAI的中間件通常是參與建立和維護(hù)這些服務(wù),但是提供這類獨(dú)立的服務(wù),并非是定制開發(fā)集成解決方案。無論哪種方式,它們的作用和技術(shù)對企業(yè)在設(shè)計(jì)集成架構(gòu)都是是非常重要的。以下XWIF服務(wù)模式是以服務(wù)為導(dǎo)向企業(yè)獨(dú)特的應(yīng)用集成環(huán)境。當(dāng)協(xié)調(diào)消息交換模式參與執(zhí)行商業(yè)

45、任務(wù)時(shí),通常需要封裝他們之間相互作用的網(wǎng)絡(luò)服務(wù),然后進(jìn)入一個(gè)專門的業(yè)務(wù)流程。這個(gè)業(yè)務(wù)流程提供了一個(gè)集中的業(yè)務(wù)邏輯來源規(guī)則,條件和有關(guān)的工作情況,這時(shí)將提供一個(gè)解決方案。近年來,像這樣業(yè)務(wù)流程的越來越多,但是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文

46、件相同,但是BPEL4WS服務(wù)定義了沒有約束力processprovides進(jìn)程。這個(gè)進(jìn)程是中立的并且可以重復(fù)使用,也可以獨(dú)立改變環(huán)境的技術(shù)部署。WS-協(xié)調(diào)是密切的WS-交易規(guī)范,它定義兩個(gè)不同類型的協(xié)調(diào),這兩者都是企業(yè)集成環(huán)境。第一種類型,原子交易,使管理的ACID一樣交易,這樣的話就需要建立原子事務(wù)協(xié)調(diào)的服務(wù)模式,這是最常見協(xié)調(diào)服務(wù)中的傳統(tǒng)一體化架構(gòu)。第二種類型提供了一個(gè)長期運(yùn)行的事務(wù)模式,是具有代表性的協(xié)調(diào)服務(wù)模式。一體化業(yè)務(wù)流程是一個(gè)典型的特征的EAI解決方案,這就是為什么協(xié)調(diào)服務(wù)是專門管理長時(shí)間運(yùn)行商業(yè)服務(wù)的原因。這種服務(wù)模式通常是使用過程服務(wù)中的一種結(jié)合手段,也是處理成功或失敗的有

47、關(guān)情況進(jìn)程的總體活動。而WS-協(xié)調(diào)提供了一個(gè)規(guī)范服務(wù)支持與管理的預(yù)定接口。企業(yè)集成架構(gòu)的基本出城部分:在新技術(shù)的幫助下,EAI建立了溝通和自動化應(yīng)用解決方案,這個(gè)方案包括兩個(gè)核心部分:中間組件和精確引擎。為了說明這些組成部分的功能,我們對基本數(shù)據(jù)交換環(huán)境進(jìn)行了規(guī)定。雖然explainkey看似簡單,但關(guān)鍵的還是EAI的概念解釋。大多數(shù)企業(yè)集成問題都是通過使用這兩個(gè)核心組件解決的,再順便說一句,這兩個(gè)兩個(gè)核心組件也同樣應(yīng)用在B2B環(huán)境。該部分能夠進(jìn)行多種運(yùn)行功能,如:sopliisticated數(shù)據(jù)轉(zhuǎn)換.合并不同來源的froin文件.補(bǔ)充收一個(gè)應(yīng)用程序的更多信息培養(yǎng)箱的主要功能集成中間件組成部分

48、,是確保收到的數(shù)據(jù)從一個(gè)源始終周期里得到培養(yǎng)的預(yù)期目標(biāo),以下五個(gè)步驟的過程表明,檢索數(shù)據(jù)乙,從應(yīng)用層響應(yīng)請求(如何將請求發(fā)送到應(yīng)用B的例子)圖10.7概述了這一過程的步驟:brokerapplicationAapplicationBFigure10.7Thekeycomponentsinvolvedin自右implEdl白自ngEscensriowithanintegrationbroker.NOTEAsindicatedbythedifferentshadingappliedtotherespectiveapplicationm-=:-銳ii-m、wZ-:-y:z:- -*第1步:獲取要求的

49、數(shù)據(jù)從源數(shù)據(jù)庫(圖10.8)啟動請求的數(shù)據(jù)取出,傳送至應(yīng)用B.申請乙進(jìn)程這一請求,并檢索數(shù)據(jù).logicdatadalaIapplicationBappliiDstionAFigura10.8TherequestfordataisreceivedbyspplicationB第二步:假設(shè)驗(yàn)證的源數(shù)據(jù)源架構(gòu)(圖10.9)在某一點(diǎn)上,檢索數(shù)據(jù)驗(yàn)證架構(gòu)代表數(shù)據(jù)模型的信息文件,將被用來運(yùn)輸應(yīng)用邊界以外的數(shù)據(jù),這一步可能會出現(xiàn)在本地的數(shù)據(jù)庫,也可以申請執(zhí)行邏輯B。后一種情況,假設(shè)數(shù)據(jù)來自多個(gè)數(shù)據(jù)源,在這種情況下為解決這種代表性的問題,可能存在一種特殊的架構(gòu)模式。spplicationAspplicatio

50、nBFigure10.9ApplicationBretriEvesandvalidatesth巳requEsted第3步:中間件的數(shù)據(jù)格式(圖10.10),在此我們將中間件組件傳送到應(yīng)用模式以及一個(gè)數(shù)據(jù)地圖,可以把所需要的A從數(shù)據(jù)檢索傳到數(shù)據(jù)格式應(yīng)用,此外,在這個(gè)例子中,它執(zhí)行的動態(tài)查詢是從外部數(shù)據(jù)源獲得的數(shù)據(jù),以補(bǔ)充所收到的數(shù)據(jù)與其他信息的不足。applir-HtionAapplicationsFigure1Q.1QThebrokerservicetransforms,filters,andaddstothereceivedcatainordErtoproduce&responseacceatabletothere3LiestincaddIication.第4步:確認(rèn)目標(biāo)數(shù)據(jù)使用其目標(biāo)模式(圖10.11),將

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

最新文檔

評論

0/150

提交評論