Contents

ABAPWebServiceMonitors
TheSAPABAPWebServiceInfrastructureprovidesasetofmonitorstodisplayinformationonthedifferententitiesinvolvedinWebService
communication.ThemonitorsareconnectedtothesupportutilitiesforWebServices.

Figure1NavigationGraph
Figure1showsthepossiblenavigationbetweenthedifferentmonitoringviewsandtheconnectedsupportutilities.Thediagramisastate
transitiondiagramwheretheroundcornernodesrepresentthestatesinthiscaseviews/screens.Thewhiteonblacknumbersinthe
roundcornernodesshouldmakeiteasiertorelatethetextandthescreenshotstothenavigationgraph.Thesharpcornernodesrepresent
activitiestriggeredfromscreens.Suchactivitiesalsoexistbetweentwoscreenslikeexecutionofaquerywhengoingfromaselection
screentoalistscreenbutinmostofthecasesthesearenotshowntokeepthefiguresimple.Theboldarrowsrepresentforwardand
back(F3)navigation.Thethinlinedarrowsrepresentnavigationpathswhereonecannotnavigateback.
ThecentralentityinWebServicecommunicationisamessage.Thereforeoneusuallyentersthemonitorsviathemessagemonitor.The
correspondingtransactionnameisSRT_MONI.ThisentrypointisshownattheverytopofFigure1.Asonlyasynchronously
processedmessagesarepersistedthemonitordisplaysonlythese.Youenterthemessagemonitorviaaninitialmessageselection

screen(Figure2)whereyoucandoyourselectionviaatimerangeand/orviavaluesfordifferentWebServiceentitiese.g.messageIDor
sequenceID.

Figure2InitialmessageselectionscreenStandardselection
Ontheselectionscreenyoucandecideifyouwanttofirstdisplayasummaryofthemessagesmatchingtheselectioncriteriaonthe
bottompartorifyouwanttodirectlydisplaythelistofmessages.Inadditionyoucanswitchbetweendisplayingarestrictedoranextended
setofmessageattributesinthemessagelistbasicviewvs.technicalview.
Theselectioncriteriaarepartitionedintotwosets,standardandadvancedselection.Incaseofstandardselection(Figure2)youhavetwo
selectionmodes.YoucaneitherselectbasedonanexplicitsetofIDsmessagesorallmessagesbelongingtoalistofsequences.The
secondmodeisbasedonatimerangewithoptionaladditionofmessageattributevalues.Ifyoudonotenteranyadditionalselectioncriteria
theprefilledtimerangeisusedforthesummarydisplayaswellasforthedetailmessagelistdisplay.
Theattributesfortimerangebasedselectionareeitherdirectmessageattributeslikeadaptertype,usernameorsender/receiverpartyand
interfacenameorthederivedattributeprocessingstatusgroup.
Thevaluesforadaptertypeare:
PlainSOAPnonWSRMbasedSAPreliablemessaging
GroupwarescenarionotavailableinNWreleasesbelow8.0
MappingnotavailableinNWreleasesbelow8.0

Eventingpublish/subscribemechanismwhichisbasedonWSmessages
StandardWebservicenativeWebServices
ShortcutlocalWebServicesthatarecalledinaperformanceoptimizedway
IntegrationServerinanXIenvironmentmessagesformintegrationserver
Theprocessingstatusisaderivedmessageattributethatcombinesthenativemessagestate,thesequencestate,theasynchronous
processingqueue(akabgRFCqueue)stateandforonfailure(eg.TentativeUpdateandConfirm/CompensateTUC/C)messagesthe
respectivestate.Theprocessingstatetellsifthereareproblemsintheprocessingofamessageornot.Allstateslistedaboveneedtobe
consideredtomakesuchastatement.
Inordertoprovideaneasiermanagementoftheprocessingstatesthesearegroupedintotheprocessingstategroups.Thevaluesforthe
processingstategroupsare:
Applicationerroranerroroccurredintheapplicationthatimplementsaserviceprovider.
Systemerroranerrorintheprocessinginfrastructureoccurred.
ErroneousthisstategroupcombinesApplicationerrorandSystemError.
Terminatedwithdumpmessageprocessingledtoashortdump.
Waitforprocessingthemessageiswaitingforprocessing.Thereasoncanbethatthemessageiscurrentlynotthefirstinthe
processingqueue.Inthatcaseallpredecessorsneedtobeprocessedfirst.Itcouldalsoindicateanoverloadsituationpreventingafast
processingofthemessage.
IncompleteprocessingthisstategroupcombinesApplicationerror,SystemerrorandWaitforprocessing
Incomplete(no"pulling"messages)inNWreleasesbelow8.0thesameresultthanIncompleteprocessing(pullingisasynonymfor
groupware)
CancelledthemessagewasmanuallycancelledoritisanautomaticallyannulledcompensatemessageinTUC/Ccommunication.
Isolatedthelogicalportofthemessageisisolated.Thereforethemessagewillnotbesenttotheserviceprovidersystem.
CancelledorisolatedthisstategroupcombinesCancelledandIsolated
Finishedthemessagewassuccessfullyprocessed.
Incomplete(no"pulling"messages)
TheadvancedselectiontabisshowninFigure3.Itprovidesmoretechnicalattributesforthemessageselectionquery.Youcanagain
eitherselectviaasetofidentifiersfortheasynchronousprocessingqueueorthemessagepersistenceentry.AsamessageIDcan
actuallyrepresenttwomessagesoneatserviceconsumersideandoneatproviderside,bothcouldbestoredonthesamesystemthe
messagepersistenceIDisauniqueidentifierforamessage.

