Customizing Runtime Workbench

Dear experts
Im looking for providing the volume of data processed by XI on monthly basis to the customer in graphical format.
I know in Performance monitoring this data is available for download only. Is there any tool which interprets this data in graphical format
-Keerthi

Hi Keerthika,
Well, you are almost there...Yes Performance Monitor is best to get the data, so if you can export into excel sheet you can generate graphical form of the same data manually.
Otherwise, One other best tool/report is Early Watch Alert Report (EWA). Although I am not if you have Solution Manager in your environment but EWA reporting does require Solution Manager. If you have SolMan, the EWA report provides your detailed information in graphical format.
It gives you data such as Peak Hours day wise, Sender based data flow and many other relevant information.
Regards
Sekhar

Similar Messages

Log on to Runtime Workbench : click display error on page

Dear all,
when i try to log on to Runtime Workbench and click on display message , i am getting error that error on page,
we have already done post implementation steps for PI(XI),,
what to do, to test the senario from Runtime Workbench.
Best regards,
dushyant.

Hi,
This will help you
SAP Note-768456 & SAP Note-928862
http://help.sap.com/saphelp_nw2004s/helpdata/en/06/5d1741b393f26fe10000000a1550b0/content.htm
Regards
Agasthuri Doss

SAP PI 7.1 - Runtime Workbench Error - "Service Unavailable"

Hi there,
We have just installed SAP PI 7.1 on an iSeries 6.1 server, all seems to be successfully installed except that the runtime workbench will not start. It seems to be that the runtime workbench service was not deployed successfully during the install.
The error when trying to launch the Runtime Workbench is:
Application cannot be started!
Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5004] Cannot create application loader for application sap.com/com.sap.xi.rwb.
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.defineSharedApplicationLoader(LoadContextUtils.java:100)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.bindLoader(DeployServiceImpl.java:1780)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:216)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)
     at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.IllegalStateException: [ERROR CODE DPL.DS.6102] The sap.com/com.sap.xi.rwb class loader is not null, but sap.com/com.sap.xi.rwbcom.sap.engine.boot.loader.ResourceMultiParentClassLoader722bac67alive for the LoadContext, which is wrong /nHint: The reason could be leaking class loaders.You can also check, whether above in the stack trace, there is a call to unregister the loader.
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.ensureLoaderNameAndUnregisteredLoader(LoadContextUtils.java:52)
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.defineSharedApplicationLoader(LoadContextUtils.java:72)
     ... 34 more
Has anybody had this error before? Or how easy is it to manually re-deploy the service again?
Thanks for the help
Lynton

I have just seen this on the forum as well which is exactly the same question that I have....
RWB application cannot be started after PI 7.1 installation
I will try it now and will let you know
Lynton
Edited by: Lynton Grice on Aug 18, 2009 12:29 PM

Problem with Runtime Workbench and with sending data from XI to SLD

Hello 
 
Could I have a little help, a hint in the two following topics: 
 
1. I run Runtime Workbench -> Component Monitoring -> Display All and I get this error: 
 
Error during communication with System Landscape Directory: User credentials are invalid or user is denied access 
 
In filesystem log I can find like this: 
 
XIRWB.com.sap.aii.mdt.frames.jsp_error [SAPEngine_Application_Thread[impl:3]_40] Fatal: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access 
Thrown: 
MESSAGE ID: com.sap.aii.rwb.agent.server.rb_LCRAgent.landscapeCommunicationError 
com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access
 at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:773)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
 at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getXIDomain(SLDAgentObjectImpl0_0.java:375)
 at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
 at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
 at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
 at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
 at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117) 
 at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
 at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
 at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at jsp_FC_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.java:24)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
