Proxy Runtime errors in Integration Engines at RWB

Hi Experts,
We have configured the point to point configuration scenario in our landscape. I have two ABAP systems exchanges data using PI. I have configured both the ABAP systems as Application Systems and Corresponding Integration server as my PI system.
In RWB of PI I can see both these systems as proxy run time under Integration Engines, but are in error status.
Path to the same is Component Monitoring>Components>Integration Engines (here I can my systems as Proxy Runtime BSAB200, Proxy Runtime BSID200).
When run the test got the below error.
Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Does the Integration Engine know the business system?
Are roles in SXMS_CONF_ITEMS and SLD consistent?
Why do we need to create the RFC destination again when we select the related integration server as PI.
Can any one throw some light whey are these errors are occured.
Thanks,
Chinna

Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Reached to SLD but not to exchange profile.
Does the Integration Engine know the business system?
Yes.
Why do we need to create the RFC destination again when we select the related integration server as PI.
A central SLD scenario involves a central SLD, but not a central exchange profile.
The exchange profile used is always the one on the Integration Server the
application system connects to the exchange profile using the SM59 destination
LCRSAPRFC.
Regards
Pothana

Similar Messages

Proxy Runtime error

Hello..
In FILE-XI-BW scenario... I'm getting error in adapter monitoring (integration engine --> Proxy runtime )
Error is.. "Unable to log on to system D03 (BW system) in language en with user XIRWBUSER...
Can any one tell me what might be the problem..
Thanks..

Hi Padma
Can you check your configuration Tab in Runtime workbench. If there also you are getting this same error.
Create a port in your business system using Tcode : we21.
Also have you set in your proxy System the destination to Integration Server?
If not:
Goto sxmb_adm -> Integration Engine configuration -> Role of Business System = Application System with corresponding integration server dest//RFCdestinatio2yourIntegrationServer.
Best Regards
- lalit -

Error in integration Engine(indicating red color)

Hi all,
I am getting error in integration engine monitoring it shows red in color.
In that below PING status its telling like Unable to log on to system with PIRWBUSER.
Post installation has done in 001 client by default.the user is also existijng in that client its a service user.Anyone can help me out to resolve this issue.
Regards
Vijay Kumar G

Please check if the system XXX exists user PIRWBUSER.
Check the exchange profile properly configured or not and also check for the Authorizations for the said user.
See the below links also
Demo application: "You cannot log on to system .... with user XIRWBUSER
RWB error: javax.ejb.CreateException XIRWBUSER cannot log
How to get rid of the error message on RWB?

Integration Engine Proxy Runtime Error

Hello,
I have ECC and PI server for my landsacpe. When i ran SXMB_IFR tcode in my ECC server i got the follwing error under Runtime work Bench
Proxy Runtime - it is shows red color.
Unable to log on to system ECC120 in language en with user PIRWBUSER
Details for Ping Status
Message: Unable to log on to system ECD210 in language en with user PIRWBUSER
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system ECD210 in language en with user PIRWBUSER
at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:114)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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_Secure1229621978943._jspService(jsp_FC_Secure1229621978943.java:15)
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:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
When i checked my PIRWBUSER password in abap and poratal level there is no conflicts. Password is correct.
For integration i have created three RFC also
LCRSAPRFC,SLDAPIRFC,SAPJ2EE all these RFC are working fine and there is no error.
Can any one suggest me how to resolve this issue.
I am waiting for your reply.
Regards,
Sankaranarayanan.G
BASIS CONSULTANT

Hi Tuhin,
I have one more problem now. Intially i have configured my PI development portal.But after some days in my PI server when i ran SXMB_IFR is detecting wrong poral now. I have tried to change from my EXCHANGE Profile under integratrion server parameters i have changed PORT,URL and others.
but it is not come to effect. can you please help me where do i need to chage the portal?
I am waiting for your reply.
Regards,
Sankar.G

Proxy Runtime Error in RWB.