Figure3InitialmessageselectionscreenAdvancedselection
Thesecondmethodtoquerymessagesishereagainbasedonatimerange.ThistimetheSAPpassportidentifiersrootcontextIDand
transactionIDcanbeusedtofurtherrestricttheresultset.TheSAPpassportcanbeusedtoidentifycommunicationentitiesinacross

systemcommunication.ItcanbehelpfultogetanendtoendmonitoringviewinacommunicationscenariowherethemessageIDcannot
beusedasuniqueIDthroughoutallinvolvedsystems.

Figure4Messagesummary
WhenyoudecidetofirstdisplaythemessagesummaryviewyoullgetaresultsimilartotheoneinFigure4.Thenumbersofmessages
forthefollowingstatusgroupsaredisplayed.
ApplicationError
SystemError
WaitforProcessing
Cancelled
Isolated
Finished
Vialineselectionandclickingontheglassesbuttonorbydoubleclickonalineyougettothemessagelistfortherespectivestatusgroup.
Asalreadymentionedthemessagelist(Figure5)canbedisplayedintwodifferentflavors.Thebasicviewshowsapredefinedsetof
messageattributeswhichdoesnotshowsomemoretechnicalattributesliketheuniquemessagepersistencyIDwhichareshowninthe
technicalview.Thetechnicalviewalsodoesnotshowallpossibleattributesforamessage.Theusercandefineapersonalviewwherehe
canselectapersonalizedsetofattributestobedisplayed.

Figure5MessageList
Fromthecurrentmessagelistonecantriggerareselectionofthemessagestobedisplayedintwoways.Eitheronechoosesageneral
reselectionwhichdisplaysapopupthatgivessimilarselectoptionsthantheinitialselectionscreen.Inthiscasethereselectionhasno
relationshiptothecurrentlydisplayedmessages.Alternativelyonecandisplaythesetofrelatedmessages.Thesearerelatedtothe
currentlyselectedmessages(bytheuserinthetablecontrol).Hereonecanchoose:
Sequencemessagesallmessagesbelongingtothesamesequencesthantheselectedmessagesaredisplayed.Thisisanextension

ofthecurrentselection.
Parentmessagesallparentmessagestothecurrentlyselectedmessagesaredisplayed.Aparent/childrelationshipexistsforexample
intheeventscenario,wherestartingfromaninitialeventmessageseveral(ornone)childmessagesarecreatedthathavetheinitial
eventmessageasparentmessage.
Childmessagesallchildmessagestothecurrentlyselectedmessages.
Themessagelistcanbeexportedindifferentformatswhichisastandardfunctionalityofthetablecontrol.Inadditiontheselected
messagesinthetablecontrolcanbeexportedinXMLformat.
Thefollowinghelptextsareavailable.Adescriptionofthefieldsinthetablecontrolcanbedisplayedviaclickingtheibutton.Adescription
oftheprocessingstatevaluescanbepoppedupviaMessagemenu.ThePAFstatescanbeignoredinreleasesbelowNW8.0.A
descriptionofaspecificprocessingstatecanbedisplayedviaclickingontherespectiveunderlinedentryintheprocessingstatecolumnof
thetablethree.
Therearesomeactionsthatcanbeexecutedtothemessagesselectedinthetablecontrol.
Theseactionsare:
Restartonlymessagesinerrorstatecanberestarted.Themessagesareaddedtotheasynchronousprocessingqueueandbythat
willbeprocessedagain.Arestartmakesforexamplesenseifsincethelastexecutiontrialthatledtoacommunicationerrorthe
configurationwaschanged.
Restartwithdebugonlyallowedifasingleerroneousmessagewasselected.ThedebuggerisstartedintheWSruntimecodenotin
theapplicationcode.
Cancelonlymessagesinerrorstatecanbecancelled.Cancellingamessagesetsittoafinalstatewithoutbeingprocessed.Insome
casesamessagecannotbecancelledinthemessagelistscreen.Itthenneedstobecancelledformtheinconsistentmessagelist
screen.
Consistencycheckonlyavailableintechnicalview.Fortheselectedmessagesaconsistencycheckbetweenthemessagestatedata
andtheasynchronousprocessingdataisexecuted.Itleadstotheinconsistentmessagelistscreen.Fortechnicalreasons
inconsistenciesareonlydetected5minutesaftertheactivitythatledtotheinconsistencytookplace.
Theconsistencycheckleadstotheinconsistentmessagelist(Figure6).Itlookssimilartothegeneralmessagelistwithsomedifferent
functionality.Thisviewisintendedforsupportactivitiesasitshowssomemoretechnicaldetailinformationthanthemessagelist.
Intheinconsistentmessageviewyoucannotdoageneralreselectionbutinsteadyoucanrunaconsistencyrecheckforthedisplayed
messages.Youcanenforcethecancellationoftheselectedmessagesskippingsomechecksthataredoneinthegeneralmessagelist
cancellationaction.ReconciliationisafunctionalitythatisonlyavailableinreleasesfromNW8.0onwards.Inlowerreleasesignorethis
button.

