Message from web service do not reach PI

[Former Member]

Hi,

I am facing a strange problem on my PI 7.0 - SP 13 [PID].

It picks data from 3 different systems using SOAP Web1, Web2, Web3.

One integration scenario and one integration objects in IR and 3 different scenarios in ID

I have a scenario ... SOAP - Proxy - Async.

This scenario has been working since last 2 years no problem.

Web1, Web 2 when send data to PID, it comes without any problem.

Now I added Web 3, which is copy of Web 2.

When we send data from Web 3, it is not reaching PI. I am getting the following error message. Chekced end points, ws user pwd all are correct.

We pointed Web 3 to PCD One more PI box, which is working.

If there was some problem with existing PI box it should have not processed or received requests from Web 1 and Web 2. correct?

If there is problem with Web 3, it should have not worked with PCD.

so now my Java dev says its fault at your end.

Where can I check?

I checked adapter engine, and all possible entries in RWB.

I dont see any mesg in MONI or message monitoring in RWB.

No entries in CC that sends the data to PI.

Restarted, checked entries in visual admin, re created config scenario, restarted system, chache refehs what not... did almost all.

But I still see the same error message.

I tried to describe in detail.

Please tell me the exact solution if any one faced similar error message earlier.

-

---

Venkat.

Edited by: Venkat A on Jun 29, 2009 10:39 PM

[former_member200962]

The problem you mentioned seems to be a binding issue......it occurs when:

1) No proper ID objects (CC, Receiver Determination, Sender Agreement, Interface Determination) are defined.

2) No proper XI-wsdl is provided to the web-application ( in your case it is Web3)

Regards,

Abhishek.

[Former Member]

1) No proper ID objects (CC, Receiver Determination, Sender Agreement, Interface Determination) are defined.

As I said, I had created the scenario using integration scenario from IR and CC is the copy object created for Web 2. So probability of mistakes are very less here but I re created the scenario and checked all objects but still i face this problem.

2) No proper XI-wsdl is provided to the web-application ( in your case it is Web3)

We are using SAP delivered standard interface at SAP and at Web service. This is without a MM and IM. So, we never used WSDL. We all the time make sure that web service sends the XML according to how SAP expects it.

It is true for other 2 servers and this Web 3 is a copy of Web 2. So there is no way that Web 3 is sending wrong XML as it works with PCD.

The scenario has never generated error message such as this since last 2 years.

any clues?

Thanks,

Venkat

Edited by: Venkat A on Jun 30, 2009 7:06 AM

[Former Member]

Venkat,

Probably the end points to where you are sending is wrong. Please open the wsdl for web3 with PCD and web3 with PID and compare both in any editor. You might be see some difference.

When you say web2 is a copy of web3 then are you using the same communication channel or a different one. If a different one then you may need to create the new WSDL.

Regards,

---Satish

[Former Member]

Satish,

the end points are different. I checcked the end points. seems to be correct. When I also tested by changing the CC name.

I am getting the following error message when I send it from Altova.

<?xml version="1.0"?>

<!-- see the documentation -->

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>Server Error</faultstring>

<detail>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

com.sap.aii.messaging.mo.MalformedMessageException: No SOAP Envelope but 1 TradingOrderRequest

at com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1051)

at com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:624)

at com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:616)

at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:382)

at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:381)

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.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: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:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

]]></text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

help

Edited by: Venkat A on Jun 30, 2009 12:13 PM

[Former Member]

the exact error message :

com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)
	at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:860)
	at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1440)
	at com.tpt.thresher.server.ws.proxy.tradingrequest.TradingOrderRequestOutBindingStub.FinOut(FinOutBindingStub.java:71)
	at com.tpt.thresher.server.ws.proxy.client.FinRequestClient.create(FinRequestClient.java:40)
	at com.tpt.thresher.server.ws.reconciliation.SendMessageHelper.send(SendMessageHelper.java:68)
	at com.tpt.thresher.server.ws.FinInterfaceProcessor.beginProcess(FinInterfaceProcessor.java:306)
	at com.tpt.thresher.server.ws.BaseInterfaceProcessor.process(BaseInterfaceProcessor.java:15)
	at com.tpt.thresher.server.ws.concurrent.SapDistributedProcessor.processTradeContract(SapDistributedProcessor.java:237)
	at com.tpt.thresher.server.ws.concurrent.SapDistributedProcessor.doProcess(SapDistributedProcessor.java:174)
	at com.tpt.thresher.server.ws.concurrent.SapDistributedProcessor.process(SapDistributedProcessor.java:163)
	at com.tpt.thresher.common.concurrent.SpringDistributedProcess.onMessage(SpringDistributedProcess.java:410)
	at com.sap.jms.client.session.Session.run(Session.java:715)
	at com.sap.jms.client.session.WaiterThread.run(WaiterThread.java:61)

This is the error message on Web 3. where else can I check for the receipt of message on PI ? FYI, i checked in CC, Mesg Moni in RWB, MONI. and how do I solve this?