Hi All,
I am getting following error,
Please, help me to solve this problem
Message: Neither the messager server nor the application server can be reached for system DSM
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Neither the messager server nor the application server can be reached for system DSM
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:863)
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:726)
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:698)
at com.sap.aii.rwb.core.R3System.getRepository(R3System.java:910)
at com.sap.aii.rwb.core.BusinessSystem.getRepository(BusinessSystem.java:802)
at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:97)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:580)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:307)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:381)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:397)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:348)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.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:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks In Advance
Mahesh

Hi Seshagiri,
Actually, i am getting this error in message Monitoring dropdown, i have Proxy Runtime Receiver System option. when i am selecting the same i am getting the following error.
javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
     at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:456)
     at com.sap.aii.mdt.api.server.IntegrationEngineHomeImpl1_0.create(IntegrationEngineHomeImpl1_0.java:195)
     at com.sap.aii.mdt.api.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:57)
     at com.sap.aii.mdt.util.MonitoringBeanCache.getMonitoringBean(MonitoringBeanCache.java:305)
     at com.sap.aii.mdt.util.WebUtil.getMonitor(WebUtil.java:351)
     at jsp_monitor_new1221049881372._jspService(jsp_monitor_new1221049881372.java:140)
     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:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     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 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:427)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
     at com.sap.aii.rwb.web.messagemonitoring.viewcontroller.MmDynPage.doProcessBeforeOutput(MmDynPage.java:69)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
     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_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.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:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

RWB: System error in INtegration Engine, Adapter engine OK

HI All,
I have an interface converting IDOCS from R/3 into Text files and sending them to Legacy system via XI.
Data is flowing correctly, however I can see some errors in the RWB. (SXI_MONITOR is clean, no errors)
Upon investigation, I found that its has transmitted the file correctly, however this INtegration system error is shown.
To explain further:
BUssiness syst name of R/3 = BS_R/3
Bussiness syst name of legacy = BS_LEGACY
Bussiness service used = BS_SERV_R3
Message INterface = MIIA_R/3
So in RWB:
Message from BS_R3 to BS_LEGACY are SUCCSSFUL (Adapter and Integration engine , both success)
Message from BS_SERV_R3 to MIIA_R/3 (Adapter engine Sucess but INtegration engine = System Error)
Is it that the messages are going fine and the acknowledgements are failing or something like that.
Appreciate your guidance on same.
Many thanks
Shirin

Hi Shirin
I got a confusion understanding above
Scenario is IDOC R/3 -> PI -> Text Files -> PI -> Legacy system ?
if you have BS_SERV_R3 to MIIA_R/3 implemented for acknowledgments then definitely thats the error. But please share how you are getting ACK to understand and resolve error.
Thanks
Gaurav

Error in integration engine prosessing

Hi
I am doing proxy to fille interface for testing purpose in RWB in integration engine i test message tab i have given proper entries and send the message.In SXMB_MONI intially status of flag is green i have registered the queues in sxmb_adm then status has changed to red i opened the message it is showing as follow.
In Moni in place of receiver service interface it is showing sender service interface.But i have configured correctly
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>SI_PROXY_SENDER</SAP:P2>
<SAP:P3>urn:SESA:PROXY:FILE</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message SI_PROXY_SENDER, request message, namespace urn:SESA:PROXY:FILE)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards
Praveen

My problem was solved my R3 RFC destination was not pointing to client of integration engine.I have corrected the same my issue was solved
Regards
Praveen

Undesrtanding Proxy communication with the Integration Engine

I want to understand all the process in a client proxy communication. I know that the Local integration engine sends a PI-SOAP to the Central Integration Engine, and the local integration engine makes the communication with the ICM in the SAP PI side. My question are the next:
1. SAP documentation mentions that the XI Adapter is necessary. Where is it located?, after or before of the ICM in the SAP PI side. What is it function?, because the message is already in PI-SOAP format.
2. How does the local integration engine send the PI-SOAP message? Does it need an XI-Adapter ?.
Thanks in advance.