Figure6Inconsistentmessagelist
Fromthemessagelistandfromtheinconsistentmessagelistonecandisplaydetailsforasinglemessage(Figure5).Forthisonecan
eitherclickontherespectivemessageID(underlined)inthetablecontrolordoubleclickinafieldofthemessagelistwherethecontentis
notunderlined.

Figure7MessagedetailsPayloadview
Figure7showsthepayloadviewwhichisthedefaultviewthatyoureachwhenyouwanttodisplaymessagedetails.Themessage
payloadsareviewedinatableontherightside.Inthisexampleonecanseethatincaseoferrortheinitialmessageversionandtheerror
versionareavailable.AnXMLviewofthepayloadcanbedisplayedinapopupwindow.
Viathemessagemenuonecanswitchtoadifferentviewwhichshowsapartfromthepayloadssomemoremessageinformationlike
headerinformation(Figure8).Italsoshowsmoredetailabouttheactualmessagestructure.Forexampleyoucanseeintheexamplethat
thepayloadisstoredasanattachmenttotheactualmessage.

Figure8MessagedetailsExtendedview
Returningtothecentralmessagelistonecannavigatetoseveralotherviewsandtools.Theentitymostrelatedtothemessageisthe
sequence.ItcontrolsthereliablemessagingWSRMorSAPsPlainSoap.InSAPsWSRMimplementationalsomessageswithqualityof
serviceexactlyonce(EO)aresentinthecontextofaWSRMsequenceinthiscasewithonebusinessmessageentryplusatechnical
terminatemessage.Thatswhyforallasynchronousmessagesarelatedsequenceexists.Thesequencesrelatedtoacertainmessage
setaredisplayedinthesequencelist(Figure9).

Figure9Sequencelist
Thesequencelistscreenislookingquitesimilartothemessagelist.Youhaveagainreselectionpossibilities.Somerelatingtoselected
sequencesandalsoageneralreselectionpopup.Asactionsrelatedtotheselectedsequencesyoucantriggerasoftorahardtermination.
Asoftterminationclosesthesequenceonconsumersidefornewmessages.Ifthesequencecontainsunfinishedmessagestheseare
processedandafterthelastmessageisprocessedthesequenceissettostateclosed.Incaseofahardterminationthesequenceis
terminatedimmediatelyandallnotyetprocessedmessagesofarecancelled.
Usuallyonewouldaccessthesequencelistviathemessagelistasthemessageisthecentralentity.Insomecasesitisusefuloreven

necessarytoenterthemessagemonitorviaselectingasequencedirectly.Forexampleifthereareno(more)messagesexistingfora
persistentWSRMsequence.Thatsequencecanonlybefoundviathemessageselectionentry.
AdirectaccesstothesequencemonitorisdonebystartingtransactionSRT_MONIS.Firsttheinitialsequenceselection(Figure10)
screenisdisplayed.HereonecaneitherenteralistofexplicitsequenceIDsordoaselectionbasedonatimerangeaddingsome
sequenceattributes.Fromtheselectionscreenonegetstothesequencelistscreen.

