在 SAP J2EE 引擎上与 BW 组件通讯时出错的解决方案.docx
《在 SAP J2EE 引擎上与 BW 组件通讯时出错的解决方案.docx》由会员分享，可在线阅读，更多相关《在 SAP J2EE 引擎上与 BW 组件通讯时出错的解决方案.docx（41页珍藏版）》请在冰豆网上搜索。
在SAPJ2EE引擎上与BW组件通讯时出错的解决方案
在SAPJ2EE引擎上与BW组件通讯时出错
在SAPJ2EE引擎上与BW组件通讯时出错
RSBOLAP017JAVAcommunication通讯错误，门户通讯时出现未知错误
RSBOLAP017JAVAcommunicationerror:
anunknownerroroccuredduringportalcommunication
Diagnosis
AnerrorhasoccurredduringcommunicationwiththeBWcomponentsonSAPJ2EEEngine.
SystemResponse
Procedure
Contactyoursystemadministratorfordetailederroranalysis.
ProcedureforSystemAdministration
SAPNote888687providesdetailedinstructionsonanalyzingcommunicationandlogonproblems.
Summary
Symptom
ThisnotedescribeshowtoanalyzelogonproblemsandcommunicationproblemsintheareaofBExWebJava.ItillustrateswaysofanalyzingthemostcommonerrorsandalsodescribestheinformationthatSAPSupportrequiretoprocessmessagesinthisareaefficiently.
Otherterms
BExWeb,WebApplication,broadcasting,RFC,HTTP,HTTPS,ABAP,Java,SingleSign-On,SSO
ReasonandPrerequisites
YouconfigureinformationbroadcastinginasystemlandscapewithSAPNetWeaver2004orahigherversion.
or
Youconfigurethe"EnterpriseReporting,Query,andAnalysis"ITscenarioand,inparticular,the"Query,ReportingandAnalysis"scenariovariantinasystemlandscapewithSAPNetWeaver2004sorahigherversion.
Whenyoutesttheconfigurationorwhenyouexecuteanapplication,problemsoccurinthecommunicationbetweentheSAPWebApplicationServerJavaandtheSAPWebApplicationServerABAP.
Solution
Classifyingtheproblem
InformationbroadcastingandJava-basedBExWebApplicationscommunicatedifferentlybetweenJavaandABAP.Inthefollowingsection,thepossibleproblemsaredividedintocategories.Determinewhichcategoryyourquestionbelongsto,readtheinformationunder"Generalprocedure..."（dependingonthecommunicationprotocol）andthenreadthesectionthatdealsspecificallywithyourproblem.
Notethattherearetwodifferentprotocols:
∙RFCcommunication:
RFCcommunicationisalwaysusedwhentheSAPWebApplicationServerJAVAandtheSAPWebApplicationServerABAPcommunicate"inthebackground",whichmeansthattheycommunicatewitheachotherontheserver.Forinstance,whenqueryresultsarereadtodisplaytheminaJava-basedBExWebApplicationorwhenprecalculatedHTMLpagesaregeneratedinabatchjobandthepagesarethendistributedtoaKnowledgeManagementfolderusinginformationbroadcasting.
∙HTTP（S）communication:
ThistypeofcommunicationusestheWebbrowserasaninterimstep.Forexample,itisusedwhentheBExbroadcaster（whichisanABAP-basedBExWebApplication）iscalledfromaJava-basedBExWebApplication.ItisalsousedintheBExbroadcasterwhenthedialogboxforselectingthefolderiscalledtoexportthedataintotheportal,andthishasbeenimplementedasaJavaiView.Technically,thetwoactionsspecifiedhereareexecutedwhenaURLisstartedontheclientside.
Itisimportanttobearthedirectionofthecommunicationinmind:
∙JavatoABAPcommunication:
TheinitiatoroftheactionisontheJavasideandthedatarecipientisontheABAPside.
∙ABAPtoJavacommunication:
TheinitiatoroftheactionisontheABAPsideandthedatarecipientisontheJavaside.
Finally,therearethefollowingtwoproblemareas:
∙Anerrormayoccurwhensettingupthecommunication:
Thishappensifatechnicalconnectionbetweenthetwosystemscannotbeestablished.
∙Theremaybeanauthentication（logon）error:
Thetechnicalconnectionexists,butthereisaproblemidentifyingtheuserintherecipientthatcorrespondswiththeuserintheinitiator.SincebothJavaandABAPworkonlywithauthenticatedusersandnotserviceusers,itisabsolutelynecessarythattheuserlogsontothecallingsystemcorrectlysothattheoverallscenariocanfunctioncorrectly.
NotethatlogonticketsareusedintheareaofinformationbroadcastingandJava-basedBExWebApplications.Inthesescenarios,theuserdoesnotneedtologontotheWebbrowserortheSAPGUItwice.Adoublelogonindicatesthatthereisanerrorintheconfiguration.Therearesomeexceptionstothisrule,whichrenderanotherlogonnecessary:
oWhenyoucallaBExWebApplicationortheBroadcasterfromaBExtool,suchastheBExWebApplicationDesigner.
oWhenyouuseaspecificexportformatthatreferencescontents（forinstance,MIMEobjects）fromtheSAPWebApplicationServerorotherservers.
Weshallnowpresentinformationaboutmoreexactwaysofanalyzingtheproblemsforeachcombinationofthethreesubjectareasthatarementionedabove.
GeneralprocedurewhenusingRFCasacommunicationprotocol
IfproblemsoccurwhenyouuseRFCasacommunicationprotocol,intheSAPJ2EEVisualAdministrator,usethefollowingmenupath
∙""->"Server"->"Services"->"LogConfigurator",
tochangethefollowinglocationstothe"ALL"severitytoreceivemoreexactinformation:
∙com.sap.ip.bi.webapplications
∙com.sap.portal.connectors.BW
∙com.sap.portal.ivs.semantic.systemLandscape
∙com.sap.portal.ivs.systemConnectionTests
∙com.sap.security.api.saml
∙com.sap.security.core.server.jaas
∙com.sap.security.core.server.saml
∙com.sap.security.core.session
∙com.sap.security.core.ticket
∙com.sap.security.core.umap
∙com.sap.security.core.util
Savethechangesanddistributethemtoallservernodes.Donotforgettoresetthevaluestotheirdefaultvaluesassoonasyouhavefoundthereasonfortheerror.Youdothistoavoidunnecessaryentriesinthelogandtopreventanegativeimpactonsystemperformance.
Afterresettingthetracesettings,carryouttheactionthatcausedtheerroragain.
FormoreinformationaboutthecauseoftheerrorinanRFCcommunication,seethelastentriesinthedev_jrfc.trcfileinthefollowingdirectory
∙/usr/sap//JC/j2ee/cluster/server<#>
AllRFCerrorsareloggedinthisfileregardlessofthedirectionofthecommunication.Inmostcases,thisallowsyoutonarrowdownthecauseoftheerror.Youcanalsofindthelogentriesfortheindividualcomponentsconcernedinthefollowingfile
∙/usr/sap//JC/j2ee/cluster/server<#>/log/defaultTrace.trc
Youcanviewtheseinthe"LogViewer"inSAPJ2EEVisualAdministrator.Thenewestentriesaredisplayedatthetopinthe"LogViewer",whichdiffersfromthedev_jrfc.trcfile.
Notethatforaclusterinstallation,extrafilesarecreatedforeachservernode.SinceyoucannotdeterminewhichservernodeisprocessingtheRFCrequest,youmayhavetogothroughallthesefiles.
NecessaryinformationforSAPsupportwhenyouopenanOSSmessageandwhenyouuseRFCasacommunicationprotocol
Ensurethatyouprovidethefollowinginformationinamessage.Byprovidingalltheinformation,youcanspeedupthemessageprocessingbecausethereisnoneedforfurtherclarifications:
1.SAPsupportalsorequiresthedev_jrfc.trcanddefaultTrace.trcfilesfortroubleshooting.Proceedasdescribedunder"GeneralprocedurewhenusingRFCasacommunicationprotocol"
IfyoucreateanOSSmessage,attachthesefilestothemessageinthecaseofRFCcommunicationproblems.Ensurethatyoucopythefilesdirectlyfromtherespectiveserverandavoidmakinganyformatconversions.
Ifyoursystemisaclusterinstallation,attachthefilesofallclusternodestothemessage.ThisisnecessarybecausethereisnowayofdeterminingwhichservernodeisprocessingtheRFCrequest.
2.Also,attachtheABAPcertificatetothemessageasanattachment.Youcanexportthisintoafilebysavingthecorrespondingcertificatebyselecting"Export"inSAPJ2EEVisualAdministratorin"View""TicketKeystore"under""->"Server"->"Services"->"KeyStorage".
3.Createscreenshotsoftheloginmodulesettingsandattachthesetothemessage.Thesettingsareunder""->"Server"->"Services"->"SecurityProvider"inSAPJ2EEVisualAdministrator.Inthesettings,select"ticket"under"Components"andchoose'Toolbar'togotochangemode.Select"com.sap.security.core.server.jaas.EvaluateTicketLoginModule"inthelistofthe"loginmodules'andchoose"Modify".Changethewindowsizeandthecolumnsequenceinsuchawaythatallentriesthatexisttherearevisible,andthencreatethescreenshot.Inthesameway,proceedunder"evaluate_assertion_ticket"withthe"com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule"loginmodule.
4.SAPsupportalsorequiresanABAPusername,forwhichthereisacounterpartinJ2EE,andthepasswordsofbothusers.
5.Finally,nametheRFCdestinationthatisusedforthecommunication.
CommunicationerrorsinRFC-basedJavatoABAPcommunication
TodeterminethecorrectSAPNetWeaverBIABAPsystem,thesystemtriestodeterminethecorrectlogonparametersforanRFClogonusingthealiasintheportalsystemlandscape.Ifthisissuccessful,thesystemtransferstheparameterstotheJRFCinterfaceandthisinterfaceisresponsiblefortheactualcommunication.
Typicalproblemsandtheircharacteristicerrormessagesareasfollows:
∙Theuserdoesnothaveanyreadauthorizationforthesystemaliasintheportalsystemlandscape.
oErrormessage:
"Nopermissionforsystemalias..."inthedefaultTrace.trclogfile.
oSolution:
Inportalsystemlandscapemaintenance,under"Authorizations",selectthe"User"checkboxforthe"Everyone"usergroup,foranotherroleoranotherusergrouptowhichtheuserisassigned,orselectitforalistofsingleusers.
∙Aparameterismissingfromthesystemparametersandthisparameterisnecessaryforsettinguptheconnection.
oErrormessage:
"'...'ismissing"inthedev_jrfc.trclogfile
oSolution:
Intheportalsystemlandscapemaintenance,checktheparametersthat
升级会员 