HI,
1. SAP documentation mentions that the XI Adapter is necessary. Where is it located?, after or before of the ICM in the SAP PI side. What is it function?, because the message is already in PI-SOAP format.
2. How does the local integration engine send the PI-SOAP message? Does it need an XI-Adapter ?.
-->XI Adapter is necessary only at the receiver side not at the sender side, by using proxy pre-configuration steps and proxy framework message from the sender system(Client proxy) will reach PI system. So, in this case XI adapter is not necessary(adapterless communication).
Proxy Framework which consists of Proxy Generator and Proxy Runtime:
Proxy Generator- Converts ABAP corresponding elements to WSDL corresponding elements and viceversa and by using Proxy Runtime, local Integration will be connected to Central Integration.
When a request is sent form client proxy-->ABAP corresponding elements will be converted to WSDL elements and local integration engine will be connected to central integration engine and whole process will be done.
If the receiver system is SAP, and since there can be many SAP systems connected to PI, to send data from PI to that particular receiver SAP system, PI needs the receiver system details like business system name etc. So, XI adapter is manadatory only at the receiver side.
check out this blog for more info:
[http://www.****************/Tutorials/XI/ABAPProxy/page1.htm]
Regards,
Sunitha

Error in integration Engine

Hi All,
In integration Engine im getting error as "Exception occurred during XSLT mapping of the application".
when i tried to test the mapping its showing the warning as "javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: Could not execute operation on Java Object. -> java.lang.reflect.InvocationTargetException at "
Please help me reagrding this issue to proceed further!!!

Hi,
Can u please explain the problem little detail...
Are u getting this error in SXMB_MONI??
If yes then can u copy the source payload and check it in the Message Mapping once??
If problem is coming from mapping... try to analyze.. else u can put now vtz exactly the prblm is..
Babu

Hi. about monitor message of integration engine from RWB.

I want to monitor message of iintegration engine from RWB.
but i can not open message content tab page and queue monitor tab page.
hint is : SSO login failed. need to logon again.
which user should i use to logon?
i tried so many user not to be able to logon successuflly.

Hi Joy,
if you want to use the SSO functionality for any component you need to maintain it first....i think u SSO configurtion is not yet done ....and hence you are getting the above error.......
Pls chk the below link....thsi is for PI 7.1...
http://help.sap.com/saphelp_nwpi71/helpdata/EN/32/1c1041a0f6f16fe10000000a1550b0/content.htm
Hope this will help..
Regds,
Pinangshuk.

JMS To proxy Runtime error

Hello,
I am doing a JMS to Proxy scenario, so in mapping at run time i am getting
an error as:
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 30, 30, 20(:main:, row:1, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 30, 30, 20(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error:
My source file is :
00 QY040 AM01- NBG IABENT21 A 6257069 21 00000020001 20070301200703030002167440 429900000002167440teealm tezste A:10245980-1; 1/1; I/EE-31; 91830; ALMSTETTER,HANS 000000000 10245980-1 ALMSTETTER,HANS91830
Can any one throw some light,how does JMS handle incoming data ?
Regards,
Anirban.

Hi All,
I want to configure JMS to Proxy Scenario , the link provided above doesnt show any blog.
Can anyone explains what steps I need to follow to configure JMS to PROXY scenario? More specifically configuration and stpes to be considered in case of JMS configuration . (Proxy I know ).
I do have the XSD , source structrure which will be genrated via MQ .
Thanks,
Pushkar

Messages versions integration engine in RWB

Hello,
i've testing in test system (in development system this don't occur).
When i raise a interface, only two version by messages have me in RWB:
adapter engine (status succeffull)
adapter engine (status succeffull)
and integration engine isn't
why?
Besides, in SXMB_MONI haven't any messages
idea?
thank

Is LOGGING and TRACE set properly in the Test System: /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
If message display is proper in Dev and not in Test then the settings in Test system are not proper.
Is the output of the scenario coming as needed?
Regards,
Abhishek.

Error in Adapter engine in RWB

Hi,
I'm facing 2 type of issues in RWB,
Issue 1) Adapter Engine is in Red State in Component monitoring,
Error: Details for 'Is the Adapter Engine Running?'
Response from Adapter Engine: Fatal ArchiveJob (Archiving) failed.(Details: Code: MS.JOB.ARCHIVE; Location: com.sap.engine.messaging.impl.core.job.executor.ArchiveExecutor; Reason: java.io.IOException: The HTTP request of command "MODIFYPATH" did not reach the XMLDAS. This may indicate that the credentials for the HTTP destination have expired.; Time: 31.03.2011 00:00:05)Response from Adapter Engine: Fatal ArchiveJob (Archiving) failed.
2) If I click, any one of the option like Communication Channel monitoring, Engine Status etc, I'm getting the error
"Internet Explorer cannot display the webpage"
It seems to be the URL to open these component(Communication Channel monitoring, Engine Status etc ) is wrong. Fromwhere the URL address is taken? Where we need check the host name??
I searched in sdn, but could not find any related topics.
Kindly help me resolve this issue ASAP.
Thanks & Regards,
Baskaran K

