Three

5/9/2017 3DaysTutorialinOSB|SOALair
SOALair
SOAExplained
3DaysTutorialinOSB
November23,2011November25,2011 AnubhawSinha SOA aqualogicservicebus,bpel,insoa,oracleservicebus,osb,serviceoriented

architecture,servicesoa,soait,soatools,trainingsoa,whatissoa
1.TableofContents
1.SERVICEORIENTEDARCHITECTURE.3
2.INTEGRATIONARCHITECTURE.5
3.HUBANDSPOKEINTEGRATIONARCHITECTURE.5
4.DISTRIBUTEDINTEGRATIONARCHITECTURE.7
5.SERVICEORIENTEDARCHITECTURE(SOA)8
6.EXTENSIBLEMARKUPLANGUAGE.9
7.WEBSERVICEDESCRIPTIONLANGUAGE.10
8.ORACLESERVICEBUS.14
8.1.Bus,whatBus?.14
8.2.ResourcesinOracleServiceBus.17
8.3.ProxyServicesandBusinessServices.18
8.4.MessageFlowsandPipelines.19
8.5.PipelinePairs.19
8.6.MessageFlowComponents.20
8.7.BuildingaMessageFlow..22
8.8.MessageExecution.22
8.9.BranchinginMessageFlows.23
8.9.1.OperationalBranching.23
8.9.2.ConditionalBranching.23
8.10.ConguringActionsinStagesandRouteNodes.24
8.10.1.CommunicationActions.24
8.10.2.FlowControlActions.25
8.10.3.MessageProcessingActions.26
8.10.4.ReportingActions.26
8.11.ConguringTransportHeadersinMessageFlows.27
8.11.1.ConguringGlobalPassThroughandHeaderSpecicCopyOptionsforTransportHeaders27
8.11.1.1.UnderstandingHowtheRunTimeUsestheTransportHeadersSe ings.28
8.12.PerformingTransformationsinMessageFlows.30
8.13.TransformationsandPublishActions.31
8.14.TransformationsandRouteNodes.31
https://soalair.wordpress.com/2011/11/23/3daystutorialinosb/ 1/45
8.14.TransformationsandRouteNodes.31
8.15.ConstructingServiceCalloutMessages.31
8.16.SOAPDocumentStyleServices.32
8.17.SOAPRPCStyleServices.33
8.18.XMLServices.35
8.19.MessagingServices.35
8.20.HandlingErrorsastheResultofaServiceCallout.36
8.21.TransportErrors.36
8.22.SOAPFaults.37
8.23.UnexpectedResponses.38
8.24.HandlingErrorsinMessageFlows.39
8.25.GeneratingtheErrorMessage,Reporting,andReplying.40
8.26.ExampleofActionCongurationinErrorHandlers.40
8.27.UsingDynamicRouting.42
8.28.SampleXMLFile.43
8.29.CreatinganXQueryResourceFromtheSampleXML..44
8.30.CreatingandConguringtheProxyServicetoImplementDynamicRouting.44
8.31.AccessingDatabasesUsingXQuery.46
8.32.UnderstandingMessageContext.47
8.33.MessageContextComponents.47
8.34.GuidelinesforViewingandAlteringMessageContext.49
8.35.UsingtheInlineXQueryExpressionEditor.50
8.36.InlineXQueries.51
8.37.UsesoftheInlineXQueryExpressionEditor.51
8.38.UsingVariableStructures.52
8.39.CreatingVariableStructureMappings.53
8.39.1.SampleWSDL..53
8.40.CreatingtheResourcesYouNeedfortheExamples.54
8.41.SavetheWSDLasaResource.55
8.42.CreateaProxyServiceThatUsestheSampleWSDL..55
8.43.BuildaMessageFlowfortheSampleProxyService.56
8.44.CreateaBusinessServiceThatUsestheSampleWSDL..56
8.45.Example1:SelectingaPredenedVariableStructure.57
8.46.Example2:CreatingaVariableStructureThatMapsaVariabletoaType.57
8.47.Example3:CreatingaVariableStructurethatMapsaVariabletoanElement.59
8.48.Example4:CreatingaVariableStructureThatMapsaVariabletoaChildElement.60
8.49.Example5:CreatingaVariableStructurethatMapsaVariabletoaBusinessService.61
8.50.Example6:CreatingaVariableStructureThatMapsaChildElementtoAnotherChildElement62
8.51.QualityofService.64
8.52.DeliveryGuarantees.64
8.53.OverridingtheDefaultElementA ribute.65
8.54.DeliveryGuaranteeRules.66
8.54.DeliveryGuaranteeRules.66
8.55.ThreadingModel67
8.56.Spli ingProxyServices.68
8.57.OutboundMessageRetries.68
8.58.ContentTypes,JMSType,andEncoding.69
8.59.Thro lingPa ern.69
8.60.WSICompliance.69
8.61.WSIComplianceChecks.71
1.SERVICEORIENTEDARCHITECTURE
WhatisSOA?
ServiceOrientedArchitecture.ThiscouldbethebasicdenitionofSOA.
ButwhyisthenameSOA?
SOAisanarchitecturalapproachforbuildingbusinessprocesswithintegrationoflooselycoupledapplications/software(ServiceOrientation).
Mostofyoumightbethinkingwhatthehelldoesthatmean?
SOAoriginatedwiththeconceptofServiceorientation.Serviceorientationislisteningandunderstandingthecustomer(customercanbeworkingon
dierentplatformsbuttheywanttoaccessapplicationbuildonadierentenvironment).
ThatseemstobeeasywithwordsbutIstilldidnotgetwhatdoesSOAmeans.
LetusstartwithbasicunderstandingofevolutionofSOA.
Considerasocalledproblemdenitionwithwhichwewilltryto:
Analyzeandunderstandproblemsfacedwithorthodoximplementationofthesoftware.
HowdidevolutionofSOAhappened
HowwouldSOAimplementationhelpbusinessgainrevenue?
AssumethatyouareabusinessmanwhicheveryoneintheITindustrythinkstobeoneday,planning/dreamingeverydaytostartasidebusiness.Thisisone
typicalexamplewhichisusedeverywhere,aswecanndalotofhelpwiththistypicalexample.Wehavetriedtomakeitabitsimpleforbeginnersto
understandwithhelponline.
SoIbeingasmallmiddleclassITguyIhaveabrilliantideatostartasmallmortgagebusinesswhereIlendmoneyatlowrateofinterest.Istartwithan
onlineservicewhereusercanloginandapplyforaloan.Withanalysiswedenedaproblemdenitionfortheservice.
Problemdenition:
1)Iftherateofinterestfortheloanapplicationislessthan5%,thentheapplicationfortheloanhastogothroughaspecialapprovalfromthe
management.Wherethemanagementwouldanalyzetherequirementoftheapplicanthisneedsandapprove.
2)Allotherapplicationcanbedirectlysanctionedbytheservice,conditionedonhavingthedetailsoftheapplicant.
ThinkinglikeabusinessmanIstartwiththinkingonhowtosavemoney,sowhatIplantoimplementingthesoftwareallbyyourselfasIhavethe
backgroundofsoftwareafterallmyparentshavespendsomuchofmoneyitshouldbeusedsomewhere.
WithallmyknowledgeandITbackgroundIplantostartwiththeimplementation.
Basicandthemostimportthingforsoftwareisitsarchitecture.SobelowishowIplantoimplementmysoftware:
Firstpageofthescreen(assumingwillimplementloginlateron)whichacceptstheuserinformationanddetailsofloantobesanctioned.
Oncetheuserentersthedetails,savetheuserdetailsinauserdetailstableandroutetherequesttocallappropriatemethods,say
requestWithRateBelowFive()andrequestWithRateAboveFive().
Callthesemethodsbasedontherequesttypei.edetailsandbackgroundinformationandcapabilitytopaytheEMI.
Callthesemethodsbasedontherequesttypei.edetailsandbackgroundinformationandcapabilitytopaytheEMI.
After6longmonthsofworkandrigoroustestingofmysoftware,Iplantoputmysoftwarelive.
Withallthedomainregistrationdonemysoftwareislive.
Nowmyprojectisliveandisgivingmealotofprot.WiththeincreasedprotIwanttohavemorefunctionalitytobeaddedinmysoftware.
Extensiontoproblemdenition:
WhereIcanretrievethedetailsoftheuserwhoareconsistentwiththeirEMIsandareloyalcustomertothecompany.Atthesametimewithmillionsof
dollarsinasmyliquidcashIhaveacquiredacompanywhichgivesspecialoerstotheuserwithautoloanswithlowrateofinterest.
Problems:
WiththecurrentimplementationofmyprojectIwillhavetomodifytheentireimplementationtoincludethenewoerandmergethenewcompanies
softwareintomysoftware.
Thiswillresultindowntimefor2dayswhichisdirectlyproportionaltolossofsignicantamountofrevenueandcustomers.
Thisimplementation/architectureofprojectiscalledaspointtopointintegration.
Thisisoneoftheoldestandoriginalintegrationpa erns.
Itderivesitsnamefromthedirect,tightlyboundconnectionsthataremadebetweenapplicationsandisthesimplestoftheintegrationarchitectures.
Thereareadvantageswithpointtopointintegration:
PointtoPointsolutionsareoftenfastandecient.
TheeciencythatderivesfromapplicationsbeingtightlyboundisonereasonwhyatleastafewPointtoPointsolutionswillcontinuetobeutilizedfor
theforeseeablefuture.
Whatarethedrawbackswiththecurrentimplementation/architectureoftheproduct?
Asthenumberofapplicationsincreasessodoestheoverallcomplexityoftheenvironment.
Highmaintenancecostsandalackofexibility,whenitbecomesnecessarytomakechanges.
Conclusion:
ThebasicproblemistheArchitectureoftheproduct,tobespecicIntegrationarchitecture.
2.INTEGRATIONARCHITECTURE
SowhatisIntegrationarchitectureandhowisitsignicantforafastgrowingbusiness.
Consideranexampleofawelldeignedbuildingwhereallelectricsandplumbingkeepworkingnoma erhowmanyappliancesareswitchedonor
connected.
Thisbuildingiscapableenoughforextensionwithouttearinguptheblueprintandstartagainwithnewelectricalconnection.
Thisisanexampleofgoodarchitecture.
Thesameappliestosoftwaresystems.Softwarearchitectureisthebackboneofanycomplexcomputersystem.Thearchitectureencompassesallofthe
softwareelements,therelationshipsbetweentheelementsandtheuserinterfacestothoseelements.Theperformanceandreliabilityofasoftwaresystemare
highlydependentuponthesoftwarearchitecture.Welldesignedsoftwarearchitecturecanbeextendedwithrelativeeasetoaccommodatenewapplications
withoutrequiringextensiveinfrastructuredevelopment.
Nowquestioncomesdowntohowcanweeliminatethisdowntimeandinfuturewithnewacquisitionsintegration.
TherearemanyothertypesofINTEGRATIONARCHITECTURE:
3.HUBANDSPOKEINTEGRATIONARCHITECTURE
Theearliestformalintegrationtechnologiesworkedontheprinciplethatallinformationcomingfromtheapplicationshadtobeprocessedwithinasingle
machineorservercalledahub.Actingasacentralpointofcontrol,thehubdealtwithallmessageprocessingincludingrouting,spli ingandcombiningof
messages,mapping,andsoon.
HubandSpokeimplementationsdecouplethesendingandreceivingapplications.UnlikePointtoPoint,theapplicationsoneithersideofthehubcanbe 4/45
https://soalair.wordpress.com/2011/11/23/3daystutorialinosb/
HubandSpokeimplementationsdecouplethesendingandreceivingapplications.UnlikePointtoPoint,theapplicationsoneithersideofthehubcanbe
modiedindependentlyofeachother.Sinceapplicationsnolongerneedtoperformdatamapping,centralizeddenitionandcontrolofbusinessprocesses
couldbeeasilyachievedforthersttime.
HubandSpokeArchitecture
CentralizedIntegrationProcessingHub
WhataretheadvantagesofHubandSpokearchitecture?
WithHubandSpoke,theintegrationenvironmentbecomeslesscomplex.WhereasPointtoPointbecomesimpossiblycomplicatedasthenumberof
connectionsincrease,HubandSpokeremains,inprinciple,simplesincealltheconnectionsaretoandfromthehub.HubandSpokeisthepreferred
architectureforachievinganeasilycontrolledandmanagedenvironmentinamediumsizedintegrationproject.
WhatarethedisadvantagesofHubandSpokearchitecture?
WithHubandSpoke,theinitialsetupoftwowaycommunicationscanbechallenging.Thehubhastocoordinatemessagesowingbetweenapplications,
andatthesametimeapplicationsonbothsidesofthehubneedtoworkwellinadecoupledfashion.Boththesourceandtargetapplicationsneedsome
knowledgeofeachotherinordertoprocessmessages.Thissometimesmakesitdiculttoaddorremovesendersandreceivers.
Sincethehubmustcontrolalloftheintegratedprocesses,itisaviableoptiononlywhenbothsenderandreceiveragreeonwhichhubtouse.Thiswillnotbe
aproblemforcompaniesthatareintegratinginternally,butmaybecomeaseriousissueforBusinesstoBusiness(B2B)andevencrossdepartmental
integrationprojects.
Unfortunately,withsomuchprocessingtakingplaceinthecentralhub,HubandSpokeexactshighoverheads.Processeswithinthehuboftenrequire
signicantprocessingpowerandlotsofdiskspace.Asthenumberandcomplexityofprocessesincrease,performancecansuerandhubsoftenbecome
diculttomanage,maintain,andextend.
PureHubandSpokeimplementationsdonotscalewell.OnesolutionistocreateaFederatedarchitecture,whichisanextensionofHubandSpokethat
allowsformultiplehubstoprovideloadsharingandbackupincaseoffailure.
4.DISTRIBUTEDINTEGRATIONARCHITECTURE
Indistributedarchitecture:
Messagetranslation,routing,spli ing,andcombiningareperformedclosertosourceandtargetsystembyusingsmallercomputerscalledagents.Agent
computersareconnectedtojustonesystemandreducetheprocessingloadonthatsystem.Agentstakeinformationfromtheapplicationtheyareconnected
to,processit,andsendittoanytargetapplication(s)interestedinreceivingthatinformation.
Thisisalsoknownaspeertopeerintegrationarchitecture.
WhataretheadvantagesofDistributedarchitecture?
Distributedarchitectureisgovernedbycentralizedrulesandtherequirementsofthebusinessow.Mostoftheprocessingisperformedinagentprocessors
locatednearthesourceandtargetapplications.Besidesgainsinprocessingeciencybydistributingtheworkloadamongdedicatedprocessors,a
DistributedArchitectureisabletogrowrelativelyeasily.
WhatarethedisadvantagesofDistributedarchitecture?
Manyorganizationshaveamixofplatformsandoperatingsystemsonwhichtheirbusinessapplicationsrun,asituationthatisoftentheresultofmergers
andacquisitions.Whenitbecomesnecessarytochangeorexpandthesystemarchitecture,itisunfortunatelynotsimplyama erofchoosingoneofthe
distributedtechnologiesandimplementingit.Optingforonetechnologymayonlyprovideadistributedsolutionforhalfofyourorganizationduetothe
mixofsystemsthatarebeingused.Beyondtheseinternalproblems,thereisalsotheissueofengaginginBusinesstoBusiness(B2B)exchangeswithother
companies.ThisisanothercasewhereaneclecticmixofsystemsandtechnologiesbetweenbusinessescanimpedetheuseofDistributedArchitecture.
5.SERVICEORIENTEDARCHITECTURE(SOA)
ServiceOrientedArchitecture(SOA)isthelatestarchitecturalapproach,althoughitsnotreallyverynew.
ServiceOrientedArchitectureisessentiallyanenhancedversionofDistributedArchitecturethatuseslooselycoupledsoftwareservicestosupportthe
requirementsofbusinessprocessesandsoftwareusers.
Itgoesastepfurtherthanthepreviousarchitecturesbyprovidinganintegratedenvironmentwhichspreadsouttheworkload,breakingdownthedierent
silosofbusinessfunctionalityandopeningtheirprocessestootherapplications.

silosofbusinessfunctionalityandopeningtheirprocessestootherapplications.

ApplicationscomprisedoflooselyboundWebServices.
OnewaytothinkofSOAislikeaLegoset.ALegosetismorethanjusttheindividualblocks;specializedbiggerpiecesforcomplexcreationsarealso
available.Similarly,withSOA,anapplicationcancustomizeand/orchangetheindividualpiecesorservicesthatituses.Usingtheseconcepts,vastand
complexcomponentbasedapplicationscanbedeveloped.
ThebreakthroughforSOAcamewiththeacceptanceofWebServices,wheredierentvendorsagreetoacommoncommunicationastandardwhichisXML.
AfterWebServicescameEnterpriseServiceBus(ESB)technology.BasedonWebServices,andexhibitingallofthecharacteristicsoftheMessagingsolutions
previouslysuppliedbytheintegrationvendors,ESBhasbecometheacceptedstandardforthecreationofanorganizationsServiceOrientedArchitecture.
WithoutexceptionalloftheintegrationvendorsnowprovideanSOAarchitecturebuiltontheconceptofanEnterpriseServiceBus(ESB).
Tosummarizethedenition,SOAisanarchitecturepa erntointegratelooselycoupledapplicationsintoonesystem.
ITcompanieshavestartedtorealizethattheultimateobjectivethesedaysforbuildingasystemwouldbetoautomatebusinessprocessesi.e.todevelop
applicationsthatwouldprovideacompleteowoftheprocessfromitsendtothebeginning.
TherearemanychallengesthatanITcompanybuildingtheapplicationwouldface.Twoofthebasicchallengeswhichlaythebasicfoundationofthe
developingbusinessprocessare:
1)Everycompanydoesnothavethesamerequirements.
2)Changesareconstantlyincorporatedinabusinessprocesstocompete;theenterpriseservicehastobeexibleenoughtoincorporatethechanges.
Ifyouarestillnotclearwiththedenitionyoumaysaythatthisstatementcontradictwiththebasicrequirementonwhichaserviceisbuildi.e.stabilityand
availabilitytoprocessasandwhenrequired.Hereitgoesagainwithverysimpleandclearwords.SOAisaggregationofsuchstableservices.Servicesare
constructedtobestableandecientwhileaggregationsaredesignedtobeagileorratheracceptthechanges.
Hencetheselooselycoupledservices(ServiceOriented)aggregationsaremuchmoreopentochangesratherthantheorthodoxmonolithicservicesthat
requireagestoincorporateevenasmallchangeintheservice.
Nowthequestionsariseshowaretheseindependentstableservicesaggregatedtodesignalooselycoupledsystem?Howdoweensurethatthestabilityof
theservicewillbemaintainedifitiscoupledwithanotherservicewhichisconstructedonadierentplatform?
Theanswertothequestionsisstandardizationoftheplatformonwhichtheservicesarecoupled.Theseservicesremainstablebyrelyingthemselveson
standardbasedinterfacesandstandard/denedmessages(SOAP/Schemas).
IhopethebasicquestionofwhySOAisintroducedinITindustryandhowwoulditlooklikeinatopviewofthesystemisclear.
Forabeginnertherearemillionsofquestionsthatneedstobeansweredwithrespecttotheingredientstocouplingofservices,howaretheseservices
deployedandonwhatplatformdowecoupleorratherhowdoweincorporatethestandardizationtointegratethissystem.Ihopethenextupcomingsection
ofSOAwouldanswertheirquestions.
6.EXTENSIBLEMARKUPLANGUAGE
WhatisXML?
FromdenitionsofW3C:
XMLstandsforEXtensibleMarkupLanguage.
XMLisamarkuplanguagemuchlikeHTML.
XMLwasdesignedtocarryandstoredata,nottodisplaydata.
XMLtagsarenotpredened.Youmustdeneyourowntags.
XMLisdesignedtobeselfdescriptive.
XMLisaW3CRecommendation.
Example:
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Dontforgetmethisweekend!</body>
</note>
Where:
Thetagsintheexampleabove(like<to>and<from>)arenotdenedinanyXMLstandard.
5/9/2017
Where: 3DaysTutorialinOSB|SOALair
Thetagsintheexampleabove(like<to>and<from>)arenotdenedinanyXMLstandard.
ThesetagsareinventedbytheauthoroftheXMLdocument.
WhatisXMLnamespace?
XMLNamespacesprovideamethodtoavoidelementnameconicts.
TheXMLnamespaceisaspecialtypeofreservedXMLa ributethatyouplaceinanXMLtag.
Thereserveda ributeisactuallymorelikeaprexthatyoua achtoanynamespaceyoucreate.
Thisa ributeprexisxmlns:,whichstandsforXMLNameSpace.
Thecolonisusedtoseparatetheprexfromyournamespacethatyouarecreating.
WhatisXMLSchema?
AnXMLSchemadescribesthestructureofanXMLdocument.
TheXMLSchemalanguageisalsoreferredtoasXMLSchemaDenition(XSD).
AnXMLSchema:
deneselementsthatcanappearinadocument
denesa ributesthatcanappearinadocument
deneswhichelementsarechildelements
denestheorderofchildelements
denesthenumberofchildelements
deneswhetheranelementisemptyorcanincludetext
denesdatatypesforelementsanda ributes
Denesdefaultandxedvaluesforelementsanda ributes.
7.WEBSERVICEDESCRIPTIONLANGUAGE
WhatisWSDL?
WSDLstandsforWebServicesDescriptionLanguage
WSDLiswri eninXML
WSDLisanXMLdocument
WSDLisusedtodescribeWebservices
WSDLisalsousedtolocateWebservicesandtheoperations(ormethods)theserviceexposes.
WSDLisaW3Crecommendation.
Tostartwithanysoftwarewehaveclientrequirements.
Theserequirementsdenetheinputandtheoutputelementsoftheservice.
ThedatatypesoftheinputandoutputmessagesintermsifwhethertheinputmessagewillhaveaUserIDwithalengthdenedof8charactersanditshout
beofstringtype.
Theserequirementsarelikeacontractbetweentheprovideroftheserviceandtheuseroftheservice.Theusercannotaccesstheserviceifitprovidesthe
input(UserID)withmorethan8charactersandtheprovideroftheserviceneedstothrowafaultormaketheserviceunavailablefortheuserwithUserID
morethan8characters.
ThiscontactisdenedinadocumentcalledWSDLonwhichwebserviceisconstructed.
YoucansaythatWSDListhestiltofawebservice.
WSDLisdenitionofwebserviceinitslanguagei.e.XML.
Itisacontractbetweentheserviceproviderandtheuser.
Itisadescriptionofthewebservice.
WSDLcanbebrokendownto4criticalchunks.
1.Interfaceinformation/Operationinformation.
2.MessageInformation/Datatypeinformation.
3.BindingInformation/TransportInformation.
4.AddressInformation/LocationInformation.
WithrespecttoconstructingaWSDLitcanbedenedwith6majorelements:
1.denitions
2.types
2.types
3.message
4.portType
5.binding
6.service
YoumightbethinkingwhyIhavewri entheelementsnameinlowercase.
Thiswouldsoundabitstupidbutthisishowtheelementsappearinthewsdldenition.
LetuslookatasampleWSDLnow.
<?xmlversion=1.0encoding=UTF8standalone=no?>
<wsdl:denitionsxmlns:soap=h p://schemas.xmlsoap.org/wsdl/soap/
xmlns:tns=h p://www.example.org/NewWSDLFile/xmlns:wsdl=h p://schemas.xmlsoap.org/wsdl/xmlns:xsd=h p://www.w3.org/2001/XMLSchema
name=NewWSDLFiletargetNamespace=h p://www.example.org/NewWSDLFile/>
<wsdl:types>
<xsd:schematargetNamespace=h p://www.example.org/NewWSDLFile/>
<xsd:elementname=NewOperation>
<xsd:complexType>
<xsd:sequence>
<xsd:elementname=intype=xsd:string/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:elementname=NewOperationResponse>
<xsd:complexType>
<xsd:sequence>
<xsd:elementname=outtype=xsd:string/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:messagename=NewOperationRequest>
<wsdl:partelement=tns:NewOperationname=parameters/>
</wsdl:message>
<wsdl:messagename=NewOperationResponse>
<wsdl:partelement=tns:NewOperationResponsename=parameters/>
</wsdl:message>
<wsdl:portTypename=NewWSDLFile>
<wsdl:operationname=NewOperation>
<wsdl:inputmessage=tns:NewOperationRequest/>
<wsdl:outputmessage=tns:NewOperationResponse/>
</wsdl:operation>
</wsdl:portType>
<wsdl:bindingname=NewWSDLFileSOAPtype=tns:NewWSDLFile>
<soap:bindingstyle=documenttransport=h p://schemas.xmlsoap.org/soap/h p/>