Root cause: 
com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access 
 at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577)
 at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341)
 at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:280)
 at com.sap.lcr.api.cimclient.CIMOMClient.performBatchOperation(CIMOMClient.java:1251)
 at com.sap.lcr.api.cimclient.CIMClient.performBatchOperation(CIMClient.java:2268)
 at com.sap.aii.utilxi.sld.MRSldProxy.stage1(MRSldProxy.java:989)
 at com.sap.aii.utilxi.sld.MRSldProxy.loadComponents(MRSldProxy.java:918)
 at com.sap.aii.utilxi.sld.MRSldProxy.loadSld(MRSldProxy.java:907)
 at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:373)
 at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:434)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:764)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)
 at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0_0.getXIDomain(SLDAgentObjectImpl0_0.java:375)
 at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)
 at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)
 at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
 at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
 at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117)
 at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
 at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
 at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at jsp_FC_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.java:24)
 at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
 at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 
 
 
I don't know what is wrong. 
I have configured: 
- SLDCHECK work properly, 
- none of the users PI* type not lock, 
- password to the PI* users in exchangeProfile entered correctly, 
- In VA in the JCo RFC Provider I have properly configure: AI_RUNTIME_JCOSERVER, LCRSAPRFC, SAPSLDAPI_SID - from the ABAP I can connect to this programs ID 
- In VA in SLD Data Supplier I have properly configure bookmarks HTTP Settings and CIM Client Generation Settings. CIMClient Test is OK 
 
I do not know what else I can see, what else I have properly configured ... I looked at the notes:: 936093 jak i 721548... 
 
 
2. I can't send data from XI to SLD, ie makes me a system definition in Web As Abap and Web as Java but nothing appear to me in Exchange Infrastructure. Exchange Infrastructure is empty - what is wrong?? 
I carried out the recommendation by 764176 and 1031321 notes 
 
I restart below applications (no effect)... 
com.sap.xi.directory (Integration Builder/Configuration) 
com.sap.aii.af.app (Adapter Engine) 
com.sap.xi.rwb (Runtime Workbench) 
com.sap.xi.repository (Integration Builder/Design) 
 
Can I ask for help and guidance in these topics? 
 
Regards 
RP 

I increased logging in the NWA (Configuration -> Log Configuration) - and increased the some things here to log ALL. So that from the NWA (Monitoring -> Logs and Traces) I see a little more information (but does not follow that with which the user is a problem). 
 
Here are some interesting logs ... 
I was most rash or irritation of those that say about the lack of credentials u2013 I must use Viusal Administrator and set good service ... 
 
What do I have done: 
In the Visual Administrator -> Cluster -> Server -> Services -> SLD Data Supplier 
I have set in the HTTP Settings tab the host and port SLD, the user name and password is also entered as it is in the SLD. To be sure, already have set for the user entered here such roles as: 
SAP_SLD_ADMINISTRATOR 
SAP_SLD_CONFIGURATOR 
SAP_SLD_DEVELOPER 
SAP_SLD_GUEST 
SAP_SLD_ORGANIZER 
Maybe we are talking in this place about a different user? 
 
Similarly, when it comes to tab CIM Client Generation Settings - here's all the same thing done. CIMClient test shows that everything is OK. 
When I click the button: This trigger the transfer of data to the SLD gets the message that everything was shipped correctly. Indeed, I received an instance of JAVA in SLD 
Also clicked on this icon: Assign application roles to user group - got information that everything is attached properly. 
 
By ABAP side, the connections: INTEGRATION_DIRECTORY_HMI, SAPSLDAPI, LCRSAPRFC, AI_RUNTIME_JCOSERVER and AI_DIRECTORY_JCOSERVER work correctly, ie I can perform the test - which means that programs ID are properly positioned in JCO Provider in VA. 
 
Puzzling is this message: 
The SLD data is inconsistent. 
 
Strange also that the message (from the ABAP everything is available in SMGW no errors): 
Connect to SAP gateway failed 
 
And what is this error: 
 
could not sync ExchangeProfile: 
Thrown: 
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
 
Below is a list of some interesting logs ... 
 
########### 
 
Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'. 
 
############# 
 
SLD is not accessible. Check SLD Data Supplier service settings. 
 
########### 
 
"Warning","2012-02-22","07:53:50:986","Data get on com.sap.sldserv.data.GetSAPBCCentralServiceInstance class processing failed. htThe SLD data is inconsistent. This is an internal processing problem.","/System/Server/SLDService","com.sap.sldserv.DataCollector","n/a","saptest2","Server 0 60_36694", 
 