Hi Baskaran,
For 1), did you check if the XML DAS communication user (used in destination "DASdefault") is configured correctly according to the documentation http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/68fac39a363d33e10000000a11466f/frameset.htm and is assigned to the "XMLDASSecurityRole" role?
And check if you have configured the rules for your Archiving job (Component Monitoring -> Adapter Engine XIE -> Background Processing).
It seems the archiving does not work because of configuration issues.
An archiving job without rules means: all messages are relevant for archiving. The delete job will only delete messages which are not relevant for archiving. So it does not do anything in this system. It can lead to the database table keeps growing, if it's the case too.
You should check the archiving configuration so that the archiving job runs successfully.
If you do not want to archive the messages, please deactivate the archiving job. Then the delete job should clean the old messages with the next execution.
You may delete it straightly on the Background Processing.
For the 2), "Internet Explorer cannot display the webpage", try using the compatibility mode of your browser.
Regards,
Caio Cagnani

Java Proxy Runtime Error - A remote host refused an attempted connection

I am able to register my Java server proxy with no errors. However when I message is sent through I get the following error in Xi Adapter:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method someJavaProxyCallIB of proxy bean com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4LocalObjectImpl0_0: A remote host refused an attempted connect operation.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method someJavaProxyCallIB of proxy bean com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4LocalObjectImpl0_0: A remote host refused an attempted connect operation.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Doea anyone know why this is happening?

I guess, that you have Java proxy libraries in the EAR file. Remove them before deploying.
Regards
Stefan

RWB - Component Monitoring - Integration Engines = none ???

Hi.
I made a Business System in SLD.
Name: DEV_410
Role: Application System
Related Integration Server: XHD_100       (XI Server)
Technical System: DEV on dev60           (type: Web AS ABAP)
Client: 410 of DEV
Logical System Name: HMXDEV410
But I cant see the business system in RWB - Component Monitoring - Integration Engines. There shoud be 'Proxy Runtime DEV_410' in Integration Engines, I think.
Is there any wrong in SLD or RWB?
Thanks in advance.
sjyoon.

Hi
Go to SLD select your business system :DEV_410
And check the following entries for your business system
Role:   Application Server
Related Integration Server : (Check if this value correctly configured to your Integration Server client)
If this configuration is correct, this means XIRWBUSER is able to connect to the proxy runtime of application systems(DEV_410). Then there will be no entries displayed under RWB - Component Monitoring - Integration Engines in RWB.( that is how my RWB component monitoring is configured)
Only error entries are displayed under RWB - Component Monitoring - Integration Engines in RWB. Say for example XIRWBUSER is not able to connect to the proxy runtime of application systems(DEV_410). Then you see a entry in RED below your RWB - Component Monitoring - Integration Engines
Satish

Proxy Runtime errors in Integration Engines at RWB

Similar Messages

Maybe you are looking for