<soap:operationsoapAction=h p://www.example.org/NewWSDLFile/NewOperation/>
<wsdl:input>
<soap:bodyuse=literal/>
</wsdl:input>
<wsdl:output>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:servicename=NewWSDLFile>
<wsdl:portbinding=tns:NewWSDLFileSOAPname=NewWSDLFileSOAP>
<soap:addresslocation=h p://www.example.org//>
</wsdl:port>
</wsdl:service>
</wsdl:denitions>
IntheWSDLdescribedaboveallthe6elementsarehighlightedinblack.YouwouldbynowhaveconcludedthataWSDLisaggregationofthese6elements.
Letusnowseewhatexactlythese6elementsconsistsofandwhyaretheyincludedinaWSDLdenition.
1)denitions:ItistherootelementofalltheWSDLdocument.
Itdenesthenameofthewebservice.
<wsdl:denitionsname=NewWSDLFilexmlns:soap=h p://schemas.xmlsoap.org/wsdl/soap/xmlns:tns=h p://www.example.org/NewWSDLFile/

xmlns:wsdl=h p://schemas.xmlsoap.org/wsdl/xmlns:xsd=h p://www.w3.org/2001/XMLSchema
targetNamespace=h p://www.example.org/NewWSDLFile/>
</wsdl:denitions>
Itdenesvariousnamespacesthatisusedthroughoutthedocument.
2)types:Itdescribesthedatatypeofthemessagebeingexchanged.
Ifthemessageexchangeisonlyintermsofsimpledatatypesasstringandintegerthenthistypeselementwouldnotberequired.
OnemorethingtonoticeisWSDLdoesnotuseanyexclusivetypingsystem,butifnotdeclareditusesW3CXMLschemaspecicationsasthedefaultchoice.
<wsdl:types>
<xsd:schematargetNamespace=h p://www.example.org/NewWSDLFile/>
<xsd:elementname=NewOperation>
<xsd:complexType>
<xsd:sequence>
<xsd:elementname=intype=xsd:string/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:elementname=NewOperationResponse>
<xsd:complexType>
<xsd:sequence>
<xsd:elementname=outtype=xsd:string/>
</xsd:sequence>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
3)messages:Itprovidestheabstractofthemessagebeingtransferredinaonewaytransmission.Itcancontainoneormorepartelementswhichcanrefer
tomessageparametersorreturnvalues.
<wsdl:messagename=NewOperationRequest>
<wsdl:partelement=tns:NewOperationname=parameters/>
</wsdl:message>
<wsdl:messagename=NewOperationResponse>
<wsdl:partelement=tns:NewOperationResponsename=parameters/>
</wsdl:message>
4)portType:portTypecombinesmultiplemessageelementsdenedabovetocompletetheroundtripoftheoperation.Eachoperationtocompleteits
serviceneedstohaveasetofrequestandresponsemessagewhichisdescribedinthemessageelements.
EachportTypecanhavemultipleoperationselement.
<wsdl:portTypename=NewWSDLFile>
<wsdl:inputmessage=tns:NewOperationRequest/>
<wsdl:outputmessage=tns:NewOperationResponse/>
</wsdl:operation>
</wsdl:portType>
Letuslinkupthe3elementsaboveandseewherewehavereachedintermsofWSDLdescription.
Startingfromthebo om,eachwebservicehasanoperationoritcanhavemanyoperationstoperform.Eachoperationduringitsservicetakesaninput
requestanddeliversanoutputresponse.ThisoperationisdenedinportTypeelementdescribedabove.Thisinputandoutputmessageshasmultiple
parametersordatatypesthatisdescribedintheelementmessage.Thedatatypecanbedenedseparatelyasacombinationofmanysubdatatypesor
elementswhichisdescribesundertypeselement.
5)binding:Thiselementdescribestheconcreteprotocol/standardonwhichtheservicewillbeimplemented.Itdescribesthedataformatspecicationon
whichthemessageandoperationsaredened.WSDLhasabuildinextensionfordeningSOAPbasedservices.HenceSOAPspecicinformationgoes
underthiselement.
<wsdl:bindingname=NewWSDLFileSOAPtype=tns:NewWSDLFile>
<soap:operationsoapAction=h p://www.example.org/NewWSDLFile/NewOperation/>
<wsdl:input>
</wsdl:input>
<wsdl:output>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
6)service:Thiselementdescribesthelocationortheaddressforinvokingtheservice.Itisusedtoaggregateasetofportstoretrievethelocationtoaccess
thespecicservice.
<wsdl:portbinding=tns:NewWSDLFileSOAPname=NewWSDLFileSOAP>
<soap:addresslocation=h p://www.example.org//>
</wsdl:port>
</wsdl:service>
SothereitiswearedonewiththecreationofaWSDL.Alltheelementsdenedhereaggregatedwillletusdeneawebservicecontract.
ThisWSDLisaveryimportantaspectofawebservice.
Thiscontractdenesalltheelements/parametersneededintherequestandresponseoftheoperationandwhichisagreeduponbytheprovideranduserof
thewebservice.
Basedontherequirementsfromtheclienttheelementsaredescribedinthemessages.
TheinputthatisreceivedfromtheusertotheoperationisvalidatedagainsttheoperationelementsdescribedintheWSDL.Theirinputcannotviolatethe
descriptionoftheinputmessageintheWSDL,whichisanimportantaspectofwebservicessecurityoperations.
8.ORACLESERVICEBUS
Asexplainedearlierservicebusisasolutiontoproblemsfacedbypoorintegrationarchitecture.
1.8.
8.1.Bus,whatBus?
TheuseofaServiceBuspa ernhelpstodecouplethepiecesfromeachother,messagesarepassedbetweenthecomponentsintheformofasynchronous
eventtopicsinapublish/subscribepa ern,thatallowseveryparttobedecoupledfromtheotherpartandwedonotneedtospantransactionsorhold
connectionsbetweentheinternalcomponentsthatwouldultimatelycauseadegradationintheperformanceofthesystem.
TheServiceBusshouldalsoperformtheroutingofmessagesbetweenthecomponentssonocomponentswouldhavetobedependentontheknowledgeof
thelocationofanothercomponent.
Connectionsbetweentheuserinterfacewillandshouldbepointtopointasthisisrequiredforthecomponenttoperformitsdutywithintheconstraintsthat
areimposeduponit,thesameholdstrueforsoftwarearchitectures.
Thereductionofdependencyonotherpartsshouldbedrivenasfardownintothearchitectureasisreasonable,asthiswillleadonedownthepathof
exibilityandtestability.
Introduction:
Aproven,lightweight,congurationbased,policydrivenintegrationtechnologyspecicallydesignedforthetaskofintegrating,virtualizing,scalingservice
management,andtraditionalmessagebrokeringacrossheterogeneousITenvironmentsandmanagingservicesinaserviceorientedarchitecture(SOA),
OracleServiceBusenablesyoutoachievevaluemorequicklywithsimple,codefree,congurationbasedserviceintegration.Youwillbeabletomove
towardenterprisewideSOAdeploymentswithahighperformance,highlyscalableSOAintegrationbackbone.
TheOracleServiceBus(OSB)providesservicebuscapabilitiesfortheentirecompany,againincludingstandardfunctionalityastransformation,routing,
eventdeliveryandpayloadvalidation.Itsmainfunctionistodecoupleintraapplicationcommunicationfrominterapplication.Endpointchangeswillnot
aecttheinternalsofcompositeapplications.TheOSBisbasedontheAqualogicServiceBus,augmentedwithkeyfeaturesfromtheOracleESB,especially
JCAadapters,DVM,XrefandJDevbaseddesigntime.
Advantages:
Locationtransparency:Isolatefromchangestoservicelocation.
Backwardcompatibility:isolatefromchangestoservicecontactonthenewserviceadded.
Serviceenablement:allowmultipleprotocols/messagestoparticipateinSOA.
Dynamicrouting:Usebusinessrulestodeterminedestinationservice.
Dynamicrouting:Usebusinessrulestodeterminedestinationservice.
Messageenrichment:updatethemessageusingtheresponsefromanotherservice.
8.2.ResourcesinOracleServiceBus
InOracleServiceBusworld,alltheartifactsarecalledtheOSBresources.InatypicalSOAenvironment,therewillbeaneedtosharethedierentresources
acrosstheprojects.TheresourcescanbeanythinglikeWSDLs,XSDs,Proxy,Businessserviceetc..
WecannotcreateallkindsofresourcesintheOSBCongurationProject.ForexamplecreatingWSDLorXSDincongurationprojectwillgivetheerror.We
canonlycreatetheGlobalResourceslikeProxyServer,JNDIProviderandSMTPServer.AlltheseresourcesthatcanbecreatedintheOSBConguration
ProjectcanbeaccessedfromdierentOSBprojectspresentintheCongurationProject.
8.3.ProxyServicesandBusinessServices
OracleServiceBusprovidesintelligentmessagebrokeringbetweenbusinessservices(suchasenterpriseservicesanddatabases)andserviceclients(suchas
presentationapplicationsorotherbusinessservices)throughproxyservicesthatyoucancongureusingOracleServiceBusConsole.Proxyservicesare
OracleServiceBusdenitionsofintermediaryWebservicesthatOracleServiceBusimplementslocallyonWebLogicServer.WithOracleServiceBus
messagebrokering,serviceclientsexchangemessageswithanintermediaryproxyserviceratherthanworkingdirectlywithabusinessservice.
OracleServiceBusallowsyoutoimplementproxyservicesindependentlyandcongurethemdynamically,asdrivenbyyourbusinessneedswithout
requiringcostlyinfrastructuredevelopmenteorts.ThecongurationfunctionsareseparatedfromthemanagementfunctionsinOracleServiceBusConsole.
Aproxyservicecanroutemessagestomultiplebusinessservices;youcanchoosetocongureaproxyservicewithaninterfacethatisindependentofthe
businessserviceswithwhichtheproxyservicecommunicates.Insuchcases,youcancongureamessageowdenitiontorouteamessagetothe
appropriatebusinessserviceandmapthemessagedataintotheformatrequiredbythebusinessservicesinterface.
BusinessservicesareOracleServiceBusdenitionsoftheenterpriseservicesthatexchangemessagesduringbusinessprocesses.Abusinessserviceandits
interfacecanbedenedandconguredusingtheOracleServiceBusConsole.Tocongureabusinessserviceyoumustspecifyitsinterface,typeoftransport
ituses,itssecurityrequirements,andothercharacteristics.
Abusinessservicedenitionissimilartothatofaproxyservice,butitdoesnothaveapipeline.
8.4.MessageFlowsandPipelines
InOracleServiceBus,amessageowistheimplementationofaproxyservice.Youcongurethelogicforthemanipulationofmessagesusingproxyservice
messageowdenitions.Thislogicincludessuchactivitiesastransformation,publishing,andreporting,whichareimplementedasindividualactions
withinthestagesofapipeline.
Pipelinesareonewayprocessingpathsthatincludenobranching.Apipelineisanamedsequenceofstagescontainingactions,representinganonbranching
Pipelinesareonewayprocessingpathsthatincludenobranching.Apipelineisanamedsequenceofstagescontainingactions,representinganonbranching
onewayprocessingpath.Itisusedtospecifythemessageowforservicerequestsandresponses.Astageisauserconguredprocessingstep.Messagesfed
intothepipelinesareaccompaniedbyasetofmessagecontextvariablesthatcontainthemessagecontents.Theycanbeaccessedormodiedbyactionsin
thepipelinestages.
8.5.PipelinePairs
Pipelinepairsarerequestandresponsepipelines.TherequestpipelinedenitionspeciestheactionsthatOracleServiceBusperformsonrequestmessages
totheproxyservicebeforeinvokingabusinessserviceoranotherproxyservice.TheresponsepipelinedenitionspeciestheprocessingthatOracleService
Busperformsonresponsesfromthebusinessorproxyservicethattheproxyserviceinvokesbeforereturningaresponsetoaclient.
Eachpipelineconsistsofasequenceofstages,eachstagecontainingactions.However,asingleservicelevelrequestpipelinemightoptionallybranchout
intooperationalpipelines(youcancongureonedefaultoperationalpipelineatmostoneperoperation).Thedeterminationoftheoperationisdonethrough
userselectedcriteria.Theresponseprocessingstartswiththerelevantoperationpipelinewhichthenjoinsintoasingleservicelevelresponsepipeline.
Figure13(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/tutorial/tutIntro.html#wp1045160)illustratessampleoperationpipelinesina
proxyservice.
Figure13ExampleofOperationPipelinesinaProxyService
8.6.MessageFlowComponents
Amessageowiscomposedofcomponentsthatdenethelogicforroutingandmanipulatingmessagesastheyowthroughaproxyservice.Nodesare
conguredtoroutemessagesthroughthemessageow,andstagesandactionscontainrulesforprocessingandtransformingmessages.
Mostoftheprocessinglogicinamessageowishandledinpipelines.Apipelineisanamedsequenceofstagesrepresentinganonbranchingoneway
processingpath.Pipelinesbelongtooneofthefollowingcategories:
Requestpipelinesprocesstherequestpathofthemessageow.
Responsepipelinesprocesstheresponsepathofthemessageow.
Errorpipelineshandleerrorsforstagesandnodesinamessageowaswellaserrorsatthelevelofthemessageow(service).
Toimplementtheprocessinglogicofaproxyservice,requestandresponsepipelinesarepairedtogetherinpipelinepairnodes.Thesepipelinepairnodes
canbecombinedwithothernodesintoasinglerootedtreestructuretocontroloverallow.
Table31(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1118731)describesthecomponents
availablefordeningmessageows.
Component Summary
Type
Startnode Everymessageowbeginswithastartnode.Allmessagesenterthemessageowthroughthestartnode,andallresponsemessagesare
returnedtotheclientthroughthestartnode.Thereisnothingtocongureinastartnode.
Pipeline Apipelinepairnodecombinesasinglerequestpipelineandasingleresponsepipelineinonetoplevelelement.Apipelinepairnodecan
pairnode haveonlyonedirectdescendantinthemessageow.Duringrequestprocessing,onlytherequestpipelineisexecutedwhenOracleService
Busprocessesapipelinepairnode.TheexecutionpathisreversedwhenOracleServiceBusprocessestheresponsepipeline.
Stage Requestpipelines,responsepipelines,anderrorhandlerscancontainstages,whereyoucongureactionstomanipulatemessagespassing
throughthepipeline.
Error Anerrorhandlercanbea achedtoanynodeorstage,tohandlepotentialerrorsatthatlocation.
handler
Branch Abranchnodeallowsprocessingtoproceedalongexactlyoneofseveralpossiblepaths.OperationalbranchingissupportedforWSDL
node basedservices,wherethebranchingisbasedonoperationsdenedintheWSDL.Conditionalbranchingissupportedforconditions
denedinanXPathbasedswitchtable.
Routenode Aroutenodeperformsrequest/responsecommunicationwithanotherservice.Itrepresentstheboundarybetweenrequestandresponse
processingfortheproxyservice.Whentheroutenodedispatchesarequestmessage,therequestprocessingisconsideredcomplete.When
theroutenodereceivesaresponsemessage,theresponseprocessingbegins.Theroutenodesupportsconditionalroutingaswellasrequest
andresponsetransformations.
Becausearoutenoderepresentstheboundarybetweenrequestandresponseprocessing,itcannothaveanydescendantsinthemessage
ow.
Figure31(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1060397)showsahighlevelviewof13/45
Figure31(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1060397)showsahighlevelviewof
componentsinamessageowdenition.
Figure31ComponentsofMessageFlow
8.7.BuildingaMessageFlow
Theonlycomponentsrequiredinamessageowareastartnodeandaroutenode.Norestrictionsexistonwhatothercomponentscanbechainedtogether
inthemessageow.Youcouldcreateasingleroutenodethatcontainedallthelogicfortheow.Or,youcouldlinktwopipelinepairnodeswithouta
branchnodeinbetween.Ifyouusebranchnodes,eachbranchnodecouldstartwithadierentelement.Onebranchcouldterminatewitharoutenode,
anothercouldbefollowedbyapipelinepair,andyetanothercouldhavenodescendant.(Whenabranchwithnodescendantsisexecutedatruntime,
responseprocessingbeginsimmediately.)
However,ingeneral,amessageowislikelytobedesignedinoneofthefollowingways:
Fornonoperationalservices(servicesthatarenotbasedonWSDLswithoperations),theowconsistsofasinglepipelinepairattherootfollowedbya
routenode.
Foroperationalservices,theowconsistsofasinglepipelinepairattheroot,followedbyabranchnodebasedonanoperation,witheachbranch
consistingofapipelinepairfollowedbyaroutenode.
8.8.MessageExecution
Tablebelowdescribeshowmessageareprocessesinatypicalmessageow:
MessageFlowNode Whathappensduringmessageprocessing?
RequestProcessing
Startnode Requestprocessingbeginsatthestartnode.
Pipelinepairnode Executestherequestpipelineonly.
Branchnode Evaluatesthebranchtableandproceedsdowntherelevant
branch.
Routenode Performstheroutealongwithanyrequesttransformations.
Inthemessageow,regardlessofwhetherroutingtakesplace
ornot,theroutenoderepresentsthetransitionfromprocessing
arequesttoprocessingaresponse.Attheroutenode,the
directionofthemessageowisreversed.Ifarequestpathdoes
nothavearoutenode,theresponseprocessingisinitiatedin
thereversedirectionwithoutwaitingforanyresponse.
ResponseProcessing Skipsanybranchnodesandcontinueswiththenodethat
precededthebranch
Routenode Executesanyresponsetransformations.
Branchnode Skipsanybranchnodesandcontinueswiththenodethat
precededthebranch
Pipelinepairnode Executestheresponsepipeline
Startnode Sendstheresponsebacktotheclient
8.9.BranchinginMessageFlows
Twokindsofbranchingaresupportedinmessageows:operationalbranching,conguredinanoperationalbranchnode,andconditionalbranching,
conguredinaconditionalbranchnode.
8.9.1.OperationalBranching
WhenmessageowsdeneWSDLbasedproxyservices,operationspecicprocessingisrequired.Whenyoucreateanoperationalbranchnodeina
messageow,youcanbuildbranchinglogicbasedontheoperationsdenedintheWSDL.
YoumustuseoperationalbranchingwhenaproxyserviceisbasedonaWSDLwithmultipleoperations.Youcanconsiderusinganoperationalbranchnode
tohandlemessagesseparatelyforeachoperation.
8.9.2.ConditionalBranching
Useconditionalbranchingtobranchbasedonaspeciedcondition,forexamplethedocumenttypeofamessage.
Conditionalbranchingisdrivenbyalookuptablewitheachbranchtaggedwithsimple,uniquestringvalues,forexample,QuantityEqualToOrLessThan150
andQuantityMoreThan150.
Youcancongureaconditionalbranchtobranchbasedonthevalueofavariableinthemessagecontext(declared,forexample,inastageearlierinthe
messageow),oryoucanconguretheconditiontobranchbasedontheresultsofanXPathexpressiondenedinthebranchitself.
Atruntime,thevariableortheexpressionisevaluated,andtheresultingvalueisusedtodeterminewhichbranchtofollow.Ifnobranchmatchesthevalue,
thedefaultbranchisfollowed.Abranchnodemayhaveseveraldescendantsinthemessageow:oneforeachbranch,includingthedefaultbranch.You
shouldalwaysdeneadefaultbranch.Youshoulddesigntheproxyserviceinsuchawaythatthevalueofalookupvariableissetbeforereachingthebranch
node.
Forexample,considerthefollowingcaseusingalookupvariable.AproxyserviceisoftypeanySOAPoranyXML,andyouneedtodeterminethetypeof
themessagesoyoucanperformconditionalbranching.Youcandesignastageactiontoidentifythemessagetypeandthendesignaconditionalbranching
nodelaterintheowtoseparateprocessingbasedonthemessagetype.
NowconsiderthefollowingcaseusinganXPathexpressionintheconditionalbranchnode.Youwanttobranchbasedonthequantityinanorder.That
quantityispassedviaavariablethatcanberetrievedfromaknownlocationin$body.
YoucoulddenethefollowingXPathexpressiontoretrievethequantity:
declarenamespaceopenuri=h p://www.openuri.org/&#8221(h p://www.openuri.org/&#8221);;
declarenamespacecom=oracle.com/demo/orders/cmnCust;
./openuri:processCust/com:cmnCust/com:Order_Items/com:Item/com:Quantity
Thecondition(forexample,<500)isthenevaluatedinorderdownthemessageowagainsttheexpression.Whicheverconditionissatisedrstdetermines
whichbranchisfollowed.Ifnobranchconditionissatised,thenthedefaultbranchisfollowed.
Youcanuseconditionalbranchingtoexposetheroutingalternativesforthemessageowatthetoplevelowview.Forexample,considerasituationwhere
youwanttoinvokeserviceAorserviceBbasedonaconditionknownearlyinthemessageow(forexample,themessagetype).Youcouldcongurethe
conditionalbranchinginaroutingtableintheroutenode.However,thatmakesthebranchingsomewhatmorediculttofollowifyouarejustlookingat
thetopleveloftheow.Instead,youcoulduseaconditionalbranchnodetoexposethisbranchinginthemessageowitselfandusesimpleroutenodesas
thesubowsforeachofthebranches.
Consideryourbusinessscenariobeforedecidingwhetheryoucongurebranchinginthemessageoworinastageorroutenode.Whenmakingyour
decision,rememberthatconguringbranchesinthemessageowcanbeawkwardinthedesigninterfaceifalargenumberofbranchesextendfromthe
branchnode.
8.10.ConfiguringActionsinStagesandRouteNodes
Actionsprovideinstructionsforhandlingmessagesinpipelinestages,errorhandlerstages,androutenodes.Thecontextdetermineswhichactionsare
availableintheOracleServiceBusConsoleorintheOracleServiceBusPluginsforWorkshopforWebLogic,asdescribedinthefollowingsections:
CommunicationActions(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1126011)
FlowControlActions(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1125471)
MessageProcessingActions(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1070403)
ReportingActions(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1080496)
8.10.1.CommunicationActions
Communicationactionscontrolmessageow:
Action Use Availablein
Dynamicpublish Publishamessagetoa Pipelinestage

servicespeciedbyan Errorhandlerstage
XQueryexpression Routenode
Publish Identifyastatically Pipelinestage

speciedtargetservicefor Errorhandlerstage
amessageandtocongure
howthemessageis
packagedandsenttothat
service
Publishtable Publishamessagetozero Pipelinestage
ormorestaticallyspecied Errorhandlerstage
services.Switchstyle
conditionlogicisusedto
determineatruntime
whichserviceswillbeused
forthepublish
Routingoptions Modifyanyorallofthe Pipelinestage
followingpropertiesinthe
outboundrequest:URI,
QualityofService,Mode,
Retryparameters,Message
Priority
Servicecallout Congureasynchronous Pipelinestage
(blocking)callouttoan Errorhandlerstage
OracleServiceBus
registeredproxyor
businessservice.
Transportheaders Settheheadervaluesin Pipelinestage
messages Errorhandlerstage
8.10.2.FlowControlActions
Flowcontrolsactionsimplementconditionalrouting,conditionallooping,anderrorhandling.Youcanalsousethemtonotifytheinvokerofsuccessorto
skiptherestoftheactionsinthestage:
Action Useto. Availablein

Foreach Iterateoverasequenceof Pipelinestage
valuesandexecuteablock
ofactions Errorhandlerstage
Ifthen Performanactionorsetof Pipelinestage

actionsconditionally, Routenode
basedontheBooleanresult
ofanXQueryexpression Errorhandlerstage
Raiseerror Raiseanexceptionwitha Pipelinestage

speciederrorcode(a
string)anddescription Errorhandlerstage
Reply Specifythatanimmediate Pipelinestage

replybesenttothe
invoker. Errorhandlerstage
Thereplyactioncanbe
usedintherequest,
responseorerrorpipeline.
Youcancongureitto
resultinareplywith
successorfailure.Inthe
caseofreplywithfailure
wheretheinbound
transportisHTTP,the
replyactionspeciesthat
animmediatereplyissent
totheinvoker
Resume Resumemessageowafter Errorhandlerstage

anerrorishandledbyan
errorhandler.Thisaction
hasnoparametersandcan
onlybeusedinerror
handlers
Skip Specifythatatruntime,the Pipelinestage
executionofthisstageis Errorhandlerstage
skippedandtheprocessing
proceedstothenextstage
inthemessageow.This
actionhasnoparameters
andcanbeusedinthe
request,responseorerror
pipelines
8.10.3.MessageProcessingActions
Theactionsinthiscategoryprocessthemessageow.Table35
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1123526)describesthemessageprocessing
actions.
Action Use Location

