Which URI to be used in the WSDL hosted by PI

[former_member188885]

Hi All,

I have a requirement Webservice -> PI -> ECC. Here i have provided the WSDL file and the WSDL URL that was generated by the Sender agreement.

When the third party team tried to open the URL i provided, it got opened. They have also tried to open the URI that were present inside the WSDL file (URI starting with HTTP and HTTPS). They say that those two URIs are not getting opened in their end.

Is this an problem? Which URL should they use for sending data to PI? Can anyone clarify on this please?

Regards,

Lavanya R

[iaki_vila · Accepted solution]

Hi Lavanya2010,

Any of the URLs mentioned by SAP in this link will work Configuring the Sender SOAP Adapter - Advanced Adapter Engine - SAP Library

Change the WSDL URI with any of that and try first with SOAPui after to share with your partner.

Regards.

[former_member183816]

See my reply in above post.

[former_member188885]

We are receiving the following error:

<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

<text>

1. com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=;AN=null;ANS=null;
   at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:233)
   at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:167)
   at com.sap.aii.af.service.cpa.InboundRuntimeLookup.&lt;init>(InboundRuntimeLookup.java:88)
   at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:519)
   at com.sap.aii.adapter.soap.web.MessageServlet.getBinding(MessageServlet.java:882)
   at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:452)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
   at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
   at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
   at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
   at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
   at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:469)
   at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:299)
   at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
   at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
   at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
   at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
   at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
   at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
   at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
   at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
   at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
   at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
   at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
   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:78)
   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:78)
   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:78)
   at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
   at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
   at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
   at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
   at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
   at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
   at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
   at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
   at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
   at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
   at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
   at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)

</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

[Former Member]

request message format is wrong so your getting this error.

[former_member440061]

Hello Lavanya,

Please check above thread. We too were getting similar error while trying to send the data to the web service. please see if it helps.

Thanks

Faisal Jamal

[iaki_vila]

Hi Lavanya,

Have you tried the next things and in this order?

- Refresh CPA cache, do a dummy change in the ID objects like to change the description.

- Test in Integration Directory, Tools->Test Configuration.

- Test in runtime workbench, Component Monitoring-> Adapter Engine -> Test Message

- Generating the WSDL with the format previously mentioned.

- Test in local with SOAPui.

- Check the input and output payloads against the PI XSDs (you can find several online validators).

Regards.

[former_member188885]

Thank you for the reply. When they tried to use the WSDL URL to invoke they have received an error message : "The invocation resulted in an error: Method Not Allowed"

[Former Member]

If possible , could you ask them to use the wsdl (you have already shared) and the endpoint(present inside the wsdl , starts from HTTP or HTTPS) to send a test message to PI, Instead of trying to access the wsdl url.

[former_member188885]

Hi Avinash,

They have used the WSDL URL and when they tried to send a test message they received the error that i have mentioned above.

[Former Member]

No need to send message to wsdl url. Message has to be sent to the endpoint url.

[former_member188885]

okay i will ask them to try.

[Former Member]

>> They have also tried to open the URI that were present inside the WSDL file (URI starting with HTTP and HTTPS). They say that those two URIs are not getting opened in their end.

its end-point url, you can't open(like WSDL URL). Only you can send request message to this endpoint.