######### 
 
com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access 
 
################ 
 
Full Message Text
CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://saptest2.unx.era.pl:56000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xit.saptest2), due to: HTTP 503: Service Unavailable
 
################## 
 
Full Message Text 
 
could not sync ExchangeProfile: 
Thrown: 
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457) 
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015) 
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238) 
at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101) 
at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1288) 
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:195) 
at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177) 
at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165) 
at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:582) 
at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43) 
at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52) 
at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167) 
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) 
at java.security.AccessController.doPrivileged(AccessController.java:219) 
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
 
############## 
 
Full Message Text 
 
Import of software component version list from component repository failed 
Thrown: 
com.sap.lcr.api.cimclient.LcrException: User credentials are invalid or user is denied access 
at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577) 
at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341) 
at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:198) 
at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:146) 
at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstancesImpl(CIMOMClient.java:443) 
at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstances(CIMOMClient.java:747) 
at com.sap.lcr.api.cimclient.CIMClient.enumerateInstances(CIMClient.java:980) 
at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.enumerateInstances(JavaCIMObjectAccessor.java:211) 
at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateInstances(SAP_SoftwareComponentAccessor.java:204) 
at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateSAP_SoftwareComponentInstances(SAP_SoftwareComponentAccessor.java:239) 
at com.sap.aii.ibrep.server.sldaccess.interfaces.CRAccess.getSwcLinks(CRAccess.java:82) 
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.getEoLinks(SwcAccessor.java:59) 
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.getEoLinks(EOAServiceImpl.java:75) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.getEoLinks(EOAServiceBean.java:66) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.getEoLinks(EOAServiceRemoteObjectImpl1_0.java:527) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:232) 
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) 
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) 
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) 
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) 
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) 
at java.security.AccessController.doPrivileged(AccessController.java:219) 
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
 
############## 
 
Full Message Text 
 
An exception was thrown in the UME/ABAP user management connector. Message: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=localhost SYSNR=60 GWHOST=localhost GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner '127.0.0.1:sapgw60' not reached 
TIME Thu Feb 23 07:28:06 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 16

Messages on Holding at Message Monitoring under Runtime Workbench

Hello Colleagues,
we have currently the problem that a lot of messages for some interfaces are in status Holding under Message Monitoring at Runtime Workbench for PI 7.1.
I'm not able to resend the messages with status Holding as well as change status to cancel.
Quality of Service for the Interfaces are Exactly Once in Order.
I assume an error message blocks the queue and due to the fact we have Exactly Once in Order configured all following messages be in status Holding.
Is my assumption right?
But, I am not abel to find any messages in status error with blocks the queue!
How can I solve that issue?
Many thanks in advance!
Jochen

I assume an error message blocks the queue and due to the fact we have Exactly Once in Order
configured all following messages be in status Holding.
AE should have least number of EOIO messages at a given instance...otherwise Holding is what you get.....and holding is common with EOIO....so see if you can chagne the QoS of some messages to EO
But, I am not abel to find any messages in status error with blocks the queue!
Never you will get an error in SXMB_MONI....or the queue blocked....
When your message goes out of IE...the corresposding message entry is marked with chequered flag...observe in MONI you will see this....however in AE the message can fail if not able to send to the target system....
For some more understanding refer my answer in this thread:
Re: Restarting Error's in SXMB_MONI
Regards,
Abhishek.

Error while opening Adapter Monitoring in Runtime Workbench

Hi,
I am unable to open Adapter Monitoring from
Runtime Workbench -> Component Monitoring -> Adapter Monitoring
When I tried to open, I am getting following message in the new window:
"The page cannot be displayed"
Please let me know where I can enable this option.
Thanks,
Yogi.

Hi,
Go thru this SAP Note- 768456,928862
Also this doc may help u-https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
Regards,
Moorthy

Customizing request & Workbench request

Dear all,
What is the differance between Customizing Request & workbench request?