Assign AssigntheresultofanXQueryexpressiontoacontextvariable. Pipeline
stage
Error
handler
stage
Delete DeleteacontextvariableorasetofnodesspeciedbyanXPathexpression. Pipeline

stage
Error
handler
stage
Insert InserttheresultofanXQueryexpressionatanidentiedplacerelativetonodesselectedbyanXPathexpression. Pipeline

stage
Error
handler
stage
Java InvokeaJavamethod,orEJBbusinessservice,fromwithinthemessageow. Pipeline

callout stage
Error
handler
stage
MFL ConvertmessagecontentfromXMLtononXML,orviceversa,inthemessagepipeline.AnMFLisaspecializedXMLdocument Pipeline

transform usedtodescribethelayoutofbinarydata.ItisanOracleproprietarylanguageusedtodenerulestotransformforma edbinary stage
dataintoXMLdata,orviceversa.
Error
handler
stage
Rename RenameelementsselectedbyanXPathexpressionwithoutmodifyingthecontentsoftheelement. Pipeline

stage
Error
handler
stage
Replace ReplaceanodeorthecontentsofanodespeciedbyanXPathexpression.Thenodeoritscontentsarereplacedwiththevalue Pipeline

returnedbyanXQueryexpression. stage
Areplaceactioncanbeusedtoreplacesimplevalues,elementsandevena ributes.AnXQueryexpressionthatreturnsnothingis Error

equivalenttodeletingtheidentiednodesormakingthemempty,dependinguponwhethertheactionisreplacingentirenodesor handler
justnodecontents. stage
ThereplaceactionisoneofasetofUpdateactions.
Validate ValidateelementsselectedbyanXPathexpressionagainstanXMLschemaelementoraWSDLresource.Youcanvalidateglobal Pipeline

elementsonly;OracleServiceBusdoesnotsupportvalidationagainstlocalelements. stage
Error
handler
stage
8.10.4.ReportingActions
Youusetheactionsinthiscategorytologorreporterrorsandgeneratealertsifrequiredinamessageowwithinastage.Table34
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1123189)describesthereportingactions.
Action Useto Available

in
Alert Generatealertsbasedonmessagecontextinapipeline,tosendtoanalertdestination.UnlikeSLAalerts,noticationsgeneratedby Pipeline
thealertactionareprimarilyintendedforbusinesspurposes,ortoreporterrors,andnotformonitoringsystemhealth.Alert stage
destinationshouldbeconguredandchosenwiththisinmind.
Error
Ifpipelinealertingisnotenabledfortheserviceorenabledatthedomainlevel,theconguredalertactionisbypassedduring handler
messageprocessing. stage
Log Constructamessagetobeloggedandtodeneasetofa ributeswithwhichthemessageislogged. Pipeline

stage
Error
handler
stage
Report Enablemessagereportingforaproxyservice. Pipeline

stage
Error
handler
stage
8.11.ConfiguringTransportHeadersinMessageFlows
Thetransportheaderactionisacommunicationtypeaction,anditisavailableinpipelinestagesanderrorhandlerstages.
8.11.1.ConfiguringGlobalPassThroughandHeaderSpecificCopyOptionsfor
TransportHeaders
Thefollowingoptionsareavailablewhenyoucongureatransportheadersaction:
ThePassallHeadersthroughPipelineoptionspeciesthatatruntime,thetransportheadersactionpassesallheadersthroughfromtheinbound
messagetotheoutboundmessageorviceversa.Everyheaderinthesourcesetofheadersiscopiedtothetargetheaderset,overwritinganyexisting
valuesinthetargetheaderset.
TheCopyHeaderfromInboundRequestoptionandtheCopyHeaderfromOutboundResponseoptionsspeciesthatatruntime,thetransport
headersactioncopiesthespecicheaderwithwhichthisoptionisassociatedfromtheinboundmessagetotheoutboundmessageorviceversa.
Usetheoptionsinawaythatbestsuitsyourscenario.Bothoptionsresultintheheadersinthesourceheadersetbeingcopiedtothetargetheaderset,
overwritinganyexistingvalueinthetargetset.NotethatthePassallHeadersthroughPipelineoptionisexecutedbeforetheheaderspecicCopyHeader
options.Inotherwords,foragiventransportheadersactionconguration,ifyouselectPassallHeadersthroughPipeline,thereisnoneedtoselectthe
CopyHeaderoptionforgivenheaders.
However,youcanselectPassallHeadersthroughPipelinetocopyallheaders,andsubsequentlyconguretheactionsuchthatindividualheadersare
deletedbyselectingDeleteHeaderforspecicheaders.
WARNING: Becausetransportheadersarespecictothetransporttypes,itisrecommendedthatthepassthrough(orcopy)optionsonlybeusedto
copyheadersbetweenservicesofthesametransporttype.Passing(orcopying)headersbetweenservicesofdierenttransporttypescan
resultinanerroriftheheaderbeingpassedisnotacceptedbythetargettransport.Forthesamereasons,becarefulwhenyouspecifya
headernameusingtheSetHeaderoption.
8.11.1.1.UnderstandingHowtheRunTimeUsestheTransportHeadersSettings
Asdescribedabove,youcanusetransportheaderactionstocongurethevaluesofthetransportheadersforoutboundrequests(themessagessentoutbya
proxyserviceinroute,publish,orservicecalloutactions)andinboundresponses(theresponsemessagesaproxyservicesendsbacktoclients).Ingeneral,
theheadervaluescanbe:
SpeciedusinganXQueryexpression
Passedthroughfromthesourcetothetargetservice
Deletedwhilegoingfromthesourcetothetargetservice
Thetransportheadersactionallowsyoutoset,delete,orpassthroughtheheadersin$inboundor$outbound.Ifyousetordeletetheseheadersandthenlog
$inboundor$outbound,youcanseetheeectsofyourchanges.However,whenthemessageissentout,theOracleServiceBusbindinglayermaymodifyor
removesomeheadersin$inboundor$outboundandtheunderlyingtransportmayinturn,ignoresomeoftheseheadersanduseitsownvalues.An
importantdistinctionisthatanymodicationsdonebythebindinglayeronaheaderaredonedirectlyto$inboundand$outbound,whereasmodications
donebythetransportaectsonlythemessageswireformat.Forexample,althoughyoucanspecifyavaluefortheoutboundContentLengthheader,the
bindinglayerdeletesitfrom$outboundwhensendingthemessage.Consequently,themodicationisvisibleintheresponsepath(forexample,youcansee
themodiedvalueifyoulog$outbound).IfyousettheUserAgentheaderin$outbound,theHTTPtransportignoresitanduseitsownvaluehowever,the
valuein$outboundisnotchanged.
Table37(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1120452)describesthetransportheaders
thatareignoredoroverwri enatruntimeandotherlimitationsthatexistforspecictransportheaders.
Transport DescriptionofLimitation TransportHeadersAectedByLi

OutboundRequest
HTTP OracleServiceBusruntimemayoverwritetheseheadersinthebindinglayerwhenpreparingthemessagefor ContentType
dispatch.Iftheseheadersaremodied,$inboundand$outboundareupdatedaccordingly.
Theunderlyingtransportmayignoretheseheadersandusedierentvalueswhensendingthemessage.Any Accept
changesdonebythetransportwillnotbereectedin$inboundor$outbound.
ContentLength
Connection
Host
UserAgent
JMS Canonlybesetwhentherequestiswithrespecttoaonewayserviceorarequest/responseservicebasedon JMSCorrelationID

JMSMessageIDcorrelation.
Ifsendingtoarequest/responseservicebasedonJMSCorrelationIDcorrelation,theseheadersareoverwri enat
runtime.
Shouldbesettothemessagetimetoliveinmilliseconds.Theresultingvalueinthemessagereceivedisthesumof JMSExpiration
thetimetolivevaluespeciedbytheclientandtheGMTatthetimeofthesendorpublish1
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1120514).
TheOracleServiceBusruntimesetstheseheaders.Inotherwords,anyspecicationsyoumakefortheseheadersat JMSMessageID
designtimeareoverwri enatruntime.
JMSRedelivered
JMSTimestamp
JMSXDeliveryCount
JMSXUserID
JMS_IBM_PutDate2
(h p://download.oracle.com/docs
JMS_IBM_PutTime2
JMS_IBM_PutApplType2
JMS_IBM_Encoding2
JMS_IBM_Character_Set2
BecauseIBMMQdoesnotallowcertainpropertiestobesetbyaclientapplication,ifyousettheseheaderswith JMSXDeliveryCount
respecttoanIBMMQdestination,aruntimeexceptionisraised.
JMSXUserID
JMSXAppID
TheseheaderscannotbedeletedwhenthePassallHeadersthroughPipelineoptionisalsospecied. JMSDeliveryMode
JMSExpiration
JMSMessageID
JMSRedelivered
JMSTimestamp
JMSXDeliveryCount
FTP Nolimitations.Inotherwordsyoucansetordeletetheheader(s)3
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1120617)
File forFileandFTPtransportsandyourspecicationsarehonoredbytheOracleServiceBusruntime.
Email TheOracleServiceBusruntimesetstheseheaders.Inotherwords,anyspecicationsyoumakefortheseheadersat ContentType

designtimeareoverwri enatruntime.
OracleServiceBusdoesnotusetheseheadersforoutboundrequests.Ifyousetthemdynamically(thatis,ifyouset From(Name)
theminthe$outboundheaderssection),OracleServiceBusignoresthem.
Date
Theseheadersarereceivedin$inbound.Dateisthetimethemailwassentbythesender.Fromisretrievedfrom
incomingmailheaders.
Forexample,ifyousettheJMSExpirationheaderto1000,andatthetimeofthesend,GMTis1,000,000(asaresultofSystem.currentTimeMillis()),ther
HeadernameswiththeJMS_IBMprexaretobeusedwithrespecttodestinationshostedbyanIBMMQserver
ForFTPandleproxies,thereisantransportrequestheaderleName.Thevalueofthisrequestheaderisthenameofthelebeingpolled.
Note Thesamelimitationsaroundse ingcertaintransportheadersandmetadataaretruewhenyousettheinboundandoutboundcon
8.12.PerformingTransformationsinMessageFlows
Transformationmapsdescribethemappingbetweentwodatatypes.OracleServiceBussupportsdatamappingthatusestheXQueryandtheeXtensible
StylesheetLanguageTransformation(XSLT)standards.XSLTmapsdescribeXMLtoXMLmappings.XQuerymapscandescribeXMLtoXML,XMLtonon
XML,andnonXMLtoXMLmappings.
Thepointinamessageowatwhichyouspecifyatransformationdependsonwhether:
Themessageformatreliesontargetservicesthatis,themessageformatmustbeinaformatacceptablebytheroutedestination.Thisapplieswhenthe
transformationisperformedinaroutenodeorinoneofthepublishactions.
Publishactionsidentifyatargetserviceforamessageandcongurehowthemessageispackagedandsenttothatservice.OracleServiceBusalsoprovides
publishtableactions.Apublishtableactionconsistsofasetofrouteswrappedinaswitchstyleconditiontable.Itisashorthandconstructthatallows
dierentroutestobeselected,basedupontheresultsofasingleXQueryexpression.
Youperformthetransformationontheresponseorrequestmessageregardlessoftheroutedestination.Inthiscase,youcancongurethe
transformationsintherequestorresponsepipelinestages.
8.13.TransformationsandPublishActions
Whentransformationsaredesignedinpublishactions,thetransformationshavealocalcopyofthe$outboundvariableandmessagerelatedvariables
($header,$body,and$a achments).Anychangesyoumaketoanoutboundmessageinapublishactionaectonlythepublishedmessage.Inotherwords,
thechangesyoumakeinthepublishactionarerolledbackbeforethemessageowproceedstoanyactionsthatfollowthepublishactioninyourmessage
ow.
Forexample,consideramessageowthatdealswithalargepurchaseorder,andyouhavetosendthesummaryofthepurchaseorder,throughemail,to
themanager.ThesummaryoftheofthepurchaseorderiscreatedintheSOAPbodyoftheincomingmessagewhenyouincludeapublishactioninthe
requestpipeline.Inthepublishaction,thepurchaseorderdataistransformedintoasummaryofthepurchaseorderforexample,allthea achmentsin
$a achmentscanbedeletedbecausetheyarenotrequiredinthesummaryofthepurchaseorder.
8.14.TransformationsandRouteNodes
Youmayneedtoroutemessagestooneoftwodestinations,basedonaWSaddressingheader.Inthatcase,contentbasedroutingandthesecond
destinationrequirethenewerversionofthedocumentintheSOAPbody.Inthissituation,youcanconguretheroutenodetoconditionallyroutetooneof
thetwodestinations.Youcancongureatransformationintheroutenodetotransformthedocumentfortheseconddestination.
Youcanalsosetthecontrolelementsintheoutboundcontextvariable($outbound)toinuencethebehaviorofthesystemfortheoutboundmessage(for
example,youcansettheQualityofService).
SeeInboundandOutboundVariables(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1107145)andConstructing
MessagestoDispatch(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1057143)forinformationaboutthesub
elementsoftheinboundandoutboundvariablesandhowthecontentofmessagesisconstructedusingthevaluesofthevariablesinthemessagecontext.
8.15.ConstructingServiceCalloutMessages
WhenOracleServiceBusmakesacalltoaserviceviaaservicecalloutaction,thecontentofthemessageisconstructedusingthevaluesofvariablesinthe
messagecontext.Themessagecontentforoutboundmessagesishandleddierentlydependinguponthetypeofthetargetservice.
HowthemessagecontentiscreateddependsonthetypeofthetargetserviceandwhetheryouchoosetoconguretheSOAPbodyorthepayload
(parametersordocument),asdescribedinthefollowingtopics:
SOAPDocumentStyleServices(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1134675)
SOAPRPCStyleServices(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1103510)
XMLServices(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1103547)
MessagingServices(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1103564)
8.16.SOAPDocumentStyleServices
MessagesforSOAPDocumentStyleservices(includingEJBdocumentanddocumentwrappedservices),canbeconstructedasfollows:
ThevariableassignedfortherequestdocumentcontainstheSOAPbody.
ThevariableassignedfortheSOAPrequestheadercontainstheSOAPheader.
ThevariableassignedfortheSOAPrequestheadercontainstheSOAPheader.
TheresponsemustbeasingleXMLdocumentitisthecontentoftheSOAPbodyplustheSOAPheader(ifspecied)
ToillustratehowmessagesareconstructedduringcalloutstoSOAPDocumentStyleservices,consideraservicecalloutactionconguredasfollows:
RequestDocumentVariable:myreq
ResponseDocumentVariable:myresp
SOAPRequestHeader:reqheader
SOAPResponseHeader:respheader
Assumealsothatatruntime,therequestdocumentvariable,myreq,isboundtothefollowingXML.
Listing31ContentofRequestVariable(myreq)
<sayHelloxmlns=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);

