JAVA™WEBSERVICESPERFORMANCE ANALYSISANDBENEFITSOFFASTINFOSET WhitePaperOctober2005 2TableofContents SunMicrosystems,Inc. TableofContents GlossaryofTerms..................................................................................3Overview........................................................................................4SunJava™SystemApplicationServer...................................................................4FastInfosetinJavaWebServicesDeveloperPack.........................................................4PushToTestSOAKitAnalysisofFastInfoset..............................................................5TestEnvironment.................................................................................10WSTestDriver....................................................................................10Methodology....................................................................................10SummaryofResults...............................................................................11GraphicSummaryofResults........................................................................11SushiBoatsModule—EndpointdoesStAXProcessing....................................................11TVDinnerModule—EndpointdoesJAXBProcessing.....................................................13TheBuffetModule—EndpointdoesDOMProcessing(withStringparam)....................................15TheBuffetModulewithBinding—EndpointdoesDOMProcessing(withdoc/literalschemabinding)..............18References......................................................................................20 3GlossaryofTerms GlossaryofTerms ANS.1:AmericanNationalStandardsInstitute(alsoANSI)ASCII:AmericanStandardCodeforInformationInterchangeDOM:DocumentObjectModelEAR:EnterpriseArchiveEJB™:EnterpriseJavaBeans™JAR:Java™ApplicationResourceJAX:JavaAPIforXMLJAXB:JavaArchitectureforXMLBindingJVM:JavaVirtualMachineJ2EE™:JavaEnterpriseEdition(JavaEE)formerlycalledJava2Platform,EnterpriseEditionOAGIS:OpenApplicationsGroupIntegrationSpecificationRPC:RemoteProcedureCallSOA:ServiceOrientedArchitectureSOAP:SimpleObjectessProtocolSTaX:StreamingAPIforXMLTPS:TransactionsPerSecondWSDL:WebServicesDescriptionLanguageXML:eXtensibleMarkupLanguage SunMicrosystems,Inc. 4Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. Overview ServiceOrientedArchitecture(SOA)hasetheindustry’sdefactostandardtobuildandpositeapplicationswithgreaterbusinessagilityandimprovedefficienciesfortradingpartnersandcustomers.Webservices,thepredominantunderlyingtechnologyofSOA,havecontinuedtoevolveinareasofsecurity,interoperability,reliability,andperformance.Thispaperprovidesdetailedanalysisandrealitiesofnewlyavailabletechnologies,suchasFastInfoset(FI),whichprovidedramaticallyimprovedWebservicesperformanceandscalability. ToesshowtheJava™patible,SunJavaSystemApplicationServer8.1leveragesFastInfosetanditsperformanceimpact,thepubliclyavailableWebServicesperformancetestkitfromPushToTest(theSOAKit)wasused.ThesetestswereconductedonsimilarenvironmentsaswereusedinpastWebservicespublishedbenchmarksonproductssuchasBEAWebLogicServer8.1,Oracle®ApplicationServer10g,IBMWebSphereApplicationServerV6.0,JBossApplicationServer4.0,andApacheGeronimo.TheseelectedtoperformparisonswithoutthebenefitofFastInfoset. SunJava™SystemApplicationServer TheJavaSystemApplicationServerprovidesaJavaEEpatibleplatformfordevelopinganddeliveringserver-sideJavaapplicationsandWebservices.Thisapplicationserveristheindustry’sfirst,andmostpopular,productionJavaEE1.4applicationserver.Focusedmainlyondeveloperproductivity,thefull-featured,high-performance,small-footprintcontainerisfreefordevelopment,deployment,andredistribution.Thiseditionisidealforembeddingandbundling,andisalreadyincludedwithNetBeans™,JavaStudioCreator,JavaStudioEnterprise,andtheSolaris™OS. Inaddition,JavaSystemApplicationServeristhecorerun-timeenginefortheJavaEnterpriseSystem,arevolutionary,subscription-basedapproachtoinfrastructuresoftwarethatreducescostplexitythroughoutdatacentersbyprovidingfullyintegrated,end-to-endinfrastructuresoftwaresuites. FastInfosetinJavaWebServicesDeveloperPack InadditiontotheWebservicestechnologiesprovidedoutoftheboxintheJavaSystemApplicationServer8.1,theadd-onJavaWebServicesDeveloperPack(WDSDP)providesdevelopersandcustomerswithquick,incrementalupdatesthatcanbeusedtobuild,test,anddeployXMLapplications,Webservices,andWebapplicationswiththelatestWebservicestechnologiesandstandardimplementations. TheJavaWSDPisalsopletelyfree,integratedtoolkit.Withthenew1.6release,developersarenowableto:
1.DevelopanddeployapplicationsusingthelatestXMLandWebservicestechnologiesslatedforinclusioninSun’s deploymentplatforms
2.EnhanceWebservicesperformancewithoutrevisingWSDLfilesorapplicationcode
3.CreateXMLandWebservices-enabledapplicationsthatexploitenhancedsecurityfeatures
4.ContinuetoenjoyJavainteroperabilityandportabilityacrossdifferentplatformsanddevices
5.Simplifyandlowerthecostoflegacyapplicationintegration,datainterchange,andpublishinginWebenvironments 5Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. TheJavaWSDP1.6releasecontainsFastInfosettechnologythatcanincreaseWebservicesperformancetwotofourtimesbyusingANS.1-basedbinaryencodingthatdecreasestransmissionandprocessingtimesformessages,paredtoXMLandASCIImessageswithzerocodechanges[5].TheJavaWSDPalsoincludesapreviewofnext-generation,XMLWebservicessecurity,apreviewoftheServiceRegistryforSOAapplications,updatestoexistingWebservicestechnologiespreviouslyreleasedintheJavaWSDP,andguidelinesfordevelopingclient-sideWebservices. PushToTestSOAKitAnalysisofFastInfoset ThePushToTestSOAKit[4]isaperformanceworkloadconsistingofasetofWebservicesponentsthatleveragethe“PatternsandStrategiesforBuildingDocument-BasedWebServices”[4]developedatSun.TheworkloadhasthreemainmodulescalledSushiBoats,TheBuffet,andTVDinner,whichinvokeWebservicesimplementedasEJBendpoints.Theserviceimplementationusesthreemainparsingtechnologies:StAX,DOM,andJAXB. DuringthecourseofanalyzingthisworkloadwithFastInfosetandportingittotheJavaSystemApplicationServer,severalissuesanddisparitieswereuncoveredinpastWebservicesSOAKitbenchmarkpublicationsfor:•BEAWebLogicServer(WebLogic)8.1•OracleApplicationServer(Oracle)10g•IBMWebSphereApplicationServer(IBM)V6.0•JBossApplicationServer(JBoss)4.0•ApacheGeronimo Theseincludebutarenotlimitedto:
1.IrregularitiesoftheSOAKitwhenappliedacrossJavaEEapplicationservervendors: •TheTVDinnermodulesinWebLogic,IBM,andJBosscanparseXMLonlywhenpassedasastringintheWSDL.TVDinnermodulehasdisparateWSDLfiles.OracleusesElement;IBM,JBoss,andWeblogicusestrings. •debug=“on”issetforOracleandJBossbuildsinjavactargets.•AllWSDLfilesaredocumentliteralforWeblogic,butOracleissetasRPCencoded.•It’sunclearifclientandserverwereonthesameordifferentmachines.Inlookingatthebuildscriptsandcode,it appearstheywerelocal(URLsappeartobehard-codedashttp://localhost).•SeveralWSDLsusexsd:anyTypetopassdata.UseofanyTypeisnotstandard.anyTypeJAX-RPC4.2.1.TheJAX- RPCspecificationdoesnotdefinethestandardJavamappingforthexsd:anyType.Thepreferredmappingisxsd:any[4].•Methodsthrowagenericjava.lang.Exception,ratherthanapplication-specificfaults.•TheBEAcodeisbuilttorunonWeblogic9.0Beta.ThecurrentversionisWeblogic9.0(GA).Thecodedidnotbuildanddeployoutoftheboxonthisversion,andhadtobedebugged.•ThebenchmarkusesOAGISschemas,andtheversionusedisstatedasbeingas8.1.However,fromtheOAGISWebsite[1],onlyversion9.0and8.0SP3wereavailablefordownload.•TVDinnerDPL.createPPO_XMLusesXMLBeans,irrespectiveofwhichapplicationserverwasbeingusedandtested.•EARscreatedaremissingejb-jar.xmlfiles,andmustbeaddedmanually. 6Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. •Thecodeisnotcleanandhadseveralissues.Someexamplesinclude:•Thesamevalueisreturnedirrespectiveoftheloadtestbeingrun.//Loadsinthecorrespondingstring:switch(pPayload){case1:sOAGIS_P1=poDoc.xmlText();break;case2:sOAGIS_P2=poDoc.xmlText();break;case3:sOAGIS_P3=poDoc.xmlText();break;}•CodecontainsSystem.outsinthecriticalcodepath.Forexample,StaxService.java)System.out.print("getRequestValues\n"); 2)Thecodeseemstoworkdifferentlyfordifferentapplicationservers,soitisnotpossibletomakeafair,parison.Forexample,intheTVDinnerserver(XMLBeansService.java)forBEA,partofthepayloadpassesasaprimitivelong: //Setthevalueofthisinstancetotheresultxmlint_usrarea.setLongValue(crcOrderQty.getValue()); Whereasforotherservers,itcreatesamemory-intensiveDOMobjectforthesamefunctionality: DocumentBuilderFactorydbf=DocumentBuilderFactory.newInstance(); DocumentBuilderdb=dbf.newDocumentBuilder();DocumentdomdocObject=db.getDOMImplementation().createDocument(NS,"CRC32",null); //TheelementCRC32iscreatedandappendeddomdocObject.getDocumentElement().appendChild(domdocObject.createTextNode(Long.toString(crcOrderQty.getValue()))); 3)ThebundlereleasedbyPushToTestappearstobepleteandismissingseveralpieces,including:•FailureoftheDPLpackagepile.Thesourceiseitheroutofsyncorplete.TVDinnerDPLusesclassesthatarenotincludedwiththedownload.Forexample:ProcessPurchaseOrderDocument,ProcessPurchaseOrderDataArea,PurchaseOrderSubLine,andsoon.•TheoriginalschemasusedtodefineallthedocumentsandgeneratetheJAXBandXMLBeansclassesaremissing(forexample,theOAGISschema).Becauseofthis,wecouldnotgeneratetheappropriateJAXBcode. 7Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. NOTE:Thebuildtarget/treeforgeneratingtheXMLBeansandJAXBclassesisnotincludedinanyofthefiles.Thisappearstohavebeendonemanually,thenimportedintoEclipseandaJARfilecreated.Itisunclearwhyasimpleanttargetwasnotwritteninstead. 4)TherearefundamentalissueswithSOAKitbenchmarkingmethodologyinpastWSbenchmarkpublicationsforBEAWebLogicServer8.1,OracleApplicationServer10g,IBMWebSphereApplicationServerV6.0,JBossApplicationServer4.0,andApacheGeronimo.•ThetestswererunfromasingleJVMclientandrequestssenttotheserver.However,thenumberofclientthreadswasfixedandperformancewasmeasuredparingthemagnitudeofCPUutilization.Webelievethattherealtestofanapplicationserver’scapabilitytoperformunderloadcanonlybemeasuredbysaturatingtheCPUuntilnofurtherloadcanbeprocessedbytheserver.Severalscalabilitystudiesthatpletedpreviouslyandmendationsfortuning,includingthoseatBEA[2],havetakenthisapproach.MeasuringorreachingapeakthroughputwithoutfullsaturationoftheCPUisanindicatorofaperformancebottlenecksuchasI/Ocontention,thread-synchronization,orincorrectconfiguration.•ThetestingtoolemployedisTestMakerwhich,uponinspectionanduse,appearstomoreofaunittestingtoolandlessofaloadgenerator.UsingthedocumentationandcodeprovidedbyPushToTest,wecouldnotgettheresultsvalidatedorduplicatedparativeorbetterhardwareforBEAoranyoftheotherapplicationserversinquestion,usingtheirclientdriversandharnessTestMaker.TheTPSwasseverelylimited,possiblyduetothreadingorsocket-handingissuesintheframework,aswellasitsuseofJython(aderivativeoftheinterpretedlanguagePython,whichwasemployedtoscriptallthetestcases).Itisunclearhowtheharnesswasrun,orifspecific,undocumentedtuningswereappliedtomakeitrunduringpreviouspublications.•Theloadfromtheclientsisgeneratedinaconvolutedmanner.Ratherthanhavingwell-definedXMLrequestdocuments,theschemaispiledexternallyintoJavausingJAXB.Then,asampleXMLdocumentisunmarshalled,modifiedinmemory,andmarshalledout.Simplerandmoreefficientapproachescouldhavebeenutilized,suchasreadingtherequestsfromXMLorgeneratingthemintheirentirety.•TheclientJVMislimitedbythenumberworksocketstofive.Bydefault,theJVMusesmonusecaseemployedinbuildingdocument-basedWebservices.moncustomerusecaseinvolvesbindingtheschemasdirectlyintheWSDL(knownastheXMLintheBodyStrategy),orutilizingxsd:anytobuildschema-independent,polymorphicprocessors. WebelievethatwiththeadventofstandardizedandadvancedAPIs,likeJAX-WebServices(WS)2.0andJAXB2.0,theembeddedXMLintheBodyStrategywilleevenmoreprevalent.Table1summarizesparisonofsomepossiblestrategies,aswellastheiradvantagesanddisadvantages. 8Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. Table1.ComparisonofPossibleStrategies StrategyUsingstring Advantages •Simple,sameaswritinga"helloworld"application. Disadvantages •Schemavalidationofferedbytheruntimecannotbeused,anderrorswiththedocumentwillnotbepickedupuntiltheservicehasreadthedocumentinmemoryandattemptedtoprocessit. •Serviceinterfaceisnotdescriptivebecausethedocumenttypeisjustageneralstring. •Schemasmustbenegotiatedoutofband.Bothserviceproviderandconsumerneedaprioriknowledgeofthecontentsofthepayload,becausetheWSDLfiledoesnotdescribetheschemaoftheexpecteddocuments. Usingxsd:any •Themappingofthexsd:anyhasbeenstandardizedtomaptoSOAPElementwithJAX-RPC1.1. •EventhoughanelementisnamedintheWSDL(forexample,BusinessDocumentRequest)andthebusinessdocumentpassedappearsinsidetheseelementsonthewire,theWebservicesclientcanstillworkpleteXMLdocumentsandmaintainschemaintegritywithouthavingtoincludedocumentcontentundertheseelements(thisisnotthecasewiththeanyTypestrategy). •RequiresdeveloperstoworkatthelowerlevelsofXML,becausetheynowhavetoworkwithcreatingandmanipulatingSOAPElementobjects. •ThereisnocohesivenessbetweentheWSDLandthedocuments,becausetheschemasdefiningthedocumentsarenotreferenceddirectly. •Schemasneedtobenegotiatedoutofband.Bothserviceproviderandconsumerneedaprioriknowledgeofthecontentsofthepayload,becausetheWSDLfiledoesnotdescribetheschemaoftheexpecteddocuments. 9Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. StrategyUsingxsd:anyType Usingschema-definedtypes(XMLintheBody) Advantages •Allowstheactionandpayloadtobepassedtogether.Thiscanbeusefulwhencreatingapolymorphicprocessorthateptsmultipledocumenttypeswiththesameactions,forexample,asingleservicethatperformsasearchactiononapurchaseorderandaninvoice,bothofwhichconformtodifferentschemas. Disadvantages •JAX-RPCspecificationdoesnotdefinestandardJavamappingforthexsd:anyType,sonotallimplementationswillbehaveliketheJavaWSDPandmaptoaSOAPElement.Infact,supportforthexsd:anyTypeisoptionalforanimplementation. •BecausetheanyTypeactuallydefinesthedatatypeforanamedelementintheWSDL,thebusinessdocumentbeingpassedintheSOAPbodyislocatedinsidetheelementidentifiedintheWSDL.Forexample,thePurchaseOrderisinsidetheBusinessDocumentRequestelement.Thismeansthatthedocumentbeingpassedmusteither:•HaveitsrootelementidentifiedintheWSDL•Beconstructedappropriatelyorwrappedintheelementonthefly •Interoperability.•ValidateagainstschemaifXML docsareused.•Betterperformancethanencoded formattingstyles.•Serviceinterfaceclearlydescribes thetypesofdocumentsexpected.ThismakestheWSDLfileeasiertounderstandforclients •Cannotusecustombindingsorbindingframeworksdirectly. 10Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. TestEnvironment ThesoftwareleveragedtheJavaSystemApplicationServer8.1UR2withJavaWSDP1.6,whichwasFastInfosetenabledanddisabledtoquantifyperformancegainsofFastInfosetinastandardmanner.WeparableWindows2003ServerhardwarewithdifferentCPUspeedsontheSun™machines.ThemajoremphasiswastomeasuretheperformancegainsofFastInfoset,nottopareittoPushToTestpastbenchmarkpublications[5],mainlybecauseofissuesaroundreproducibility. Thehardwareconfigurationusedwassimilartotheconfigurationusedbytheoriginalpublications,whichwasanHPProLiantDL560R01Serverwith2xXeonMP,3.0-GHz,1-GBDDRSDRAM,andCompaqSmartArray5iPlusdual-channel64MB,plus:•Ultra160SCSIIntegratedRAIDcontrollersupporting0,1,1+0,5RAIDLevelbusspeed400-MHzFSB•OperatingSystem:Windows2003Server WSTestDriver SincetheclientTestMakerdriverprovidedinthePushToTestSOAKitdistributionhadmanyissuesandwasnonfunctional,theclient-sideWSTestDriver[2]wasusedtodrivetheloadontheendpoints.WSTestisanopensource,WebservicesbenchmarkpublishedbySunin2004,andsubsequentlyusedbyothervendorstotestWebservicesperformance. WSTestsimulatesamultithreadedserverprogramthatmakesmultipleWebservicescallsinparallel.WSTestmeasuresthethroughputofasystemhandlingmultipletypesofWebservicerequests.ThisnotionofaWebservicesoperationcorrespondstoarequest/responsecycle.WSTestreportstheThroughput-AveragenumberofWebservicesoperationsexecutedpersecondandtheResponseTime-Averagetimetakentoprocessarequest.Thesemetricsarereportedforalltestedoperations. WSTestreadsthesepropertiesatinitializationintoanin-memorystructurethatisthenessedbyeachthreadtoinitiateanoperationasperthedefinedmix.Anewoperationisstartedassoonasaprioroperationpleted(thereisnothinktime).ThenumberofoperationsexecutedandtheresponsetimesareumulatedduringtheSteadyStateperiod,andreportedattheendoftherun. Methodology
1.MostusecasesintheSOAKitrevolvearoundWebservicesthateptXMLasstringinthepayload,andparseitusingStAX,DOM,orJAXBprotocols.Suchstrategies,thoughsimpletodesign,sufferfromtheissuespreviouslydiscussed.Additionally,thesestrategiesarenotoptimalforhigh-performanceencodingslikeFastInfosetandothers,eventhoughaperformanceimprovementisseenwhenFastInfosetisenabled(seesubsequentsections).Forexample,whenanentireXMLdocumentispassedasastring,high-performanceencodingslikeFastInfosetputethestructureoftheXMLdocument,andcannotoptimizeperformance,whichmeanstheycannotdemonstratetheirtruepotentialandbenefits.Forthispurpose,weaddedanadditionaloperationtotheWSDLfortheJavaSystemApplicationServerthatbindsthepayloadtospecificelementsintheschemausingtheXMLintheBodyStrategywithdocument-literalformatting.
2.TuningsappliedwhichadheredtothosepublishedbyPushToTestwerereappliedtotheJavaSystemApplicationServerwithFastInfosetenabledanddisabled. 11Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. SummaryofResults paringperformanceandbenefits,theJavaSystemApplicationServer8.1UR2withFastInfosetprovidesdramaticallyenhancedWebservicesperformanceforbothsmallandlargedatasetswhentestedonthePushToTestSOAKit,acrossJAXB,DOMandStAXparsingtechnologies,andanincrementalnumberofconcurrentusers.Detailsoftherunscanbefoundinthefollowingsections. FastInfosetusepletelytransparenttoendusers.FastInfosetcanbeenableddynamicallyonlywhenitdetectsFastInfosetsupportinbothclientandserver,otherwisethestandardSOAPisused.TheJavaWSDPandfutureversionswillcontinuetoprovideperformanceoptimizationaswellasgreaterflexibilityandinteroperabilityacrossheterogeneousJavaEEapplicationservervendors. TheseresultsarenotparabletopastPushToTestbenchmarkpublications[5]duetodifferencesinmachineclockspeeds,loadgenerationclients,benchmarkingmethodologies,codeirregularities,andotherSOAKitreproducibilityissuesoutlinedinthispaper. GraphicSummaryofResults Werantwobenchmarksonsimilarhardwareintwosets.ThefirstsetwasrunwithtwoCPUsontheserversideandhyperthreadingturnedonfortheXeonprocessors.ThesecondsetwasrunwithfourCPUsontheserversidewithhyperthreadingturnedofffortheCPUs.Inbothcases,resultswerealmostidentical.ThediagramsshowtheresultsofthedualCPUruns,withvariedConcurrentVirtualUsers(CVUs). SushiBoatsModule—EndpointdoesStAXProcessing 12Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. 13Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. TVDinnerModule—EndpointdoesJAXBProcessing 14Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. 15Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. TheBuffetModule—EndpointdoesDOMProcessing(withStringparam) 16Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. 17Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. TheBuffetModulewithBinding—EndpointdoesDOMProcessing(withdoc/literalschemabinding) 18Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. 19Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset SunMicrosystems,Inc. 20Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset References
1.OAGIS/
2.WSTestWebServicesBenchmark/
3.SPECjAppServer2002PerformanceTuning/pub/a/2004/01/chow_deisher.html
4.PatternsandStrategiesforBuildingDocument-BasedWebServices/developer/technicalArticles/xml/jaxrpcpatterns/index.html
5.UsingFastInfoset/webservices/docs/1.6/jaxrpc/fastinfoset/manual.html#Using-FI
6.PushToTestBenchmark SunMicrosystems,Inc. Java™WebServicesPerformanceAnalysisandBenefitsofFastInfoset ©2005SunMicrosystems,Inc.,4150NetworkCircle,SantaClara,CA95054USA Allrightsreserved. Thisproductordocumentisprotectedbycopyrightanddistributedunderlicensesrestrictingitsuse,copying,distribution,andpilation.NopartofthisproductordocumentmaybereproducedinanyformbyanymeanswithoutpriorwrittenauthorizationofSunanditslicensors,ifany.Third-partysoftware,includingfonttechnology,iscopyrightedandlicensedfromSunsuppliers. PartsoftheproductmaybederivedfromBerkeleyBSDsystems,licensedfromtheUniversityofCalifornia. Sun,SunMicrosystems,theSunlogo,Java,J2EE,Solaris,EJB,NetBeans,SunUltra,andEnterpriseJavaBeansaretrademarks,registeredtrademarks,orservicemarksofSunMicrosystems,Inc.intheU.S.andothercountries. UNIXisaregisteredtrademarkintheUnitedStatesandothercountries,exclusivelylicensedthroughX/OpenCompany,Ltd. AllSPARCtrademarksareusedunderlicenseandaretrademarksorregisteredtrademarksofSPARCInternational,Inc.intheU.S.andothercountries.ProductsbearingSPARCtrademarksarebaseduponanarchitecturedevelopedbySunMicrosystems,Inc. TheOPENLOOKandSun™GraphicalUserInterfacewasdevelopedbySunMicrosystems,Inc.foritsusersandlicensees.SunacknowledgesthepioneeringeffortsofXeroxinresearchinganddevelopingtheconceptofvisualorgraphicaluserinterfacesforputerindustry.Sunholdsanon-exclusivelicensefromXeroxtotheXeroxGraphicalUserInterface,whichlicensealsocoversSun’slicenseeswhoimplementOPENLOOKGUIsandplywithSun’swrittenlicenseagreements. RESTRICTEDRIGHTS:Use,duplication,ordisclosurebytheU.S.GovernmentissubjecttorestrictionsofFAR52.227-14(g)
(2)(6/87)andFAR52.227-19(6/87),orDFAR252.227-7015(b)(6/95)andDFAR227.7202-3(a).DOCUMENTATIONISPROVIDED“ASIS”ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONSANDWARRANTIES,INCLUDINGANYIMPLIEDWARRANTYOFMERCHANTABILITY,FITNESSFORAPARTICULARPURPOSEORNON-INFRINGEMENT,AREDISCLAIMED,EXCEPTTOTHEEXTENTTHATSUCHDISCLAIMERSHELDTOBELEGALLYINVALID. SunMicrosystems,Inc.4150NetworkCircle,SantaClara,CA95054USAPhone1-650-960-1300or1-800-555-9SUNWeb ©2005SunMicrosystems,Inc.Allrightsreserved.Sun,SunMicrosystems,theSunlogo,Java,J2EE,Solaris,EJB,NetBeans,SunUltra,andEnterpriseJavaBeansaretrademarks,registeredtrademarks,orservicemarks ofSunMicrosystems,Inc.intheU.S.andothercountries. 10/05