Hi,
Workbench Requests
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Workbench requests record changes made to ABAP Workbench objects.
There are local and transportable Workbench requests. (Local Workbench requests have the target system <space>.)
The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.
Customizing requests
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
Changes to Customizing settings are recorded in Customizing requests.
When you release the requests, the current status of the recorded settings is exported, and can then be imported into the consolidation system and, if necessary, into subsequent delivery systems.
The client settings determine whether
o changes to the Customizing settings are possible
o the changes are recorded
When you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System.
Regards,
Satish

Problems after new installation (Runtime workbench not working as expected)

Hello
We have just finished installing new ECC & Netweaver in our company.
On PI side, I created a sample file (Payload) and did IR and ID configuration
and saw the payload getting picked up from the source directory and getting
posted in the target directory successfully.
However, when I went to Runtime Workbench and clicked on the Adapter and
File adapter to see the messages, I dont see anything. It is just blank.
However, when I click on Display it shows integration server and 4 items under it. 4th item is Adapter Engine which has a RED button next to it, indicating there is some problem.
When I click on the Adapter button to see the list of adapters, i see again a red button next JPR. However, File doesn't show any error message. But when I double click on File adapter, instead of showing successful messages, it shows a blank screen as if no file has been transmitted.
Also down at the bottom of the Runtime Work Bench Screen
Self-Tast Status and
Are Communication Channels without errors
also show a Red buttons next to it.
By double clicking on 'Are communication Channels without errors - Details", I get the following error message:
1 communication channels have an error status0 communication channels inactive0 communication channels not providing any status information0 adapters logging communication-channel-independent processing errors .
This is a fresh new install and any feedback on this will be greatly appreciated.
Thanks

Not answered completely. But still closing to make room for new questions

Error in Component Monitoring(Runtime Workbench)

Hi,
I am getting an error in component monitoring section of runtime workbench. I got a note(851711), where it says 'CompilingException' error can be corrected by applying SP14. But I am still getting same error after applying SP14 and redeploying XI ADAPTER FRAMEWORK CORE 3.0 (SAPXIAFC.sca), XI TOOLS 3.0 (SAPXITOOL.sca) and XI ADAPTER FRAMEWORK 3.0 (SAPXIAF.sca). Please advice how to correct this error.
Error Message:
com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: D:/usr/sap/QN7/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1138903402125.java:27: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier (try -source 1.4 or lower to use 'enum' as an identifier) import com.sapportals.htmlb.enum.TableCellStyle; ^ D:/usr/sap/QN7/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1138903402125.java:947: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier (try -source 1.4 or lower to use 'enum' as an identifier) compTable.setColumnType(com.sapportals.htmlb.enum.TableColumnType.IMAGELINK, 1); ^ D:/usr/sap/QN7/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1138903402125.java:948: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier (try -source 1.4 or lower to use 'enum' as an identifier) compTable.getColumn(1).setCellHAlignment(-1, com.sapportals.htmlb.enum.CellHAlign.CENTER); ^ 3 errors .
Thanks,
Ask.

Hi,
it can be for some system configured on http destination or the sld system configured for this server.
take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
regards.
roberti

Strange Behaviour into Runtime Workbench

Hi all,
I have a question for us.
Into our system PI 7.1 we have a strange behaviour in Runtime Workbench - Message Monitoring.
When I choose for the fiel "FROM" the value "Database" I obtain the list of software component that I find the value "Integration Server".
But when I choose the value "Database (Overview)" the value "Integration Server" into list of software component doesn't exist.
Why Do the system have this behaviour?
best regards,
Davide Bruno

Hey,
The old way of seeing msg use - the db option... In Pi 71 the db overiew options gives you an aggregated view of ur messages. this is very helpful in tracking repeated failures, anylysing the types of failures etc...The "strange" view is actually a pretty neat tool... We used to do this in excel sheets after dowloading the report from sxmb_moni..
regards,
Arvind R

Error in Runtime WorkBench/Component Monitoring