<intVal>100</intVal>
<string>Hello</string>
</sayHello>
Atruntime,theSOAPrequestheadervariable,reqheader,isboundtothefollowingSOAPheader.
Listing32ContentofSOAPRequestHeaderVariable(reqheader)
<soap:Headerxmlns:soap=h p://schemas.xmlsoap.org/soap/envelope/
xmlns:wsa=h p://schemas.xmlsoap.org/ws/2003/03/addressing&gt(h p://schemas.xmlsoap.org/ws/2003/03/addressing&gt);
<wsa:Action></wsa:Action>
<wsa:To></wsa:To>
<wsa:From></wsa:From>
<wsa:ReplyTo></wsa:ReplyTo>
<wsa:FaultTo></wsa:FaultTo>
</soap:Header>
Inthisexamplescenario,thefullbodyofthemessagesenttotheexternalserviceisshowninListing33
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1103498)(thecontentsofthemyreqand
reqheadervariablesareshowninbold).
Listing33MessageSenttotheServiceasaResultofServiceCalloutAction
<?xmlversion=1.0encoding=UTF8?>
<soapenv:Envelopexmlns:soapenv=h p://schemas.xmlsoap.org/soap/envelope/&gt(h p://schemas.xmlsoap.org/soap/envelope/&gt);
<soap:Headerxmlns:soap=hp://schemas.xmlsoap.org/soap/envelope/
xmlns:wsa=hp://schemas.xmlsoap.org/ws/2003/03/addressing&gt(hp://schemas.xmlsoap.org/ws/2003/03/addressing&gt);
<wsa:Action></wsa:Action>
<wsa:To></wsa:To>
<wsa:From></wsa:From>
<wsa:ReplyTo></wsa:ReplyTo>
<wsa:FaultTo></wsa:FaultTo>
</soap:Header>
<soapenv:Body>
<sayHelloxmlns=hp://www.openuri.org/&gt(hp://www.openuri.org/&gt);
</sayHello>
</soapenv:Body>
</soapenv:Envelope>
Basedonthecongurationoftheservicecalloutactiondescribedabove,theresponsefromtheserviceisassignedtothemyrespvariable.Thefullresponse
fromtheexternalserviceisshowninListing34
Listing34ResponseMessageFromtheServiceasaResultofServiceCalloutAction
<env:Envelopexmlns:env=h p://schemas.xmlsoap.org/soap/envelope/&#8221(h p://schemas.xmlsoap.org/soap/envelope/&#8221);
xmlns:xsi=h p://www.w3.org/2001/XMLSchemainstance&#8221(h p://www.w3.org/2001/XMLSchemainstance&#8221);
xmlns:soapenc=h p://schemas.xmlsoap(h p://schemas.xmlsoap).
org/soap/encoding/xmlns:xsd=h p://www.w3.org/2001/XMLSchema&gt(h p://www.w3.org/2001/XMLSchema&gt);
<env:Header/>
<env:Bodyenv:encodingStyle=h p://schemas.xmlsoap.org/soap/encoding/&gt(h p://schemas.xmlsoap.org/soap/encoding/&gt);
<m:sayHelloResponsexmlns:m=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);
<resultxsi:type=xsd:string>ThismessagebroughttoyoubyHelloandthenumber100
</result>
</m:sayHelloResponse>
</env:Body>
</env:Envelope>
Inthisscenario,themyrespvariableisassignedthevalueshowninListing35
Inthisscenario,themyrespvariableisassignedthevalueshowninListing35
Listing35ContentofResponseVariable(myresp)asaResultofServiceCalloutAction

<resultns0:type=xsd:stringxmlns:ns0=h p://www.w3.org/2001/XMLSchemainstance&gt(h p://www.w3.org/2001/XMLSchemainstance&gt);
ThismessagebroughttoyoubyHelloandthenumber100
</result>
8.17.SOAPRPCStyleServices
MessagesforSOAPRPCStyleservices(includingEJBRPCservices)canbeconstructedasfollows:
Requestmessagesareassembledfrommessagecontextvariables.
TheSOAPbodyisbuiltbasedontheSOAPRPCformat(operationwrapper,parameterwrappers,andsoon).
TheSOAPheaderisthecontentofthevariablespeciedfortheSOAPrequestheader,ifoneisspecied.
Partaselementtheparametervalueisthevariablecontent.
Partassimpletypetheparametervalueisthestringrepresentationofthevariablecontent.
Partascomplextypetheparametercorrespondstorenamingtherootofthevariablecontentaftertheparametername.
Responsemessagesareassembledasfollows:
TheoutputcontentisthecontentofSOAPheader,ifaSOAPheaderisspecied.
Partaselementtheoutputcontentisthechildelementoftheparameter;thereisatmostonechildelement.
Partassimple/complextypetheoutputcontentistheparameteritself.
ToillustratehowmessagesareconstructedduringcalloutstoSOAPRPCStyleservices,lookatthisexamplewiththefollowingconguration:
Amessagecontextvariableinput1isboundtoavalue100.
Amessagecontextvariableinput2isboundtoastringvalue:Hello.
Aservicecalloutactionconguredasfollows:
RequestParameterintval:input1
RequestParameterstring:input2
ResponseParameterresult:output1
Inthisscenario,thebodyoftheoutboundmessagetotheserviceisshowninListing36
Listing36ContentofOutboundMessage
<soapenv:Envelopexmlns:soapenv=h p://schemas.xmlsoap.org/soap/envelope/&gt(h p://schemas.xmlsoap.org/soap/envelope/&gt);
<soapenv:Body>
<sayHello2xmlns=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);
</sayHello2>
</soapenv:Body>
</soapenv:Envelope>
TheresponsereturnedbytheservicetowhichthecallwasmadeisshowninListing37
Listing37ContentofResponseMessageFromthehelloWorldService
<env:Envelopexmlns:env=h p://schemas.xmlsoap.org/soap/envelope/&#8221(h p://schemas.xmlsoap.org/soap/envelope/&#8221);
xmlns:xsi=h p://www.w3.org/2001/XMLSchemainstance&#8221(h p://www.w3.org/2001/XMLSchemainstance&#8221);
xmlns:soapenc=h p://schemas.xmlsoap.org/soap/encoding/&#8221(h p://schemas.xmlsoap.org/soap/encoding/&#8221);
xmlns:xsd=h p://www.w3.org/2001/XMLSchema&gt(h p://www.w3.org/2001/XMLSchema&gt);
<env:Header/>
<env:Bodyenv:encodingStyle=h p://schemas.xmlsoap.org/soap/encoding/&gt(h p://schemas.xmlsoap.org/soap/encoding/&gt);
<m:sayHello2Responsexmlns:m=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);
<resultxsi:type=n1:HelloWorldResultxmlns:n1=java:>
<messagexsi:type=xsd:string>
ThismessagebroughttoyoubyHelloandthenumber100
</message>
</result>
</m:sayHello2Response>
</m:sayHello2Response>
</env:Body>
</env:Envelope>
Themessagecontextvariableoutput1isassignedthevalueshowninListing38
Listing38ContentofOutputVariable(output1)
<messagens0:type=xsd:stringxmlns:ns0=h p://www.w3.org/2001/XMLSchemaintance&gt(h p://www.w3.org/2001/XMLSchemaintance&gt);

ThismessagebroughttoyoubyHelloandthenumber100</message>
8.18.XMLServices
MessagesforXMLservicescanbeconstructedasfollows:
Therequestmessageisthecontentofthevariableassignedfortherequestdocument.
ThecontentoftherequestvariablemustbeasingleXMLdocument.
Theoutputdocumentistheresponsemessage.
ToillustratehowmessagesareconstructedduringcalloutstoXMLservices,takeforexampleaservicecalloutactionconguredasfollows:
RequestDocumentVariable:myreq
ResponseDocumentVariable:myresp
Assumealsothatatruntime,therequestdocumentvariable,myreq,isboundtothefollowingXML.
Listing39ContentofmyreqVariable
<sayHelloxmlns=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);

</sayHello>
Inthisscenario:
Theoutboundmessagepayloadisthevalueofthemyreqvariable,asshowninTable39
Theresponseandthevalueassignedtothemessagecontextvariable,myresp,isshowninListing310
Listing310ContentofmyrespVariable

<resultxsi:type=xsd:string>ThismessagebroughttoyoubyHelloandthenumber100
</result>
8.19.MessagingServices
InthecaseofMessagingservices:
Therequestmessageisthecontentoftherequestvariable.Thecontentcanbesimpletext,XML,orbinarydatarepresentedbyaninstanceof<binary
contentref=/>referenceXML.
Responsemessagesaretreatedasbinary,sotheresponsevariablewillcontainaninstanceof<binarycontentref=/>referenceXML,regardlessofthe
actualcontentreceived.
Forexample,iftherequestmessagecontextvariablemyreqisboundtoanXMLdocumentofthefollowingformat:<hello>there</hello>,theoutbound
messagecontainsexactlythispayload.Theresponsemessagecontextvariable(myresp)isboundtoareferenceelementsimilartothefollowing:
<binarycontentref=cid:18507337599555665022ca29e5c.1079b180f61.7fd8/>
8.20.HandlingErrorsastheResultofaServiceCallout
Youcancongureerrorhandlingatthemessageow,pipeline,routenode,andstagelevel.Thetypesoferrorsthatarereceivedfromanexternalserviceas
Youcancongureerrorhandlingatthemessageow,pipeline,routenode,andstagelevel.Thetypesoferrorsthatarereceivedfromanexternalserviceas
theresultofaservicecalloutincludetransporterrors,SOAPfaults,responsesthatdonotconformtoanexpectedresponse,andsoon.
Thefaultcontextvariableissetdierentlyforeachtypeoferrorreturned.Youcanbuildyourbusinessanderrorhandlinglogicbasedonthecontentofthe
faultvariable.Tolearnmoreabout$fault,seeFaultVariable
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1051816).
8.21.TransportErrors
WhenatransporterrorisreceivedfromanexternalserviceandthereisnoerrorresponsepayloadreturnedtoOracleServiceBusbythetransportprovider
(forexample,inthecasethatanHTTP403errorcodeisreturned),theservicecalloutactionthrowsanexception,whichinturncausesthepipelinetoraisean
error.Thefaultvariableinausercongurederrorhandlerisboundtoamessageforma edsimilarlytothatshowninListing311
Listing311ContentsoftheOracleServiceBusfaultVariableTransportError,noErrorResponsePayload
<con:faultxmlns:con=h p://www.bea.com/wli/sb/context&gt(h p://www.bea.com/wli/sb/context&gt);

<con:errorCode>BEA380000</con:errorCode>
<con:reason>NotFound</con:reason>
<con:details>
.
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:Pipeline>PipelinePairNode1_request</con:Pipeline>
<con:Stage>Stage1</con:Stage>
</con:location>
</con:fault>
Inthecasethatthereisapayloadassociatedwiththetransporterrorforexample,whenanHTTP500errorcodeisreceivedfromthebusinessserviceand
thereisXMLpayloadintheresponseamessagecontextfaultisgeneratedwiththecustomerrorcode:BEA382502.
ThefollowingconditionsmustbemetforaBEA382502errorresponsecodetobetriggeredastheresultofaresponsefromaservicewhenthatserviceuses
anHTTPorJMStransport:
(HTTP)Theresponsecodemustbeanycodeotherthan200or202.
(JMS)Theresponsemusthaveapropertysettoindicatethatitisanerrorresponsethetransportmetadatastatuscodesetto1indicatesanerror.
Thecontenttypemustbetext/xml.
IftheserviceisAnySoaporWSDLbasedSOAP,thenitmusthaveaSOAPenvelope.ThebodyinsidetheSOAPenvelopemustbeXMLformat;itcannot
betext.
IftheservicetypeisAnyXML,oramessagingserviceoftypetextreturnsXMLcontentwithanonsuccessfulresponsecode(anycodeotherthan200or
202).
IfthetransportisHTTP,theErrorResponseDetailelementwillalsocontaintheHTTPerrorcodereturnedwiththeresponse.TheErrorResponseDetail
elementinthefaultcontainserrorresponsepayloadreceivedfromtheservice.Listing312
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1103763)showsanexampleofthe
ErrorResponseDetailelement.
Listing312ContentsoftheOracleServiceBusfaultVariableTransportError,withErrorResponsePayload
<ctx:Faultxmlns:ctx=h p://www.bea.com/wli/sb/context&gt(h p://www.bea.com/wli/sb/context&gt);

<ctx:errorCode>BEA382502<ctx:errorCode>
<ctx:reason>Servicecallouthasreceivedanerrorresponsefromtheserver</ctx:reason>
<ctx:details>
<alsb:ErrorResponseDetailxmlns:alsb=h p://www.oracle.com/&gt(h p://www.oracle.com/&gt);
<alsb:detail><![CDATA[
...
]]>
</alsb:detail><alsb:h presponsecode>500</alsb:h presponsecode>
</alsb:ErrorResponseDetail>
</ctx:details>
<ctx:location>...</ctx:location>
</ctx:Fault>
Note: TheXMLschemafortheservicecalloutgeneratedfaultisshowninXMLSchemafortheServiceCalloutGeneratedFaultDetails
8.22.SOAPFaults
IncaseanexternalservicereturnsaSOAPfault,theOracleServiceBusruntimesetsupthecontextvariable$faultwithacustomerrorcodeand
descriptionwiththedetailsofthefault.Todoso,thecontentsofthe3elementsunderthe<SOAPENV:Fault>elementintheSOAPfaultareextractedand
usedtoconstructanOracleServiceBusfaultelement.
Takeforexampleascenarioinwhichaservicereturnsthefollowingerror.
Listing313SOAPFaultReturnedFromServiceCallout
<SOAPENV:Envelopexmlns:SOAPENV=h p://schemas.xmlsoap.org/soap/envelope/&gt(h p://schemas.xmlsoap.org/soap/envelope/&gt);