Figure10Initialsequenceselection
Fromthemessagelist,theinconsistentmessagelistandthesequencelistonecannavigatetoothequeueentrylist.Inthisscreeneither
theupdatetaskmonitor(TransactionSM13)isdisplayedortheasynchronousprocessingqueue(bgRFC)monitor(Transaction
BGRFCMONFigure11).Theupdatetaskmonitorisonlydisplayedifthereisapendingupdatetaskinrelationtotheselected
message(s).

Figure11Queueentrylistasynchronousprocessingqueue
Theasynchronousprocessingqueuemonitorshowsincaseofmultiplemessageselectiononlythedataforthefirstmessageinthe
selectionset.Thedataoftheprocessingqueueisdisplayedintheleftpart.ThequeueIDisincaseofWSRMcommunicationcomposedof
aprefixandthesequenceID.Ontherightsideoncanseetheunitsinthequeue.Eachmessageisassociatedtooneunit.Onproviderside
thisisa1:1relationship.Technicalmessageslikeaclosesequencemessagearealsovisibleasaunit.Thestateoftheunitandthequeue
isdisplayedastrafficlights.IntheexampleinFigure11thereisaprobleminprocessing.
Thequeueentrylistisintendedforspecialistswhohavedeepknowledgeofthemessageprocessinginfrastructure.Especiallytheactions
thatcanbeexecutedherecanleadtoinconsistentprocessingstatesiftheuserdoesnotexactlyknowwhathe/shedoes.

Figure12ApplicationLog
Fromthemessagelistandinconsistentmessagelistonecannavigatetotheapplicationlogentries(Figure12)relatedtothecurrently
selectedmessages.Therearetwoflavors,messagerelatedentriesandcontextrelatedentries.Inthefirstcaseallapplicationlogentries
whichcontainthemessageID,asequenceoraTUC/C(tentativeupdateandconfirmorcompensate)compensatemessagerelatedtothe
selectedmessagessetaredisplayed.Amessagelogentryisforexamplewrittenifamessageismanuallycancelledorasequenceis
manuallyterminated.Contextrelatedapplicationlogentriesarerelatedtothemessageprocessinginfrastructureindependentonspecific
processedmessages.
Averyimportanttoolforerroranalysisinmessageprocessingistheerrorlog.Fromthemessagelisttheinconsistentmessagelistandthe
sequencelistonecannavigatetotheerrorloglist(Figure13)fortheselectedmessages/sequences.Alreadyinthelistthereissome
technicaldatadisplayedfortherespectiveerror.Mostofitiscutoffinthescreenshot.Veryimportantforrootcauseanalysisistheerror
text.Bydoubleclickingonalinefurthererrordetailisdisplayedbelowthelist.Inthebottomareaonecanforexampletriggerthedisplayof
thecallstackatthemomentwhentheerrorwasdetectedorthehttperrorpagesentbacktotheserviceconsumer.Fromtheerrorloglist
onecannavigatetothetraceviewforaselectederrorlogentry.Traceshavetobeswitchedoninadvanceinordertogetaresult.
Thefullfunctionalityoftheerrorlogandtracefunctionality(WebServiceSupportUtilitiestransactionSRT_UTIL)isdescribedina
separatedocumentWebServiceUtilities.ThesetoolsareintendedforsupportbythedevelopmentteamsoftheWebService
infrastructure.ForSAPcustomerstheerrorlogshorttextandtheerrorlogdatacanhelptofindtherootcauseofaprobleminmessage
processing.
TheerrorlogtoolandthetracestoolsareaccesseddirectlyviatransactionSRT_UTIL.Fromtheentryscreenonecanstarttheerrorlog
vieweronecanswitchonandconfiguretracesanddisplaythetraceresults.Therearethreedifferenttypesoftraces:
Performancetraceforthemessageprocessinginfrastructure.Regardingtheserviceproviderapplicationcodeonlythetotaltimeis
recorded.
Payloadtracetotracedetailsofthemessagepayload.
Functionaltracetoseemoredetailsonthedatainsidethemessageprocessinginfrastructure.
AllthisisnotcontainedinFigure1tokeepthepicturesimple.

Figure13Errorloglist
Fromthemessagelisttheinconsistentmessagelistandthesequencelistonecannavigatetothelistofruntimeerrors(akaABAPshort
dumps)relatingtotheselection(Figure14).ViaadoubleclickonecannavigatetotheruntimeerrordetailviewwellknowntoABAP
programmers(ST22).Incaseofanerrorintheserviceproviderimplementationwhereitmakesnosensetoproceedusuallyashortdump
istriggeredandtheerrordataislogged.

Figure14Runtimeerrorlist
Intheruntimeerrorlistonecandoareselectandexportthelistdata.Forerroranalysisitusuallymakesmoresensetonavigatetothe
errordetailviewandexportthedetailederrorinfoforfurtheruse.

Backtotop\