Hi all,
1. I have configured an AS ABAP system to connect to the SLD successfully. In the Technical System List of SLD, it's named "TE1 on sap0810". (Successful)
2. After, i have created a Business System corresponding for this Technical System "TE1 on sap0810" with Client 810. In the Business System List of SLD, it's named "BUSINESS_SYSTEM_TE1CLNT810". (Successful)
3. And after, i log on into Runtime WorkBench and choose "Component Monitoring" Tab and choose Display all component, i get an error about the Business System "BUSINESS_SYSTEM_TE1CLNT810" for "Ping Status" and "Self-Test Status" as message below: (Error)
Ping Status: Unable to log on to system BUSINESS_SYSTEM_TE1CLNT810 in language en with user PIRWBUSER Last Retry Jul 28, 2008 5:48:56 PM ICT ... Details
Self-Test Status: Unable to log on to system BUSINESS_SYSTEM_TE1CLNT810 in language en with user PIRWBUSER Last Retry Jul 28, 2008 5:48:56 PM ICT ... Details
Anyone can please help me to resolve this problem?
Thanks a lot in advance,
<removed by moderator>
Vinh Vo
Edited by: Mike Pokraka on Jul 28, 2008 5:07 PM

hi friend
If you have created the TS & BS correctly in SLD
check the following points:
1)The JCO service might have been down...check it out....Sometimes it happens due to overloading of server...try to restart the server.....after clearing queue and cache restarting the server
2)check the RFC destinations AI_DIRECTORY_JCOSERVER, AI_RUNTIME_JCOSERVER.
regards
kummari

Error in Runtime workbench.

Hi Experts,
In the runtime workbench i have seen a error, the message direction is inbound. The error details are :
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at SeeXIAS2, the whole lookup name is deployedAdapters/SeeXIAS2/shareable/SeeXIAS2.: java.lang.Exception: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at SeeXIAS2, the whole lookup name is deployedAdapters/SeeXIAS2/shareable/SeeXIAS2.
Could you please let me know why exactly the error has occured ?
Many Thanks,
Ravi

Hi,
Please check if you have configured the AS2 adapter properly ...
Please confirm it as per the sample scenario give in AS2 Manual.
Refer the links for the AS2 Manuals
SEEBURGER EDI &AS/2 adapter installation and configuration guides
Thanks
swarup

Error in Runtime Workbench, Component Monitoring, Proxy Runtime

Hi,
I have the following error in the Runtime Workbench, under Component Monitoring->Integration Engines->Proxy Runtime. The error message is Ping Status: Unable to logon to system xxx in language EN with user XIRWBUSER. However, I am unable to find out where the account and password are specified in order to correct this. Any help would be appreciated.

Hi,
it can be for some system configured on http destination or the sld system configured for this server.
take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
regards.
roberti

Error in Runtime WorkBench/Configuration/Save Configuration

Hi all,
In Runtime WorkBench, when i choose "Configuration" tab, and after choose "Save Configuration", i get an error message as below:
"Configuration saved RFC ping failed for the following RFC destinations (created upon saving) in the system DEV800: PMIDEV800, PMITST910"
In this case, my XI system has one Integration Server: DEV800 and one Business System TST910. Two RFC (Process Monitoring Infrastructure RFC) created: PMIDEV800, PMITST910 can't not function correctly. And i don't know how i can correct this error.
Anyone can please help me to correct this error?
Thanks a lot in advance,
Vinh Vo

hi vinh vo,
do chk this link
Installing and Configuring SAP Interactive Forms by Adobe for the SAP NetWeaver Composition Environment
Thanx
Sampath

"Error in message monitoring in runtime workbench"

Hello All,
I have an error in message monitoring in runtime workbench.
We have installed PI7.0 and it should run on port 50000.But it is running on port 50100.
Please suggest what are the steps involved to resolve this problem.
Thanks and Regards
SAN
null
k san

San,
Can you please copy / paste error message.
Also check if you have set correct port in Exchange profile under Runtimeworkbench.
Nilesh

Customizing Runtime Workbench

Similar Messages

Maybe you are looking for