<SOAPENV:Body>
<SOAPENV:Fault>
<faultcode>SOAPENV:Client</faultcode>
<faultstring>ApplicationError</faultstring>
<detail>
<message>ThatsanError!</message>
<errorcode>1006</errorcode>
</detail>
</SOAPENV:Fault>
</SOAPENV:Body>
</SOAPENV:Envelope>
The<faultcode>,<faultstring>,and<detail>elementsareextractedandwrappedinan<alsb:ReceivedFault>element.Notethatthefaultcode
elementinListing315(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1103806)containsa
QNameanyrelatednamespacedeclarationsarepreserved.IfthetransportisHTTP,theReceivedFaultelementwillalsocontaintheHTTPerrorcode
returnedwiththefaultresponse.
Thegenerated<alsb:ReceivedFault>element,alongwiththecustomerrorcodeandtheerrorstringareusedtoconstructthecontentsofthefault
contextvariable,whichinthisexampletakesaformatsimilartothatshowninListing314
Listing314ContentsoftheOracleServiceBusFaultVariableSOAPFault
<ctx:Faultxmlns:ctx="http://www.bea.com/wli/sb/context">
<ctx:errorCode>BEA382500<ctx:errorCode>
<ctx:reason>servicecalloutreceivedasoapFaultresponse</ctx:reason>
<ctx:details>
<alsb:ReceivedFaultxmlns:alsb="http://www.oracle.com/...">
<alsb:faultcode
xmlns:SOAPENV="http://schemas.xmlsoap.org/soap/envelope/">SOAPENV:Clien
</alsb:faultcode>
<alsb:faultstring>ApplicationError</alsb:faultstring>
<alsb:detail>
<message>ThatsanError!</message>
<errorcode>1006</errorcode>
</alsb:detail>
<alsb:httpresponsecode>500</alsb:httpresponsecode>
</alsb:ReceivedFault>
</ctx:details>
<ctx:location></ctx:location>
</ctx:Fault>
Note: TheuniqueerrorcodeBEA382500isreservedforthecasewhenservicecalloutactionsreceiveSOAPfaultresponses.
8.23.UnexpectedResponses
Whenaservicereturnsaresponsemessagethatisnotwhattheproxyserviceruntimeexpects,amessagecontextfaultwillbegeneratedandinitializedwith
thecustomerrorcodeBEA382501.ThedetailsofthefaultincludethecontentsoftheSOAPBodyelementoftheresponse.IfthetransportisHTTP,the
ReceivedFaultelementwillalsocontaintheHTTPerrorcodereturnedwiththefaultresponse.
TheXMLschemadenitionoftheservicecalloutgeneratedfaultdetailsisshowninListing315
Listing315XMLSchemafortheServiceCalloutGeneratedFaultDetails
<xs:complexTypename=ReceivedFaultDetail>
<xs:sequence>
<xs:elementname=faultcodetype=xs:QName/>
<xs:elementname=faultstringtype=xs:string/>
<xs:elementname=detailminOccurs=0>
<xs:complexType>
<xs:complexType>
<xs:sequence>
<xs:anynamespace=##anyminOccurs=0maxOccurs=unboundedprocessContents=lax/>
</xs:sequence>
<xs:anyA ributenamespace=##anyprocessContents=lax/>
</xs:complexType>
</xs:element>
<xs:elementname=h presponsecodetype=xs:intminOccurs=0/>\
type=xs:intminOccurs=0/>
</xs:sequence>
</xs:complexType>
<xs:complexTypename=UnrecognizedResponseDetail>
<xs:sequence>
<xs:elementname=detailminOccurs=0type=xs:string/>
</xs:sequence>
</xs:complexType>
<xs:complexTypename=ErrorResponseDetail>
<xs:sequence>
<xs:elementname=detailminOccurs=0type=xs:string/>
</xs:sequence>
</xs:complexType>
8.24.HandlingErrorsinMessageFlows
Theprocessdescribedinthenextparagraphconstitutesanerrorhandlingpipelineforthestageofanerrorhandler.Inaddition,anerrorpipelinecanbe
denedforapipeline(requestorresponse)orforanentireproxyservice.
Theerrorhandleratthestagelevelisinvokedforhandlinganerror;Ifthestagelevelerrorhandlerisnotabletohandleagiventypeoferror,thepipeline
errorhandlerisinvoked.Ifthepipelinelevelerrorhandleralsofailstohandletheerror,theservicelevelerrorhandlerisinvoked.Iftheservicelevelerror
handleralsofails,theerrorishandledbythesystem.Thefollowingtablesummarizesthescopeoftheerrorhandlersatvariouslevelsinthemessageow.
Level Scope
Stage Handlesalltheerrorswithinastage.
Pipeline Handlesalltheerrorsinapipeline,alongwithanyunhandlederrorsfromanystageinapipeline.
Service Handlesalltheerrorsinaproxyservice,alongwithanyunhandlederrorsinanypipelineinaservice.
Note: AllWSSecurityerrorsarehandledatthislevel.
System Handlesalltheerrorsthatarenothandledanywhereelseinapipeline.
Note: Thereareexceptionstothescopeoferrorhandlers.Forexample,anexceptionthrownbyanonXMLtransformationatthestagelevelisonly
caughtbytheservicelevelerrorhandler.SupposeatransformationoccursthattransformsXMLtoMFLforanoutgoingproxyserviceresponse
message,italwaysoccursinthebindinglayer.Therefore,forexample,ifanonXMLoutputismissingamandatoryeldatthestagelevel,onlya
servicelevelerrorhandlercancatchthiserror.
Formoreinformationonerrormessagesanderrorhandling,seeProxyServices:ErrorHandlers
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyerrors.html)inUsingtheOracleServiceBusConsole.
Youcanhandleerrorsbyconguringatestthatchecksifanassertionistrueandusethereplyactionconguredfalse.Youcanrepeatthistestatvarious
levels.Alsoyoucanhaveanerrorwithoutanerrorhandleratalowerlevelandhandleitthroughanerrorhandleratanhigherlevelinmessageow.
Ingeneral,itiseasiertohandlespecicerrorsatastagelevelofthemessageowanduseerrorhandlersatthehigherlevelformoregeneraldefault
processingoferrorsthatarenothandledatthelowerlevels.Itisgoodpracticetoexplicitlyhandleanticipatederrorsinthepipelinesandallowtheservice
levelhandlertohandleunanticipatederrors.
Note: YoucanonlyhandleWSSecurityrelatederrorsattheservicelevel.
8.25.GeneratingtheErrorMessage,Reporting,andReplying
Apredenedcontextvariable(thefaultvariable)isusedtoholdinformationaboutanyerrorthatoccursduringmessageprocessing.Whenanerroroccurs,
Apredenedcontextvariable(thefaultvariable)isusedtoholdinformationaboutanyerrorthatoccursduringmessageprocessing.Whenanerroroccurs,
thisvariableispopulatedwithinformationbeforetheappropriateerrorhandlerisinvoked.Thefaultvariableisdenedonlyinerrorhandlerpipelinesand
isnotsetinrequestandresponsepipelines,orinrouteorbranchnodes.Foradditionalinformationabout$fault,seePredenedContextVariables
Intheeventoferrorsforrequest/responsetypeinboundmessages,itisoftennecessarytosendamessagebacktotheoriginatoroutliningthereasonwhyan
erroroccurred.YoucanaccomplishthisbyusingaReplywithFailureactionafterconguringthemessagecontextvariableswiththeresponseyouwantto
send.Forexample,whenanHTTPmessagefails,ReplywithFailuregeneratestheHTTP500status.WhenaJMSmessagefails,ReplywithFailuresetsthe
JMS_BEA_Errorpropertytotrue.TheOracleServiceBuserroractionsarediscussedinProxyServices:ErrorHandlers
AnerrorhandlingpipelineisinvokedifaserviceinvokedbyaproxyservicereturnsaSOAPfaultortransporterror.AnyreceivedSOAPfaultisstoredin
$body,soifaReplywithFailureisexecutedwithoutmodifying$body,theoriginalSOAPfaultisreturnedtotheclientthatinvokedtheservice.Ifareply
actionisnotcongured,thesystemerrorhandlergeneratesanewSOAPfaultmessage.TheproxyservicerecognizesthataSOAPfaultisreturnedbecausea
HTTPerrorstatusisset,ortheJMSpropertySERVER_Errorissettotrue.
Someusecasesrequireerrorreporting.Youcanusethereportactioninthesesituations.Forexample,considerascenarioinwhichtherequestpipeline
reportsamessagefortrackingpurposes,buttheserviceinvokedbytheroutenodefailsafterthereportingaction.Inthiscase,thereportingsystemlogged
themessage,butthereisnoguaranteethatthemessagewasprocessedsuccessfully,onlythatthemessagewassuccessfullyreceived.
YoucanusetheOracleServiceBusConsoletotrackthemessagetoobtainanaccuratepictureofthemessageow.Thisallowsyoutoviewtheoriginal
reportedmessageindicatingthemessagewassubmi edforprocessing,andalsothesubsequentreportederrorindicatingthatthemessagewasnot
processedcorrectly.Tolearnhowtocongureareportactionandusethedatareportedatruntime,seeProxyServices:Actions
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyactions.html)inUsingtheOracleServiceBusConsole.
8.26.ExampleofActionConfigurationinErrorHandlers
Thisexampleshowshowyoucancongurethereportandreplyactionsinerrorhandlers.ThemessageowshowninFigure32
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1063705)includesanerrorhandleronthevalidate
loanapplicationstage.TheerrorhandlerinthiscaseisasimplemessageowwithasinglestagecongureditisrepresentedintheOracleServiceBus
ConsoleasshowninFigure32(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1063705).
Figure32ErrorHandlerMessageFlow
Thestageis,inturn,conguredwithactions(replace,report,andreply)asshowninFigure33
Figure33ActionsinStageErrorHandler
Theactionscontrolthebehaviorofthestageinthepipelineerrorhandlerasfollows:
ReplaceThecontentsofaspeciedelementofthebodyvariablearereplacedwiththecontentsofthefaultcontextvariable.Thebodyvariableelement
isspeciedbyanXPathexpression.ThecontentsarereplacedwiththevaluereturnedbyanXQueryexpressioninthiscase
$fault/ctx:reason/text()
ReportMessagesfromthereportingactionarewri entotheOracleServiceBusReportingDataStreamiftheerrorhandlerconguredwiththisaction
isinvoked.TheJMSReportingProviderreportsthemessagesontheOracleServiceBusDashboard.OracleServiceBusprovidesthecapabilitytodeliver
messagedatatooneormorereportingproviders.Messagedataiscapturedfromthebodyofthemessageandfromanyothervariablesassociatedwith
themessage,suchasheaderorinboundvariables.Youcanusethemessagedeliveredtothereportingproviderforfunctionssuchastrackingmessagesor
regulatoryauditing.
Whenanerroroccurs,thecontentsofthefaultcontextvariablearereported.ThekeynameiserrorCode,andthekeyvalueisextractedfromthefault
variableusingthefollowingXPathexpression:./ctx:errorCode.Key/valuepairsarethekeyidentiersthatidentifythesemessagesintheDashboardat
runtime.
Tocongureareportactionandusethedatareportedatruntime,seeProxyServices:Actions
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyactions.html)inUsingtheOracleServiceBusConsole.
ReplyAtruntime,animmediatereplyissenttotheinvokeroftheloanGateway3proxyservice(seeFigure33
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1063796))indicatingthatthemessagehada
faultThereplyisWithFailure.
Forcongurationinformation,seeProxyServices:ErrorHandlers
Whenyoudonotknowtheserviceyouneedtoinvokefromtheproxyserviceyouarecreating,youcanusedynamicrouting.
Foranygivenproxyservice,youcanuseoneofthefollowingtechniquestodynamicallyroutemessages:
Inamessageowpipeline,designanXQueryexpressiontodynamicallysetthefullyqualiedservicenameinOracleServiceBusandusethedynamic
routeordynamicpublishactions.
Note:
DynamicRoutingcanbeachievedinaroutenode,whereasdynamicpublishingcanachievedinastageinarequestpipelineoraresponsepipeline.
Withthistechnique,theproxyservicedynamicallyusestheserviceaccountoftheendpointbusinessservicetosendusernamesandpasswordsinits
outboundrequests.Forexample,ifaproxyserviceisroutingarequesttoBusinessServiceA,thentheproxyserviceusestheserviceaccountfrom
BusinessServiceAtosendusernamesandpasswordsinitsoutboundrequest.SeeImplementingDynamicRouting
BusinessServiceAtosendusernamesandpasswordsinitsoutboundrequest.SeeImplementingDynamicRouting
Congureaproxyservicetorouteorpublishmessagestoabusinessservice.Then,intherequestactionssectionfortherouteactionorpublishaction,
addaRoutingOptionsactionthatdynamicallyspeciestheURIofaservice.
Withthistechnique,tosendusernamesandpasswordsinitsoutboundrequests,theproxyserviceusestheserviceaccountofthestaticallydened
businessservice,regardlessoftheURItowhichtherequestisactuallysent.
Forinformationonhowtousethistechnique,seeImplementingDynamicRouting
Note:
Thistechniqueisusedwhentheoverviewoftheinterfaceisxed.Theoverviewoftheinterfaceincludesmessagetypes,porttypes,andbinding,and
excludestheconcreteinterface.TheconcreteinterfaceisthetransportURLatwhichtheserviceislocated.
ImplementingDynamicRouting
Youcanusedynamicroutingtodeterminethedestinationduringtheruntimeofaproxyservice.ToachievethisyoucanusearoutingtableinanXML
letocreateanXQueryresource.
Note:
InsteadofusingtheXQueryresource,youcanalsodirectlyusetheXMLlefromwhichtheresourceiscreated.
AnXMLleortheXqueryresourcecanbemaintainedeasily.Atruntimeyouprovidetheentryintheroutingtablethatwilldeterminetheroutingor
publishingdestinationoftheproxyservice.TheXMLleortheXQueryresourcecontainsaroutingtable,whichmapsalogicalidentierto(suchasthe
nameofacompany)tothephysicalidentier(thefullyqualiednameoftheserviceinOracleServiceBus).Thelogicalidentier,whichisextractedfrom
themessage,mapsontothephysicalidentier,whichisthenameoftheserviceyouwanttoinvoke.
Note:
Tousethedynamicrouteaction,youneedthefullyqualiednameoftheserviceinOracleServiceBus.
InapipelinethelogicalidentierisobtainedwithanXPathintothemessage.YouassigntheXMLtableintheXQueryresourcetoavariable.You
implementaqueryagainstthevariableintheroutingtabletoextractthephysicalidentierbasedonthecorrespondinglogicalidentier.Usingthis
variableyouwillbeabletoinvoketherequiredservice.Thefollowingsectionsdescribehowtoimplementdynamicrouting.
SampleXMLFile(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1099442).
CreatinganXQueryResourceFromtheSampleXML
CreatingandConguringtheProxyServicetoImplementDynamicRouting
8.27.UsingDynamicRouting
8.28.SampleXMLFile
YoucancreateanXQueryresourcefromthefollowingXMLle.SavethisassampleXquery.xml.
Listing316SampleXMLFile
<routing>
<row>
<logical>Sample</logical>
<physical>default/goldservice</physical>
</row>
<row>
<logical>ABCCorp</logical>
<physical>default/silverservice</physical>
</row>
</routing>
8.29.CreatinganXQueryResourceFromtheSampleXML
Inanactivesession,selectProjectExplorerfromtheleftnavigationpanel.TheProjectViewpageisdisplayed.
SelecttheprojecttowhichyouwanttoaddtheXQueryresource.
SelecttheprojecttowhichyouwanttoaddtheXQueryresource.
IntheProjectViewpage,selecttheXQueryresourcefromtheSelectResourceTypedropdownlist.TheCreateXQuerypageisdisplayed.
IntheResourceNameeld,enterthenameoftheresource.Thisisamandatory.
IntheResourceDescriptioneld,providetheadescriptionfortheresource.Thisisoptional.
IntheXQueryeld,providethepathtotheXMLyouareusingasanXQueryresource.ClickonBrowsetolocatethele.Optionally,youcancopyand
pastetheXMLintheXQueryeld.Thisismandatory.
SavetheXQueryresource.
Activatethesession.
Inanactivesession,selectProjectExplorerfromtheleftnavigationpanel.TheProjectViewpageisdisplayed.
Selecttheprojecttowhichyouwanttoaddtheproxyservice.
IntheProjectViewpage,selecttheProxyServiceresourcefromtheSelectResourceTypedropdownlist.TheGeneralCongurationpageisdisplayed.
IntheServiceNameeldoftheGeneralCongurationpage,enterthenameoftheproxyservice.Thisismandatory.
Selectthetypeofservicebyclickingonthebu onadjacenttovarioustypesofservicesavailableunderServiceType.Formoreinformationonselecting
theservicetype,seeProxyServices:Actions(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyactions.html).
ClickFinish.OntheSummarypage,clickSavetosavetheproxyservice.
OntheProjectViewpage,clicktheEditMessageFlowiconagainstthenewlycreatedproxyserviceintheResourcetable.TheEditMessageFlowpageis
displayed.
Clickonthemessageowtoaddapipelinepairtothemessageow.
ClickonRequestPipelineiconselectAddStagefromthemenu.
ClickontheStage1icontoandselectEditStagefromthemenu.TheEditStageCongurationpageappears.
ClickAddActionicon.ChooseAddanActionitemfromthemenu.
ChoosetheAssignactionfromMessageProcessing.
ClickonExpression.TheXQueryExpressionEditorisdisplayed.
ClickonXQueryResources.ThebrowserdisplaysthepagewhereyoucanimporttheXQueryresource.ClickontheBrowsetolocatetheXQuery
resource.
ClickonValidatetovalidatetheimportedXQueryresource.
SavetheimportedXQueryresourceonsuccessfulvalidation.
OntheEditStageCongurationpage,enterthenameofthevariableintheeld.
ThisassignstheXQueryresourcetothisvariable.Thevariablenowcontainstheexternalizedroutingtable.
ClickontheAssignactionicontoaddanotherassignaction.
Note:
Todothisrepeatstep11(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1073907)tostep13
EnterthefollowingXquery:
<ctx:route>
<ctx:serviceisProxy=false>{$routingtable/row[logical/text()=$logicalidentier]/physical/text()}
</ctx:service>
</ctx:route>
Intheabovecode,replace$logicalidentierbytheactualXPathtoextractthelogicalidentierfromthemessage(examplefrom$body).
ClickonValidatetovalidatetheXquery.
SavetheXqueryonsuccessfulvalidation.
OntheEditStageCongurationpage,enterthenameofthevariable(forexample,routeresult)intheeld.
ThisextractstheXMLusedbythedynamicrouteactionintothisvariable.
Clickonthemessageowtoaddaroutenodetotheendofthemessageow.
ClickontheRouteNodeiconandselectEditfromthemenu.
ClicktheAddActionicon.ChooseAddanActionitemfromthemenu.
ChoosetheDynamicRouteaction.
ClickonExpression.TheXQueryExpressionEditorisdisplayed.
Enterthevariablefromstep22(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1093903)(for
example,$routeresult)
OracleServiceBusprovidesreadaccesstodatabasesfromproxyserviceswithoutrequiringyoutowriteacustomEJBorcustomJavacodeandwithout
theneedforaseparatedatabaseproductlikeOraclceDataServiceIntegrator.Youcanusetheexecutesql()functiontomakeasimpleJDBCcalltoa
databasetoperformsimpledatabasereads.AnySQLqueryislegal,fromaquerythatgetsasingletaxrateforthesuppliedlocationtoaquerythatdoesa
complexjointoobtainanorderscurrentstatusfromseveralunderlyingdatabasetables.
Adatabasequerycanbeusedtogetdataformessageenrichment,forroutingdecisions,orforcustomizingthebehaviorofaproxyservice.Takefor
exampleascenarioinwhichanOracleServiceBusproxyservicereceivesrequestforquotemessages.Theproxyservicecanroutetherequestsbasedon
thecustomersprioritytooneofanumberofquotationbusinessservices(say,standard,gold,orplatinumlevelservices).Theproxyservicecanthen
performaSQLbasedaugmentationoftheresultsthatthoseservicesreturnforexample,basedontheselectedshipmethodandtheweightoftheorder,
theshippingcostcanbelookedupandthatcostaddedtotherequestforquotemessage.
fnbea:executesql()(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/xquery.html#wp1101465)describesthesyntaxforthe
functionandprovidesexamplesofitsuse.Theexecutesql()functionreturnstypeddataandautomaticallytranslatesvaluesbetweenSQL/JDBCand
XQuerydatamodels.
YoucanstorethereturnedelementinauserdenedvariableinanOracleServiceBusmessageow.
ThefollowingdatabasesandJDBCdriversaresupportedusingtheexecutesql()function:
IBMDB2/NT8
MicrosoftSQLServer2000,2005
Oracle8.1.x
Oracle9.x,10.x
Pointbase4.4,5.x
Sybase12.5.2and12.5.3
WebLogicType4JDBCdrivers
ThirdpartydriverssupportedbyWebLogicServer
UsenonXAdriversfordatasourcesyouusewiththefnbea:executesql()
UsenonXAdriversfordatasourcesyouusewiththefnbea:executesql()
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/xquery.html#wp1101465)functionthefunctionsupportsreadonlyaccessto
thedatasources.
WARNING:
InadditiontospecifyinganonXAJDBCdriverclasstousetoconnecttothedatabase,youmustensurethatyoudisableglobaltransactionsandtwo
phasecommit.(GlobaltransactionsareenabledbydefaultintheWebLogicServerconsoleforJDBCdatasources.)Thesespecicationscanbemadefor
yourdatasourceviatheWebLogicServerAdministrationConsole.SeeCreateJDBCDataSources
(h p://download.oracle.com/docs/cd/E12840_01/wls/docs103/ConsoleHelp/taskhelp/jdbc/jdbc_datasources/CreateDataSources.html)intheWebLogic
ServerAdministrationConsoleOnlineHelp.
ForcompleteinformationaboutdatabaseandJDBCdriverssupportinOracleServiceBus,seeSupportedDatabaseCongurations
(h p://edocs.bea.com/platform/suppcongs/congs_al10gr3/osb10gr3/supported_db.html)inSupportedCongurationsforOracleServiceBus.
Databasesotherthanthecoresetdescribedintheprecedinglistingarealsosupported.However,forthecoredatabaseslistedabove,theXQueryengine
doesabe errecognitionandmappingofdatatypestoXQuerytypesthanitdoesforthenoncoredatabasesinsomecases,acoredatabases
proprietaryJDBCextensionsareusedwhenfetchingdata.Forthenoncoredatabases,theXQueryenginereliestotallyonthestandardtypecodes
providedbytheJDBCdriverandstandardJDBCresultsetaccessmethods.
Whendesigningyourproxyservice,youcanenterXQueriesinlineaspartofanactiondenitioninsteadofenteringthemasresources.Youcanalsouse
inlineXQueriesforconditionsinIfThenactionsinmessageows.ForinformationaboutusingtheinlineXQueryeditor,seeCreatingVariable
StructureMappings(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1096693).
ThemessagecontextisasetofvariablesthatholdmessagecontextandinformationaboutmessagesastheyareroutedthroughtheOracleServiceBus.
Together,theheader,body,anda achmentsvariables,(referencedas$header,$bodyand$a achmentsinXQuerystatements)representthemessageasit
owsthroughOracleServiceBus.ThecanonicalformofthemessageisSOAP.EveniftheservicetypeisnotSOAP,themessageappearsasSOAPinthe
OracleServiceBusmessagecontext.
InaMessageContext,$headercontainsaSOAPheaderelementand$bodycontainsaSOAPBodyelement.TheHeaderandBodyelementsarequalied
bytheSOAP1.1orSOAP1.2namespacedependingontheservicetypeoftheproxyservice.AlsoinaMessageContext,$a achmentscontainsawrapper
elementcalleda achmentswithonechilda achmentelementpera achment.Thea achmentelementhasabodyelementwiththeactuala achment.
Whenamessageisreceivedbyaproxyservice,themessagecontentsareusedtoinitializetheheader,body,anda achmentsvariables.ForSOAP
services,theHeaderandBodyelementsaretakendirectlyfromtheenvelopeofthereceivedSOAPmessageandassignedto$headerand$body
respectively.FornonSOAPservices,theentirecontentofthemessageistypicallywrappedinaBodyelement(qualiedbytheSOAP1.1namespace)and
assignedto$body,andanemptyHeaderelement(qualiedbytheSOAP1.1namespace)isassignedto$header.
BinaryandMFLmessagesareinitializeddierently.ForMFLmessages,theequivalentXMLdocumentisinsertedintotheBodyelementthatisassigned
to$body.Forbinarymessages,themessagedataisstoredinternallyandapieceofreferenceXMLisinsertedintotheBodyelementthatisassignedto
$body.ThereferenceXMLlookslike<binarycontentref=/>,wherecontainsauniqueidentierassignedbytheproxyservice.
ThemessagecontextisdenedbyanXMLschema.YoumustuseXQueryexpressionstomanipulatethecontextvariablesinthemessageowthat
denesaproxyservice.
ThepredenedcontextvariablesprovidedbyOracleServiceBuscanbegroupedintothefollowingtypes:
Messagerelatedvariables
Inboundandoutboundvariables
Operationvariable
Faultvariable
Forinformationaboutthepredenedcontextvariables,seePredenedContextVariables
The$bodycontainsmessagepayloadvariable.WhenamessageisdispatchedfromOracleServiceBusyoucandecidethevariables,whoseyouwantto
includeintheoutgoingmessage.ThatdeterminationisdependentuponwhetherthetargetendpointisexpectingaSOAPoranonSOAPmessage:
Forabinary,anytextorXMLmessagecontentinsidetheBodyelementin$bodyissent.
ForMFLmessages,theBodyelementin$bodycontainstheXMLequivalentoftheMFLdocument.
Fortextmessages,theBodyelementin$bodycontainsthetext.Fortexta achments,thebodyelementin$a achmentscontainsthetext.Ifthecontents
areXMLinsteadofsimpletext,theXMLissentasatextmessage.
ForXMLmessages,theBodyelementin$bodycontainstheXML.ForXMLa achments,thebodyelementin$a achmentscontainstheXML.
SOAPmessagesareconstructedbywrappingthecontentsoftheheaderandbodyvariablesinsidea<soap:Envelope>element.(TheSOAP1.1namespace
isusedforSOAP1.1services,whiletheSOAP1.2namespaceisusedforSOAP1.2services.)IfthebodyvariablecontainsapieceofreferenceXML,itis
sent.Thatisthereferencedcontentisnotsubstitutedinthemessage.
FornonSOAPservices,iftheBodyelementof$bodycontainsabinarycontentelement,thenthereferencedcontentstoredinternallyissentasis,
regardlessofthetargetservicetype.
Formoreinformation,seeMessageContext(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html).
Thetypesforthemessagecontextvariablesaredenedbythemessagecontextschema(MessageContext.xsd).Whenworkingwiththemessagecontext
variablesintheOracleXQueryMapper,youneedtoreferenceMessageContext.xsd,whichisavailableinaJARle,ORACLE_HOME/osb_10.3/lib/sb
schemas.jar,andthetransportspecicschemas,whichareavailableat
ORACLE_HOME/osb_10.3/lib/transports/
whereORACLE_HOMErepresentsthedirectoryinwhichyouinstalledOracleServiceBus.
Tolearnaboutthemessagecontextschemaandthetransportspecicschemas,seeMessageContextSchema
Considerthefollowingguidelineswhenyouwanttoinspectoralterthemessagecontext:
InanXQueryexpression,therootelementinavariableisnotpresentinthepathinareferencetoanelementinthatvariable.Forexample,thefollowing
XQueryexpressionobtainstheContentDescriptionofthersta achmentinamessage:
$a achments/ctx:a achment[1]/ctx:contentDescription
Toobtaintheseconda achment
$a achments/ctx:a achment[2]/ctx:body/*
AcontextvariablecanbeemptyoritcancontainasingleXMLelementorastringvalue.However,anXQueryexpressionoftenreturnsasequence.When
youuseanXQueryexpressiontoassignavaluetoavariable,onlytherstelementinthesequencereturnedbytheexpressionisstoredasthevariable
value.Forexample,ifyouwanttoassignthevalueofaWSAddressingMessageIDfromaSOAPheader(assumingthereisoneintheheader)toa
variablenamedidvar,theassignactionspecicationis:
assigndata($header/wsa:messageIDtovariableidvar
Note:
Inthiscase,iftwoWSAddressingMessageIDheadersexist,theidvarvariablewillbeassignedthevalueoftherstone.
Inthiscase,iftwoWSAddressingMessageIDheadersexist,theidvarvariablewillbeassignedthevalueoftherstone.
Thevariables$header,$body,and$a achmentsareneverempty.However,$headercancontainanemptySOAPHeaderelement,$bodycancontainan
emptySOAPBodyelement,and$a achmentscancontainanemptya achmentelement.
Incasesinwhichyouuseatransformationresource(XSLTorXQuery),thetransformationresourceisdenedtotransformthedocumentintheSOAP
bodyofamessage.Tomakethistransformationcaseeasyandecient,theinputparametertothetransformationcanbeanXQueryexpression.For
example,youcanusethefollowingXQueryexpressiontofeedthebusinessdocumentintheBodyelementofamessage($body)asinputtoa
transformation:
$body/*[1]
Theresultofthetransformationcanbeputbackin$bodywithareplaceaction.Thatisreplacethecontentof$body,whichisthecontentoftheBody
element.Formoreinformation,seeXQueryTransformations
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/xquerytransforms.html)andXSLTransformations
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/xsl ransforms.html)inUsingtheOracleServiceBusConsole.
Inadditiontoinsertingorreplacingasingleelement,youcanalsoinsertorreplaceaselectedsequenceofelementsusinganinsertorreplaceaction.You
cancongureanXQueryexpressiontoreturnasequenceofelements.Forexample,youcanuseinsertandreplaceactionstocopyasetoftransport
headersfrom$inboundto$outbound.Forinformationonaddinganaction,seeAddinganActioninProxyServices:Actions
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyactions.html)inUsingtheOracleServiceBusConsole.Foranexample,see
CopyingJMSPropertiesFromInboundtoOutbound
CopyingJMSPropertiesFromInboundtoOutbound
Itisassumedthattheinterfacesoftheproxyservicesandoftheinvokedbusinessservicemaybedierent.Therefore,OracleServiceBusdoesnot
propagateanyinformation(suchasthetransportheadersandJMSproperties)fromtheinboundvariabletotheoutboundvariable.
Thetransportheadersfortheproxyservicesrequestandresponsemessagesarein$inboundandthetransportheadersfortheinvokedbusinessservices
requestandresponsearein$outbound.
Forexample,thefollowingXQueryexpressioncanbeusedinacasewheretheuserdenedJMSpropertiesforaonewaymessage(aninvocationwithno
response)needtobecopiedfrominboundmessagetooutboundmessage:
Usethetransportheadersactiontoset
$inbound/ctx:transport/ctx:request/tp:headers/tp:userheader
astherstchildof:
./ctx:transport/ctx:request/tp:headers
intheoutboundvariable.
Tolearnhowtocongurethetransportheaderaction,see:
TransportHeadersinProxyServices:Actions(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyactions.html)inUsing
theOracleServiceBusConsole.
WorkingwithVariableStructures
Thefollowingsectionsdescribe
UsingtheInlineXQueryExpressionEditor
UsingVariableStructures(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1137136)
CreatingVariableStructureMappings
OracleServiceBusallowsyoutoimportXQueriesthathavebeencreatedwithanexternaltoolsuchastheOracleXQueryMapper.Youcanusethese
XQueriesanywhereintheproxyservicemessageowbybindingtheXQueryresourceinputtoanInlineXQuery,andbindingtheXQueryresource
outputtoanactionthatusestheresultastheinput;forexample,theassign,replace,orinsertactions.
However,youcanentertheXQueryinlineaspartoftheactiondenitioninsteadofenteringtheXQueryasaresource.YoucanalsouseInlineXQueries
fortheconditioninanIfThenaction.
UsetheInlineXQueryExpressionEditortoentersimpleXQueriesthatconsistofthefollowing:
FragmentsofXMLwithembeddedXQueries.
Simplevariablepathsalongthechildaxis.
Note:
FormorecomplexXQueries,itisrecommendedthatyouusetheXQueryMapper,especiallyifyouarenotfamiliarwithXQuery.
InlineXQueriescanbeusedeectivelyto:
CreatevariablestructuresbyusingtheInlineXQueryExpressionEditor.SeeUsingVariableStructures
ExtractoraccessabusinessdocumentorRPCparameterfromtheSOAPenvelopeelementsin$headeror$body.
Extractoraccessana achmentdocumentin$a achments.
SetuptheparametersofaservicecalloutactionbyextractingitfromtheSOAPenvelope.
InserttheresultparameterofaservicecalloutactionintotheSOAPenvelope.
ExtractasequencefromtheSOAPenvelopetodriveaforloop.
UpdateaniteminthesequenceinaforloopwithanUpdateaction.
Note:
YoucanalsousetheInlineXQueryExpressionEditortocreatevariablestructures.Formoreinformation,seeUsingVariableStructures
OracleServiceBusallowsyoutoimportXQueriesthathavebeencreatedwithanexternaltoolsuchastheOracleXQueryMapper.Youcanusethese
XQueriesanywhereintheproxyservicemessageowbybindingtheXQueryresourceinputtoaninlineXQuery,andbindingtheXQueryresource
outputtoanactionthatusestheresultastheactioninput;forexample,theassign,replace,orinsertactions.However,youcanentertheXQueryinlineas
partoftheactiondenitioninsteadofenteringtheXQueryasaresource.YoucanalsouseinlineXQueriesfortheconditioninanIfThenaction.
TheinlineXQueryandXPatheditorsallowyoutodeclareavariablesstructurebymappingittoatypeorelementandthencreatingpathexpressions
withadraganddropactionfromthegraphicalrepresentationofthestructure.Youcanalsoenterthepathexpressionsmanually.
Youcanusethisfeaturedirectlyforalluserdenedvariables,aswellas$inbound,$outbound,and$fault.However,youcannotuseitdirectlytoaccess
XMLa achmentsin$a achments,headersin$header,ordocumentsandRPCparametersin$body,withoneexceptionyoucanuseitdirectlytoaccess
documentsandparametersin$bodyforrequestmessagesreceivedbyaWSDLproxyservice.
Tolearnmoreaboutcreatingvariablestructures,seeCreatingVariableStructureMappings
TolearnmoreaboutXQueryenginesupportandtherelationshipwiththeOracleDataServiceIntegratorfunctionsandoperators,seeXQuery
TolearnmoreaboutXQueryenginesupportandtherelationshipwiththeOracleDataServiceIntegratorfunctionsandoperators,seeXQuery
Implementation(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/xquery.html).
YoutypicallyusetheInlineXQueryExpressionEditortoentersimpleXQueriesthatconsistofthefollowing:
FragmentsofXMLwithembeddedXQueries.
Simplevariablepathsalongthechildaxis.
Note:
FormorecomplexXQueries,werecommendthatyouusetheOracleXQueryMapper,aneditorwithdraganddropfunctionality.SeeTransformingData
UsingtheXQueryMapper(h p://download.oracle.com/docs/cd/E13160_01/wli/docs10gr3/dtguide/index.html)inTransformingDataUsingtheXQuery
Mapper.
ExamplesofgoodusesofinlineXQueriesare:
ExtractoraccessabusinessdocumentorRPCparameterfromtheSOAPenvelopeelementsin$headeror$body.
Extractoraccessana achmentdocumentin$a achments.
SetuptheparametersofaservicecalloutbyextractingitfromtheSOAPenvelope.
FoldtheresultparameterofaservicecalloutintotheSOAPenvelope.
ExtractasequencefromtheSOAPenvelopetodriveaforloop.
UpdateaniteminthesequenceinaforloopwithanUpdateaction.
YoucanalsousetheInlineXQueryExpressionEditortocreatevariablestructures.Formoreinformation,seeUsingVariableStructures
YoucanusetheInlineXQueryExpressionEditortocreatevariablestructures,withwhichyoudenethestructureofagivenvariablefordesign
purposes.Forexample,itiseasiertobrowsetheXPathvariableintheconsoleratherthanviewingtheXMLschemaoftheXPathvariable.
Note:
Itisnotnecessarytocreatevariablestructuresforyourruntimetowork.Variablestructuresdenethestructureofthevariableorthevariablepathbutdo
notcreatethevariable.Variablesarecreatedatruntimeasthetargetoftheassignactioninthestage.
Inatypicalprogramminglanguage,thescopeofvariablesisstatic.Theirnamesandtypesareexplicitlydeclared.Thevariablecanbeaccessedanywhere
withinthestaticscope.
InOracleServiceBus,therearesomepredenedvariables,butyoucanalsodynamicallycreatevariablesandassignvaluetothemusingtheassignaction
orusingtheloopvariableintheforloop.Whenavalueisassignedtoavariable,thevariablecanbeaccessedanywhereintheproxyservicemessage
ow.Thevariabletypeisnotdeclaredbutthetypeisessentiallytheunderlyingtypeofthevalueitcontainsatanypointintime.
Note:
Thescopeoftheforloopvariableislimitedandcannotbeaccessedoutsidethestage.
WhenyouusetheInlineXQueryExpressionEditor,theXQueryhaszeroormoreinputsandoneoutput.Becauseyoucandisplaythestructureofthe
inputsandthestructureoftheoutputvisuallyintheExpressionEditoritself,youdonotneedtoopentheXMLschemaorWSDLresourcestoseetheir
structurewhenyoucreatetheInlineXQuery.Thegraphicalstructuredisplayalsoenablesyoutodraganddropsimplevariablepathsalongthechildaxis
withoutpredicates,intothecomposedXQuery.
Eachvariablestructuremappingentryhasalabelandmapsavariableorvariablepathtooneormorestructures.Thescopeofthesemappingsisthe
stageorroutenode.Becausevariablesarenotstaticallytyped,avariablecanhavedierentstructuresatdierentpoints(oratthesamepoint)inthestage
orroutenode.Therefore,youcanmapavariableoravariablepathtomultiplestructures,eachwithadierentlabel.Toviewthestructure,selectthe
correspondinglabelwithadropdownlist.
Note:
YoucanalsocreatevariablestructuremappingsintheInlineXPathExpressionEditor.However,althoughthevariableoravariablepathismappedtoa
structure,theXPathsgeneratedwhenyouselectfromthestructureareXPathsrelativetothevariable.AnexampleofarelativeXPathis
./ctx:a achment/ctx:body.
Thefollowingsectionsdescribehowtocreateseveraltypesofvariablestructuremappings:
SampleWSDL(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1055812)
CreatingtheResourcesYouNeedfortheExamples
Example1:SelectingaPredenedVariableStructure
Example2:CreatingaVariableStructureThatMapsaVariabletoaType
Example3:CreatingaVariableStructurethatMapsaVariabletoanElement
Example4:CreatingaVariableStructureThatMapsaVariabletoaChildElement
Example5:CreatingaVariableStructurethatMapsaVariabletoaBusinessService
Example6:CreatingaVariableStructureThatMapsaChildElementtoAnotherChildElement
8.30.CreatingandConfiguringtheProxyServicetoImplementDynamicRouting
8.31.AccessingDatabasesUsingXQuery
8.32.UnderstandingMessageContext
8.33.MessageContextComponents
8.34.GuidelinesforViewingandAlteringMessageContext
8.35.UsingtheInlineXQueryExpressionEditor
8.36.InlineXQueries
8.37.UsesoftheInlineXQueryExpressionEditor
8.38.UsingVariableStructures
8.39.CreatingVariableStructureMappings
8.39.1.SampleWSDL
ThissampleWSDLisusedinmostoftheexamplesinthissection.YouneedtosavethisWSDLasaresourceinyourconguration.Formoreinformation,see
CreatingtheResourcesYouNeedfortheExamples
Listing317SampleWSDL
<denitions
name=samplewsdl
targetNamespace=h p://example.org&#8221(h p://example.org&#8221);
xmlns=h p://schemas.xmlsoap.org/wsdl/&#8221(h p://schemas.xmlsoap.org/wsdl/&#8221);
xmlns:s0=h p://www.oracle.com&#8221(h p://www.oracle.com&#8221);
xmlns:s1=h p://example.org&#8221(h p://example.org&#8221);
xmlns:soap=h p://schemas.xmlsoap.org/wsdl/soap/&gt(h p://schemas.xmlsoap.org/wsdl/soap/&gt);
<types>
<xs:schema
a ributeFormDefault=unqualied
elementFormDefault=qualied
elementFormDefault=qualied
targetNamespace=h p://www.oracle.com&#8221(h p://www.oracle.com&#8221);
xmlns:xs=h p://www.w3.org/2001/XMLSchema&gt(h p://www.w3.org/2001/XMLSchema&gt);
<xs:elementname=POtype=s0:POType/>
<xs:complexTypename=POType>
<xs:all>
<xs:elementname=idtype=xs:string/>
<xs:elementname=nametype=xs:string/>
</xs:all>
</xs:complexType>
<xs:elementname=Invoicetype=s0:InvoiceType/>
<xs:complexTypename=InvoiceType>
<xs:all>
<xs:elementname=idtype=xs:string/>
<xs:elementname=nametype=xs:string/>
</xs:all>
</xs:complexType>
</xs:schema>
</types>
<messagename=POTypeMsg>
<partname=POtype=s0:POType/>
</message>
<messagename=InvoiceTypeMsg>
<partname=InvReturntype=s0:InvoiceType/>
</message>
<portTypename=POPortType>
<operationname=GetInvoiceType>
<inputmessage=s1:POTypeMsg/>
<outputmessage=s1:InvoiceTypeMsg/>
</operation>
</portType>
<bindingname=POBindingtype=s1:POPortType>
<soap:bindingstyle=rpctransport=h p://schemas.xmlsoap.org/soap/h p/&gt(h p://schemas.xmlsoap.org/soap/h p/&gt);
<operationname=GetInvoiceType>
<soap:operationsoapAction=h p://example.com/GetInvoiceType/&gt(h p://example.com/GetInvoiceType/&gt);
<input>
</input>
<output>
</output>
</operation>
</binding>
</denitions>
8.40.CreatingtheResourcesYouNeedfortheExamples
Tomakeuseoftheexamplesthatfollow,yousavethesampleWSDLasaresourceinyourcongurationandcreatethesamplebusinessserviceandproxy
servicethatusethesampleWSDL.
TheinstructionsthatfollowtellhowtoaccomplishthetasksintheOracleServiceBusConsole:
SavetheWSDLasaResource(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1057308)
CreateaProxyServiceThatUsestheSampleWSDL
BuildaMessageFlowfortheSampleProxyService
CreateaBusinessServiceThatUsestheSampleWSDL
8.41.SavetheWSDLasaResource
1.IntheleftnavigationpaneintheOracleServiceBusConsole,underChangeCenter,clickCreatetocreateanewsessionformakingchangestothecurrent
conguration.
2.Intheleftnavigationpane,clickProjectExplorer.
3.IntheProjectViewpage,clicktheprojecttowhichyouwanttoaddtheWSDL.
3.IntheProjectViewpage,clicktheprojecttowhichyouwanttoaddtheWSDL.
4.IntheProjectViewpage,intheCreateResourceeld,selectWSDLunderInterface.
5.IntheCreateaNewWSDLResourcepageintheResourceNameeld,enterSampleWSDL.Thisisarequiredeld.
6.IntheWSDLeld,copyandpastethetextfromthesampleWSDLintothiseld.
Note: Thisisarequiredeld.
1.ClickSave.ThenewWSDLSampleWSDLisincludedinthelistofresourcesandsavedinthecurrentsession.Youmustnowcreateaproxyservicethat
usesthisWSDL,seeCreateaProxyServiceThatUsestheSampleWSDL
2.Intheleftnavigationpane,clickProjectExplorer.
3.IntheProjectViewpage,selecttheprojecttowhichyouwanttoaddtheproxyservice.
4.IntheProjectViewpage,intheCreateResourceeld,selectProxyServiceunderService.
5.IntheEditaProxyServiceGeneralCongurationpage,intheServiceNameeld,enterProxywithSampleWSDL.Thisisarequiredeld.
6.IntheServiceTypeeld,whichdenesthetypesandpackagingofthemessagesexchangedbytheservice:
1.SelectWSDLWebServicefromunderCreateaNewService.
2.ClickBrowse.TheWSDLBrowserisdisplayed.
3.SelectSampleWSDL,thenselectPOBindingintheSelectWSDLDenitionspane.
4.ClickSubmit.
5.KeepthedefaultvaluesforallothereldsontheGeneralCongurationpage,thenclickNext.
6.KeepthedefaultvaluesforalleldsontheTransportCongurationpages,thenclickNext.
7.IntheOperationSelectionCongurationpage,makesureSOAPBodyTypeisselectedintheSelectionAlgorithmeld,thenclickNext.
8.Reviewthecongurationdatathatyouhaveenteredforthisproxyservice,thenclickSave.ThenewproxyserviceProxywithSampleWSDLis
includedinthelistofresourcesandsavedinthecurrentsession.Tobuildmessageowforthisproxyservice,seeBuildaMessageFlowforthe
SampleProxyService(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1059091).
9.IntheProjectViewpage,intheActionscolumn,clicktheEditMessageFlowiconfortheProxywithSampleWSDLproxyservice.
10.IntheEditMessageFlowpage,clicktheProxywithSampleWSDLicon,thenclickAddPipelinePair.PipelinePairNode1isdisplayed,whichincludes
requestandresponsepipelines.
11.ClicktheRequestPipelineicon,thenclickAddStage.TheStageStage1isdisplayed.
12.ClickSave.ThebasicmessageowiscreatedfortheProxywithSampleWSDLproxyservice.
13.Intheleftnavigationpane,clickProjectExplorer.TheProjectViewpageisdisplayed.
14.Selecttheprojecttowhichyouwanttoaddthebusinessservice.
15.FromtheProjectViewpage,intheCreateResourceeld,selectBusinessServicefromunderService.TheEditaBusinessServiceGeneral
Congurationpageisdisplayed.
16.IntheServiceNameeld,enterBusinesswithSampleWSDL.Thisisarequiredeld.
17.IntheServiceTypeeld,whichdenesthetypesandpackagingofthemessagesexchangedbytheservice,dothefollowing:
1.SelectWSDLWebServicefromunderCreateaNewService.
3.SelectSampleWSDL,thenselectPOBindingintheSelectWSDLDenitionspane.
4.ClickSubmit.
5.KeepthedefaultvaluesforallothereldsontheGeneralCongurationpage,thenclickNext.
6.EnteranendpointURIintheEndpointURIeldontheTransportCongurationpage.
ClickAdd,andthenclickNext.
7.UsethedefaultvaluesforalleldsontheSOAPBindingCongurationpage.
ClickNext.
8.Reviewthecongurationdatathatyouhaveenteredforthisbusinessservice,andthenclickSave.Thenewbusinessservice
BusinesswithSampleWSDLisincludedinthelistofresourcesandissavedinthecurrentsession.
9.Fromtheleftnavigationpane,clickActivateunderChangeCenter.Thesessionendsandthecongurationisdeployedtoruntime.Youarenow
readytousetheexamplescontinueinExample1:SelectingaPredenedVariableStructure
8.42.CreateaProxyServiceThatUsestheSampleWSDL
8.43.BuildaMessageFlowfortheSampleProxyService
8.44.CreateaBusinessServiceThatUsestheSampleWSDL
8.45.Example1:SelectingaPredefinedVariableStructure
Inthisexample,youselectapredenedvariablestructureusingtheproxyserviceProxyWithSampleWSDL,whichhasaservicetypeWSDLWebServicethat
usesthebindingPOBindingfromSampleWSDL.
Theproxyservicemessageowneedstoknowthestructureofthemessageinordertomanipulateit.Toachievethis,OracleServiceBusautomatically
providesapredenedstructurethatmapsthebodyvariabletotheSOAPbodystructureasdenedbytheWSDLoftheproxyserviceforallthemessagesin
theinterface.Thispredenedstructuremappingislabeledbody.
Note: Thispredenedstructureisalsosupportedformessagingserviceswithatypedinterface.
Toselectapredenedvariablestructure:
IntheVariableStructurespanelontheXQueryExpressionEditorpage,selectbodyfromthedropdownlistofbuiltinstructures.
ThevariablestructurebodyisdisplayedinFigure34
Figure34VariableStructuresbody
8.46.Example2:CreatingaVariableStructureThatMapsaVariabletoaType
SupposetheproxyserviceProxyWithSampleWSDLinvokesaservicecallouttothebusinessserviceBusinessWithSampleWSDL,whichalsohasaservice
typeWSDLWebServicethatusesthebindingPOBindingfromSampleWSDL.TheoperationGetInvoiceTypeisinvoked.
Inthisexample,themessageowneedstoknowthestructureoftheresponseparameterinordertomanipulateit.Toachievethis,youcancreateanew
variablestructurethatmapstheresponseparametervariabletothetypeInvoiceType.
Tomapavariabletoatype:
1.IntheVariableStructurespanel,clickAddNewStructure.AdditionaleldsaredisplayedinFigure35
Figure35VariableStructuresAddaNewStructure
1.SelecttheXMLType.
2.IntheStructureLabeleld,enterInvoiceTypeasthedisplaynameforthevariablestructureyouwanttocreate.Thisdisplaynameenablesyoutogivea
meaningfulnametothestructuresoyoucanrecognizeitatdesigntimebutithasnoimpactatruntime.
3.IntheStructurePatheld,enter$InvoiceTypeasthepathofthevariableatruntime.
4.ToselectthetypeInvoiceType,dothefollowing:
1.UndertheTypeeld,selecttheappropriateradiobu on,thenselectWSDLTypefromthedropdownlist.
3.IntheWSDLBrowser,selectSampleWSDL,thenselectInvoiceTypeunderTypesintheSelectWSDLDenitionspane.
4.ClickSubmit.InvoiceTypeisdisplayedunderyourselectionWSDLType.
5.ClickAdd.ThenewvariablestructureInvoiceTypeisincludedunderXMLTypeinthedropdownlistofvariablestructures.
ThevariablestructureInvoiceTypeisdisplayedinFigure36
Figure36VariableStructuresInvoiceType
8.47.Example3:CreatingaVariableStructurethatMapsaVariabletoanElement
SupposeatemporaryvariablehastheelementInvoicedescribedintheSampleWSDLWSDL.Inthisexample,theProxyWithSampleWSDLmessageow
needstoaccessthisvariable.Toachievethis,youcancreateanewvariablestructurethatmapsthevariabletotheelementInvoice.
Tomapavariabletoanelement:
1.IntheVariableStructurespanel,clickAddNewStructure.
2.MakesureyouselecttheXMLType.
3.IntheStructureLabeleld,enterInvoiceasthemeaningfuldisplaynameforthevariablestructureyouwanttocreate.
4.IntheStructurePatheld,enter$Invoiceasthepathofthevariablestructureatruntime.
5.ToselecttheelementInvoice,dothefollowing:
1.FortheTypeeld,makesureyouselecttheappropriateradiobu on.ThenselectWSDLElementfromthedropdownlist.
2.ClickBrowse.
3.IntheWSDLBrowser,selectSampleWSDL,thenselectInvoiceunderElementsintheSelectWSDLDenitionspane.
3.IntheWSDLBrowser,selectSampleWSDL,thenselectInvoiceunderElementsintheSelectWSDLDenitionspane.
4.ClickSubmit.InvoiceisdisplayedunderyourselectionWSDLElement.
5.ClickAdd.ThenewvariablestructureInvoiceisincludedunderXMLTypeinthedropdownlistofvariablestructures.
ThevariablestructureInvoiceisdisplayedinFigure37
Figure37VariableStructuresInvoice
8.48.Example4:CreatingaVariableStructureThatMapsaVariable
toaChildElement
TheProxyWithSampleWSDLproxyserviceroutestothedocumentstyleAnySOAPbusinessservicethatreturnsthePurchaseOrderintheSOAPbody.In
thisexample,theProxyWithSampleWSDLproxyservicemessageowmustthenmanipulatetheresponse.Toachievethis,youcancreateanewstructure
thatmapsthebodyvariabletothePOelement,andspecifythePOelementasachildelementofthevariable.Youneedtospecifyitasachildelement
becausethebodyvariablecontainstheSOAPBodyelementandthePOelementisachildoftheBodyelement.
Tomapavariabletoachildelement:
2.MakesureyouselecttheXMLType.
3.IntheStructureLabeleld,enterbodytoPOasthemeaningfuldisplaynameforthevariablestructureyouwanttocreate.
4.IntheStructurePatheld,enter$bodyasthepathofthevariablestructureatruntime.
5.ToselectthePOelement:
1.UndertheTypeeld,makesureyouselecttheappropriateradiobu on,andthenselectWSDLElementfromthedropdownlist.
2.ClickBrowse.
3.IntheWSDLBrowser,selectSampleWSDL,thenselectPOunderElementsintheSelectWSDLDenitionspane.
4.ClickSubmit.
5.SelecttheSetaschildcheckboxtosetthePOelementasachildofthebodytoPOvariablestructure.
6.ClickAdd.ThenewvariablestructurebodytoPOisincludedunderXMLTypeinthedropdownlistofvariablestructures.
ThevariablestructurebodytoPOisdisplayedinFigure38
Figure38VariableStructuresbodytoPO
8.49.Example5:CreatingaVariableStructurethatMapsaVariable
toaBusinessService
TheProxyWithSampleWSDLproxyserviceroutesthemessagetotheBusinessWithSampleWSDLbusinessservice,whichalsohasaservicetypeWSDLWeb
ServicethatusesthebindingPOBindingfromSampleWSDL.Inthisexample,themessageowmustthenmanipulatetheresponse.Toachievethis,youcan
deneanewstructurethatmapsthebodyvariabletotheBusinessWithSampleWSDLbusinessservice.ThisresultsinamapofthebodyvariabletotheSOAP
bodyforallthemessagesintheWSDLinterfaceoftheservice.
Note: Thismappingisalsosupportedformessagingserviceswithatypedinterface.
Tomapavariabletoabusinessservice:
2.SelectServiceInterface.
3.IntheStructureLabeleld,enterBusinessServiceasthemeaningfuldisplaynameforthevariablestructure.
4.IntheStructurePatheld,$bodyisalreadysetasthedefault.Thisisthepathofthevariablestructureatruntime.
5.Toselectthebusinessservice,dothefollowing:
1.UndertheServiceeld,clickBrowse.TheServiceBrowserisdisplayed.
2.IntheServiceBrowser,selecttheBusinessWithSampleWSDLbusinessservice,thenclickSubmit.ThebusinessserviceisdisplayedundertheService
eld.
3.IntheOperationeld,selectAll.
4.ClickAdd.ThenewvariablestructureBusinessServiceisincludedunderServiceInterfaceinthedropdownlistofvariablestructures.
ThevariablestructureBusinessServiceisdisplayedinFigure39
Figure39VariableStructuresBusinessService

8.50.Example6:CreatingaVariableStructureThatMapsaChildElementtoAnother
ChildElement
ModifytheSampleWSDLsothattheProxyWithSampleWSDLproxyservicereceivesasinglea achment.Thea achmentisaPurchaseOrder.Inthis

example,theproxyservicemessageowmustthenmanipulatethePurchaseOrder.Toachievethis,youcandeneanewstructurethatmapsthebody
elementin$a achmentstothePOelement,whichisspeciedasachildelement.Thebodyelementisspeciedasavariablepathoftheform:
$a achments/ctx:a achment/ctx:body
Youcanselectandcopythebodyelementfromthepredeneda achmentsstructure,pastethiselementasthevariablepathtobemappedinthenew
mappingdenition.
Tomapachildelementtoanotherchildelement:
1.IntheVariableStructurespanel,selecta achmentsfromthedropdownlistofbuiltinstructures.
Thevariablestructurea achmentsisdisplayedinFigure310
Figure310VariableStructuresa achments
1.Selectthebodychildelementinthea achmentsstructure.ThevariablepathofthebodyelementisdisplayedinthePropertyInspectorontherightside
ofthepage:
1.Copythevariablepathofthebodyelement.
3.SelecttheXMLType.
4.IntheStructureLabeleld,enterPOa achmentasthemeaningfuldisplaynameforthisvariablestructure.
5.IntheStructurePatheld,pastethevariablepathofthebodyelement:
Thisisthepathofthevariablestructureatruntime.
1.ToselectthePOelement:
1.UndertheTypeeld,makesuretheappropriateradiobu onisselected,thenselectWSDLElement.
2.ClickBrowse.
3.IntheWSDLBrowser,selectSampleWSDL,thenselectPOunderElementsintheSelectWSDLDenitionspane.
4.ClickSubmit.
5.SelecttheSetaschildcheckboxtosetthePOelementasachildofthebodyelement.
6.ClickAdd.ThenewvariablestructurePOa achmentisincludedunderXMLTypeinthedropdownlistofvariablestructures.
7.Iftherearemultiplea achments,addanindextothereferencewhenyouuseeldsfromthisstructuredvariableinyourXQueries.Forexample,if
youdragthePOeldtotheXQueryeld,butasPOwillbetheseconda achment,changetheinsertedvaluefrom
$a achments/ctx:a achment/ctx:body/oracle:PO/oracle:id
to
$a achments/ctx:a achment[2]/ctx:body/oracle:PO/oracle:id
8.51.QualityofService
ThefollowingsectionsdiscussqualityofservicefeaturesinOracleServiceBusmessaging:
DeliveryGuarantees(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1065307)
OutboundMessageRetries(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1065437)
8.52.DeliveryGuarantees
OracleServiceBussupportsreliablemessaging.Whenmessagesareroutedtoanotherservicefromaroutenode,thedefaultqualityofservice(QoS)isexactly
onceiftheproxyservicetransportisdenedasJMS/XA;otherwisebesteortQoSissupported.
QualityofserviceissetinthequalityOfServiceelementinthe$outboundcontextvariable.
ThefollowingdeliveryguaranteetypesareprovidedinOracleServiceBus,showninTable39
Delivery Description
Reliability
Exactly Exactlyoncereliabilitymeansthatmessagesaredeliveredfrominboundtooutboundexactlyonce,assumingaterminatingerrordoesnot
once occurbeforetheoutboundmessagesendisinitiated.Exactlyoncemeansreliabilityisoptimized.
Exactlyoncedeliveryreliabilityisahint,notadirective.Whenexactlyonceisspecied,exactlyoncereliabilityisprovidedifpossible.Ifexactly
onceisnotpossible,thenatleastoncedeliverysemanticsarea empted;ifthatisnotpossible,besteortdeliveryisperformed.
ThedefaultvalueofthequalityOfServiceelementisexactlyonceforaroutenodeactionforthefollowinginboundtransports:
email
FTP
File
JMS/XA
SFTP
TransactionalTuxedo
Note: DonotretrytheoutboundtransportwhentheQoSisexactlyonce
Atleast Atleastoncesemanticsmeansthemessageisdeliveredtotheoutboundfromtheinboundatleastonce,assumingaterminatingerrordoesnot
once occurbeforetheoutboundmessagesendisinitiated.Deliveryisconsideredsatisedevenifthetargetservicerespondswithatransportlevel
error.Howeveritisnotsatisedinthecaseofatimeout,afailuretoconnect,orabrokencommunicationlink.IffailoverURLsarespecied,
atleastoncesemanticsisprovidedwithrespecttoatleastoneoftheURLs.
Atleastoncedeliverysemanticsisa emptedifexactlyonceisnotpossiblebutthequalityOfServiceelementisexactlyonce.
Besteort Besteortmeansthatthereisnoreliablemessagingandthereisnoeliminationofduplicatemessageshowever,performanceisoptimized.It
isperformedifthequalityOfServiceelementisbesteort.Besteortdeliveryisalsoperformedifexactlyonceandatleastoncedelivery
semanticsarenotpossiblebutthequalityOfServiceelementisexactlyonce.
ThedefaultvalueofthequalityOfServiceelementforaroutenodeisbesteortforthefollowinginboundtransports:
HTTP
JMS/nonXA
NonTransactionalTuxedo
ThedefaultvalueofthequalityOfServiceelementisalwaysbesteortforthefollowing:
Servicecalloutactionalwaysbesteort,butcanbechangedifrequired.
Publishactiondefaultstobesteort,modiable
Note: WhenthevalueofthequalityOfServiceelementisbesteortforapublishaction,allerrorsareignored.However,whenthevalue
ofthequalityOfServiceelementisbesteortforaroutenodeactionoraServicecalloutaction,anyerrorwillraiseanexception.
Formoredetailedinformationaboutqualityofserviceforothertransports,seethedocumentationforthetransport,atOracleServiceBusTransports
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/transports.html).
8.53.OverridingtheDefaultElementAttribute
Tooverridethedefaultexactlyoncequalityofservicea ribute,youmustsetthequalityOfServiceintheoutboundmessagecontextvariable($outbound).For
moreinformation,seeMessageContextSchema(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1060634).
YoucanoverridethedefaultqualityOfServiceelementa ributeforthefollowing:
Routenodeaction
Publishaction
Servicecallout
TooverridethequalityOfServiceelementa ribute,youmustusetherouteoptionsactiontorouteorpublish,andalsoselectthecheckboxforaservice
calloutaction.SeeMessageContextSchema(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1060634).
8.54.DeliveryGuaranteeRules
Thedeliveryguaranteesupportedwhenaproxyservicepublishesamessageorroutesarequesttoabusinessservicedependsonthefollowingconditions:
ThevalueofthequalityOfServiceelement.
Theinboundtransport(andconnectionfactory,ifapplicable).
Theoutboundtransport(andconnectionfactory,ifapplicable).
However,iftheinboundproxyserviceisaLocalTransportandisinvokedbyanotherproxyservice,theinboundtransportoftheinvokingproxyserviceis
responsibleforthedeliveryguarantee.Thatisbecauseaproxyservicethatinvokesanotherproxyserviceisoptimizedintoadirectinvocationifthetransport
oftheinvokedproxyserviceisaLocalTransport.Formoreinformationontransportprotocols,seeProxyServices
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyservices.html)andBusinessServices
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/businessServices.html)inUsingtheOracleServiceBusConsole.
Note: Nodeliveryguaranteeisprovidedforresponsesfromaproxyservice.
Thefollowingrulesgoverndeliveryguarantees,showninTable310
DeliveryGuarantee Rule
Provided
Exactlyonce TheproxyserviceinboundtransportistransactionalandthevalueofthequalityOfServiceelementisexactlyoncetoanoutbound
JMS/XAtransport.
Atleastonce Theproxyserviceinboundtransportisle,FTP,oremailandthevalueofthequalityOfServiceelementisexactlyonce.
Atleastonce TheproxyserviceinboundtransportistransactionalandthevalueofthequalityOfServiceelement,whereapplicable,isexactly
oncetoanoutboundtransportthatisnottransactional.
Nodelivery Allothercases,includingallresponseprocessingcases.
guarantee
Note: TosupportatleastonceandexactlyoncedeliveryguaranteeswithJMS,youmustexploitJMStransactionsandcongurearetrycountandretry
intervalontheJMSqueuetoensurethatthemessageisredeliveredintheeventofaservercrashorafailurethatisnothandledinanerrorhandler
withaReplyorResumeaction.File,FTP,andemailtransportsalsointernallyuseaJMS/XAqueue.Thedefaultretrycountforaproxyservice
withaJMS/XAtransportis1.ForalistofthedefaultJMSqueuescreatedbyOracleServiceBus,seetheOracleServiceBusDeploymentGuide
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/deploy/index.html).
Thefollowingareadditionaldeliveryguaranteerules:
IfthetransportoftheinboundproxyserviceisFile,FTP,email,TransactionalTuxedo,orJMS/XA,therequestprocessingisperformedinatransaction.
WhenthequalityOfServiceelementissettoexactlyonce,anyroutenodeandpublishactionsexecutedintherequestowtoatransactional
destinationareperformedinthesametransaction.
WhenthequalityOfServiceelementissettobesteortforanyactioninaroutenode,servicecalloutorpublishactionsareexecutedoutsideofthe
requestowtransaction.Specically,forJMS,Tuxedo,TransactionalTuxedo,orEJBtransport,therequestowtransactionissuspendedandthe
TransactionalTuxedoworkisdonewithoutatransactionorinaseparatetransactionthatisimmediatelycommi ed.
Ifanerroroccursduringrequestprocessing,butiscaughtbyausererrorhandlerthatmanagestheerror(byusingtheresumeorreplyaction),the
messageisconsideredsuccessfullyprocessedandthetransactioncommits.Atransactionisabortedifthesystemerrorhandlerreceivestheerrorthat
is,iftheerrorisnothandledbeforereachingthesystemlevel.Thetransactionisalsoabortedifaserverfailureoccursduringrequestpipeline
processing.
IfaresponseisreceivedbyaproxyservicethatusesaJMS/XAtransporttobusinessservice(andtheproxyinboundisnotTransactionalTuxedo),the
responseprocessingisperformedinasingletransaction.
WhenthequalityOfServiceelementissettoexactlyonce,allroute,servicecallout,andpublishactionsareperformedinthesametransaction.
WhenthequalityOfServiceelementissettobesteort,allpublishactionsandservicecalloutactionsareexecutedoutsideoftheresponseow
transaction.Specically,forJMS,EJB,ortransactionalTuxedotypesoftransports,theresponseowtransactionissuspendedandtheserviceisinvoked
withoutatransactionorinaseparatetransactionthatisimmediatelycommi ed.
ProxyserviceresponsesexecutedintheresponseowtoaJMS/XAdestinationarealwaysperformedinthesametransaction,regardlessofthe
qualityOfServiceelementse ing.
IftheproxyserviceinboundtransportistransactionalTuxedo,boththerequestprocessingandresponseprocessingaredoneinthistransaction.
Note: YouwillencounteraruntimeerrorwhentheinboundtransportistransactionalTuxedoandtheoutboundisanasynchronoustransport,for
example,JMS/XA.
8.55.ThreadingModel
TheOracleServiceBusthreadingmodelworksasfollows:
TheOracleServiceBusthreadingmodelworksasfollows:
Therequestandresponseowsinaproxyserviceexecuteindierentthreads.
Servicecalloutsarealwaysblocking.AnHTTProuteorpublishactionisnonblocking(forrequest/responseoronewayinvocation),ifthevalueofthe
qualityOfServiceelementisbesteort.
JMSrouteactionsorpublishactionsarealwaysnonblocking,buttheresponseislostiftheserverrestartsaftertherequestissentbecauseOracleService
Bushasnopersistentmessageprocessingstate.
Note: Inarequestorresponseowpublishaction,responsesarealwaysdiscardedbecausepublishactionsareinherentlyaonewaymessagesend.
8.56.SplittingProxyServices
Youmaywanttosplitaproxyserviceinthefollowingsituations:
WhenHTTPistheinboundandoutboundtransportforaproxyservice,youmaywanttoincorporateenhancedreliabilityintothemiddleofthemessage
ow.Toenableenhancedreliabilityinthisway,splittheproxyserviceintoafrontendHTTPproxyserviceandabackendJMS(onewayor
request/response)proxyservicewithanHTTPoutboundtransport.Intheeventofafailure,therstproxyservicemustquicklyplacethemessageinthe
queueforthesecondproxyservice,inordertoavoidlossofmessages.
TodisablethedirectinvocationoptimizationforanonJMStransportwhenaproxyservice,sayloanGateway1invokesanotherproxyservice,say
loanGateway2.RoutetotheproxyserviceloanGateway2fromtheproxyserviceloanGateway1wheretheproxyserviceloanGateway2usesJMS
transport.
TohaveanHTTPproxyservicepublishtoaJMSqueuebuthavethepublishactionrollbackifthereisaexceptionlateronintherequestprocessing,split
theproxyserviceintoafrontendHTTPproxyserviceandabackendJMSproxyservice.ThepublishactionspeciesaqualityOfServiceelementof
exactlyonceandusesanXAconnectionfactory.
8.57.OutboundMessageRetries
InadditiontoconguringinboundretriesformessagesusingJMS,youcancongureoutboundretriesandloadbalancing.Loadbalancing,failover,and
retriesworkinconjunctiontoprovideperformanceandhighavailability.Foreachmessage,thelistofURLsyouprovideasfailoverURLsisautomatically
orderedbasedontheloadbalancingalgorithmintoafailoversequence.IftheretrycountisN,theentiresequenceisretriedNtimesbeforestopping.The
systemwaitsforthespeciedretryintervalbeforecommencingsubsequentloopsthroughthesequence.Aftercompletingtheretrya empts,ifthereisstill
anerror,theerrorhandlerpipelinefortheroutenodeisinvoked.Formoreinformationontheerrorhandlerpipeline,seeAddingPipelineErrorHandling
inProxyServices(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyservices.html)inUsingtheOracleServiceBusConsole.
Note: ForHTTPtransports,anyHTTPstatusotherthan200or202isconsideredanerrorbyOracleServiceBusandmustberetried.Becauseofthis
algorithm,itispossiblethatOracleServiceBusretrieserrorslikeauthenticationfailurethatmayneverberectiedforthatURLwithinthe
timeperiodofinterest.Ontheotherhand,ifOracleServiceBusalsofailsovertoadierentURLforsubsequenta emptstosendagiven
message,thenewURLmaynotgivetheerror.
Note: Forqualityofservice=exactlyoncefailoverorretrieswillnotbeexecuted.
8.58.ContentTypes,JMSType,andEncoding
Tosupportinteroperabilitywithheterogeneousendpoints,OracleServiceBusallowsyoutocontrolthecontenttype,theJMStype,andtheencodingused.
OracleServiceBusdoesnotmakeassumptionsaboutwhattheexternalclientorserviceneeds,butusestheinformationconguredforthispurposeinthe
servicedenition.OracleServiceBusderivesthecontenttypeforoutboundmessagesfromtheservicetypeandinterface.Contenttypeisapartoftheemail
andHTTPprotocols.
Iftheservicetypeis:
XMLorSOAPwithorwithoutaWSDL,thecontenttypeistext/XML.
MessagingandtheinterfaceisMFLorbinary,thecontenttypeisbinary/octetstream.
Messagingandtheinterfaceistext,thecontenttypeistext/plain.
MessagingandtheinterfaceisXML,thecontenttypeistext/XML.
Additionally,thereisaJMStype,whichcanbebyteortext.YouconguretheJMStypetousewhenyoudenetheserviceinOracleServiceBusConsoleor
intheOracleServiceBusPluginsforWorkshopforWebLogic.
Youcanoverridethecontenttypeintheoutboundcontextvariable($outbound)forproxyservicesinvokingaservice,andintheinboundcontextvariable
($inbound)foraproxyserviceresponse.Formoreinformationon$outboundand$inboundcontextvariables,seeInboundandOutboundVariables
Encodingisalsoexplicitlyconguredintheservicedenitionforalloutboundmessages.Formoreinformationonservicedenitions,seeProxyServices 42/45
Encodingisalsoexplicitlyconguredintheservicedenitionforalloutboundmessages.Formoreinformationonservicedenitions,seeProxyServices
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyservices.html)inandBusinessService
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/businessServices.html)inUsingtheOracleServiceBusConsole.
8.59.ThrottlingPattern
InOracleServiceBus,youcanrestrictthemessageowtoabusinessservice.Thistechniqueofrestrictingamessageowtoabusinessserviceisknownas
thro ling.Forinformation,seeThro linginOracleServiceBus(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/thro ling.html)in
theOracleServiceBusOperationsGuide.
8.60.WSICompliance
OracleServiceBusprovidesWebServiceInteroperability(WSI)complianceforSOAP1.1servicesintheruntimeenvironment.TheWSIbasicprolehas
thefollowinggoals:
DisambiguatetheWSDLandSOAPspecicationswhereverambiguityexists.
DeneconstraintsthatcanbeappliedwhenreceivingmessagesorimportingWSDLssothatinteroperabilityisenhanced.Whenmessagesaresent,
constructthemessagesothattheconstraintsaresatised.
TheWSIbasicproleisavailableatthefollowingURL:
h p://www.wsi.org/Proles/BasicProle1.1.html(h p://www.wsi.org/Proles/BasicProle1.1.html).
WhenyoucongureaproxyserviceorbusinessservicebasedonaWSDL,youcanusetheOracleServiceBusConsoleortheOracleServiceBusPluginsfor
WorkshopforWebLogictospecifywhetheryouwantOracleServiceBustoenforceWSIcompliancefortheservice.Forinformationonhowtodothis,see
OperationSelectionCongurationpageunderProxyServices
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyservices.html)inUsingtheOracleServiceBusConsole
ProxyServiceOperationSelectionCongurationpageinUsingtheOracleServiceBusPluginsforWorkshopforWebLogic
WhenyoucongureWSIcomplianceforaproxyservice,checksareperformedoninboundrequestmessagesreceivedbythatproxyservice.Whenyou
congureWSIcomplianceforaninvokedservice,checksareperformedwhenanyproxyreceivesaresponsemessagefromthatinvokedservice.Oracle
recommendsthatyoucreateanerrorhandlerfortheseerrors,sincebydefault,theproxyserviceSOAPclientreceivesasystemerrorhandlerdenedfault.
Formoreinformationoncreatingfaulthandlers,see:
ProxyServices:ErrorHandlers(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/proxyerrors.html)inUsingtheOracleService
BusConsole.
AddingandConguringErrorHandlersinMessageFlows
(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/eclipsehelp/tasks.html#taskAddCongErrorHandlersInMessageFlows)inUsingtheOracle
ServiceBusPluginsforWorkshopforWebLogic.
Formessagessentfromaproxyservice,whetherasoutboundrequestorinboundresponse,WSIcompliancechecksarenotexplicitlyperformed.Thatis
becausethepipelinedesignerisresponsibleforgeneratingmostofthemessagecontent.However,thepartsofthemessagegeneratedbyOracleServiceBus
shouldsatisfyallofthesupportedWSIcompliancechecks.Thisincludesthefollowingcontent:
Serviceinvocationrequestmessage.
Systemgeneratederrormessagesreturnedbyaproxyservice.
HTTPstatuscodesgeneratedbyaproxyservice.
TheEnforceWSICompliancecheckboxisdisplayedasshowninFigure311
Figure311EnforceWSIComplianceCheckbox
8.61.WSIComplianceChecks
Note: WSIcompliancechecksrequirethatthesystemknowswhatoperationisbeinginvokedonaservice.Forrequestmessagesreceivedbyaproxy
service,thatmeansthatthecontextvariable$operationshouldnotbenull.Thatdependsupontheoperationselectionalgorithmbeingcongured
properly.Forresponsemessagesreceivedfrominvokedservices,theoperationshouldbespeciedintheactioncongurationsforroute,publish,
andservicecallout.
WhenyoucongureWSIcompliancecheckingforaproxyserviceorabusinessservice,OracleServiceBuscarriesoutthefollowingchecks,shownin
Table311(h p://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageow.html#wp1065557).
Check WSIBasicProleDetails OracleServiceBusDescription

3.1.1SOAP R9980AnEnvelopemustconformtothestructurespeciedin Thischeckappliestorequestandresponsemessages.Ifaresponse
Envelope SOAP1.1,Section4,SOAPEnvelope(subjecttoamendment). messageischeckedandthemessagedoesnotpossessanouterEnvelope
Structure tag,asoap:clienterrorisgenerated.IfthemessageisanEnvelopetagbut
possessesadierentnamespace,itishandledbythe3.1.2SOAP
EnvelopeNamespace.
3.1.2SOAP R1015AReceivermustgenerateanerroriftheyencounteran Thischeckappliestorequestandresponsemessagesandisrelatedtothe
Envelope envelopewhosedocumentelementisnotsoap:Envelope. 3.1.1SOAPEnvelopeStructure.Ifarequestmessagehasalocalnameof
Namespace Envelope,butthenamespaceisnotSOAP1.1,asoap:VersionMismatch
errorisgenerated.
3.1.3SOAP R1014Thechildelementsofthesoap:bodyelementinan Thischeckappliestorequestandresponsemessages.Allrequesterror
Body Envelopemustbenamespacequalied. messagesgenerateasoap:Clienterror.
Namespace
Qualication
3.1.4 R1008AnEnvelopemustnotcontainaDocumentType Thischeckappliestorequestandresponsemessages.Allrequesterror
Disallowed Declaration. messagesgenerateasoap:Clienterror.
Constructs
3.1.5SOAP R1011AnEnvelopemustnothaveanychildelementsof Thischeckappliestorequestandresponsemessages.Allrequesterror
Trailers soap:Envelopefollowingthesoap:bodyelement. messagesgenerateasoap:Clienterror.
3.1.9SOAP R1032Thesoap:Envelope,soap:header,andsoap:body Thischeckappliestorequestandresponsemessages.Anyrequesterror
a ributeson elementsinanEnvelopemustnothavea ributesinthe messagesgenerateasoap:clienterror.
SOAP1.1 namespaceh p://schemas.xmlsoap.org/soap/envelope/
elements (h p://schemas.xmlsoap.org/soap/envelope/)
3.3.2SOAP R1000WhenanEnvelopeisafault,thesoap:Faultelement Thischeckonlyappliestoresponsemessages.
Fault mustnothaveelementchildrenotherthanfaultcode,
Structure faultstring,faultactor,anddetail.
3.3.3SOAP R1001WhenanEnvelopeisaFault,theelementchildrenofthe Thischeckonlyappliestoresponsemessages.
Fault soap:Faultelementmustbeunqualied.
Namespace
Qualication
3.4.6HTTP R1113Aninstanceshouldusea400BadRequestHTTP Onlyappliestoresponsesforaproxyservicewhereyoucannot
ClientError statuscodeifaHTTPrequestmessageismalformed. inuencethestatuscodereturnedduetoerrorsintherequest.
StatusCodes
R1114Aninstanceshouldusea405MethodnotAllowed
HTTPstatuscodeifaHTTPrequestmessageismalformed.
R1125Aninstancemustusea4xxHTTPstatuscodefora
responsethatindicatesaproblemwiththeformatofarequest.
3.4.7HTTP R1126Aninstancemustreturna500InternalServerError Thischeckappliesdierentlytorequestandresponsemessages.For

ServerError HTTPstatuscodeiftheresponseenvelopeisafault. requestmessages,anyfaultsgeneratedhavea500InternalServerError
StatusCodes HTTPstatuscode.Forresponsemessages,anerrorisgeneratediffault
responsesarereceivedthatdonothavea500InternalServerErrorHTTP
statuscode.
4.7.19 R2729Anenvelopedescribedwithanrpcliteralbindingthatis Thischeckonlyappliestoresponsemessages.OracleServiceBusnever
Response aresponsemusthaveawrapperelementwhosenameisthe generatesanonfaultresponsefromaproxyservice.
Wrappers correspondingwsdl:operationnamesuxedwiththestring
Response.
4.7.20Part R2735Anenvelopedescribedwithanrpcliteralbindingmust Thischeckappliestorequestandresponsemessages.Anyrequesterror
Accessors placethepartaccessorelementsforparametersandreturn messagesgenerateasoap:clienterror.
valueinnonamespace.
R2755Thepartaccessorelementsinamessagedescribedwith
anrpcliteralbindingmusthavealocalnameofthesamevalue
asthenamea ributeofthecorrespondingwsdl:partelement.
4.7.22 R2738Anenvelopemustincludeallsoapbind:headersspecied Thischeckappliestorequestandresponsemessages.Anyrequesterror

Required onawsdl:inputorwsdl:outputofawsdl:operationofa messagesgenerateasoap:clienterror.
Headers wsdl:bindingthatdescribesit.
4.7.25 R2744AHTTPrequestmessagemustcontainaSOAPActiona Thischeckappliestorequestmessagesandasoap:clienterroris

Describing HTTPheadereldwithaquotedvalueequaltothevalueofthe returned.
SOAPAction soapActiona ributeofsoap:operation,ifpresentinthe
correspondingWSDLdescription.
R2745AHTTPrequestmessagemustcontainaSOAPactiona
HTTPheadereldwithaquotedemptystringvalue,ifinthe
correspondingWSDLdescription,theSOAPActionof
soapbind:operationiseithernotpresent,orpresentwithan
emptystringasitsvalue.
Onethoughton3 Days Tutorial inOSB
1.brahmasays:
August19,2012at7:58pm
helloanubhav,thisisvenkatafromhyderabad,iamgoodinterestedtolearnoracleosb,couldyoupleaseprovideyourcontactdetailssothatican
contactyou
canuprovideonlinetrainingforOSB?
Reply(h ps://soalair.wordpress.com/2011/11/23/3daystutorialinosb/?replytocom=14#respond)
CreateafreewebsiteorblogatWordPress.com.(h ps://wordpress.com/?ref=footer_website)

Three

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Three

Transféré par

Droits d'auteur :

Formats disponibles

5/9/2017 3DaysTutorialinOSB|SOALair

November23,2011November25,2011 AnubhawSinha SOA aqualogicservicebus,bpel,insoa,oracleservicebus,osb,serviceoriented

8.59.Thro lingPa ern.69

Thereserveda ributeisactuallymorelikeaprexthatyoua achtoanynamespaceyoucreate.

<soap:bindingstyle=documenttransport=h p://schemas.xmlsoap.org/soap/h p/>

<wsdl:denitionsname=NewWSDLFilexmlns:soap=h p://schemas.xmlsoap.org/wsdl/soap/xmlns:tns=h p://www.example.org/NewWSDLFile/

<soap:bindingstyle=documenttransport=h p://schemas.xmlsoap.org/soap/h p/>

declarenamespaceopenuri=h p://www.openuri.org/&#8221(h p://www.openuri.org/&#8221);;

Action Use Availablein

Dynamicpublish Publishamessagetoa Pipelinestage

Publish Identifyastatically Pipelinestage

Action Useto. Availablein

Ifthen Performanactionorsetof Pipelinestage

Raiseerror Raiseanexceptionwitha Pipelinestage

Reply Specifythatanimmediate Pipelinestage

Resume Resumemessageowafter Errorhandlerstage

Action Use Location

Delete DeleteacontextvariableorasetofnodesspeciedbyanXPathexpression. Pipeline

Insert InserttheresultofanXQueryexpressionatanidentiedplacerelativetonodesselectedbyanXPathexpression. Pipeline

Java InvokeaJavamethod,orEJBbusinessservice,fromwithinthemessageow. Pipeline

MFL ConvertmessagecontentfromXMLtononXML,orviceversa,inthemessagepipeline.AnMFLisaspecializedXMLdocument Pipeline

Rename RenameelementsselectedbyanXPathexpressionwithoutmodifyingthecontentsoftheelement. Pipeline

Replace ReplaceanodeorthecontentsofanodespeciedbyanXPathexpression.Thenodeoritscontentsarereplacedwiththevalue Pipeline

Areplaceactioncanbeusedtoreplacesimplevalues,elementsandevena ributes.AnXQueryexpressionthatreturnsnothingis Error

Validate ValidateelementsselectedbyanXPathexpressionagainstanXMLschemaelementoraWSDLresource.Youcanvalidateglobal Pipeline

Action Useto Available

Log Constructamessagetobeloggedandtodeneasetofa ributeswithwhichthemessageislogged. Pipeline

Report Enablemessagereportingforaproxyservice. Pipeline

Transport DescriptionofLimitation TransportHeadersAectedByLi

JMS Canonlybesetwhentherequestiswithrespecttoaonewayserviceorarequest/responseservicebasedon JMSCorrelationID

Email TheOracleServiceBusruntimesetstheseheaders.Inotherwords,anyspecicationsyoumakefortheseheadersat ContentType

Note Thesamelimitationsaroundse ingcertaintransportheadersandmetadataaretruewhenyousettheinboundandoutboundcon

<sayHelloxmlns=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);

<m:sayHelloResponsexmlns:m=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);

<messagens0:type=xsd:stringxmlns:ns0=h p://www.w3.org/2001/XMLSchemaintance&gt(h p://www.w3.org/2001/XMLSchemaintance&gt);

<sayHelloxmlns=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);

<m:sayHelloResponsexmlns:m=h p://www.openuri.org/&gt(h p://www.openuri.org/&gt);

<con:faultxmlns:con=h p://www.bea.com/wli/sb/context&gt(h p://www.bea.com/wli/sb/context&gt);

<ctx:Faultxmlns:ctx=h p://www.bea.com/wli/sb/context&gt(h p://www.bea.com/wli/sb/context&gt);

<SOAPENV:Envelopexmlns:SOAPENV=h p://schemas.xmlsoap.org/soap/envelope/&gt(h p://schemas.xmlsoap.org/soap/envelope/&gt);

ModifytheSampleWSDLsothattheProxyWithSampleWSDLproxyservicereceivesasinglea achment.Thea achmentisaPurchaseOrder.Inthis

Check WSIBasicProleDetails OracleServiceBusDescription

3.4.7HTTP R1126Aninstancemustreturna500InternalServerError Thischeckappliesdierentlytorequestandresponsemessages.For

4.7.22 R2738Anenvelopemustincludeallsoapbind:headersspecied Thischeckappliestorequestandresponsemessages.Anyrequesterror

4.7.25 R2744AHTTPrequestmessagemustcontainaSOAPActiona Thischeckappliestorequestmessagesandasoap:clienterroris

Onethoughton3 Days Tutorial inOSB

Vous aimerez peut-être aussi