cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Adapter Posting Failure

Former Member
0 Kudos

We have interface SOAP - RFC, pretty simple. But upon post of SOAP message through basic authorization (user/passwd) it is coming back with fault message -

<detail>

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

<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

<text>com.sap.aii.af.service.cpa.CPAException: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn&apos;t retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;

at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.checkForError(CommonLookup.java:53)

at com.sap.aii.af.service.cpa.InboundRuntimeLookup.getBinding(InboundRuntimeLookup.java:411)

at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:714)

at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:430)

Everything works fine through Scenario Test and Test message on RWB. The WSDL is generated on Sender SOAP channel and Outbound interface. Cache seems to be alright (delta/full/SXI_CACHE)

URL used for generating the WSDL

http://server:port/XISOAPAdapter/MessageServlet?channel=:BS_CCBCC_ECYBORG:CC_ECYBORG_HOURS_SOAP_SEND...

Any pointer will be helpful.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Samir,

Are you using any authentication while connecting to the XI box. If yes please check the roles assigned to that user it should have role as SAP_XI_APPL_SERV_USER and if required an additional profile as SAP_NEW. This is in case you are using a user specifically to connect to the XI from the 3rd party application.

Cheers

Abhimanyu

Former Member
0 Kudos

hi samir,

some input / response not as per expected. make sure the input is the same like the structure that you already define.

regards

fernand

Former Member
0 Kudos

Hi, first make sure that your channels and agreements are activated in ID. Try a CPACache refresh using PIDIRUSER.

http://<host>:<port>/CAPCache/refresh?mode=full

Regards.

MS

Former Member
0 Kudos

As I mentioned before, everything works fine in Test Sceario and posting through RWB - that means everything is activated. And also as I said before all cache seems to be fine (full/deta and SXI_Cache)

former_member182503
Active Contributor
0 Kudos

Samir,

This issue is usually related to outdated CPA Cache, but, as you said, you've already done a full CPACache refresh, so, check if your Sender Agreement is well configured.

Best regards,

José Nunes

Former Member
0 Kudos

Since it is working fine in Test Scenario and also on RWB, how else should I ensure that sender agreement/channels are fine.

I observed that in Problem tab of Cache for Integration Directory it has two items -

Unable to notify Adapter Engine 'xxxx.com' that is affected by

the data changes

HTTP connection to 'http://<sldServer>:port/CPACache/invalidate' returns

the status code '401' (Unauthorized) in response

Unable to notify integration runtime (Java) of data changes

HTTP connection to 'http://<sldserver>:port/run/value_mapping_cache/ext?

method=invalidateCache&mode=Invalidate&consumer=af.sld.serversld&consumer_mode=IR' returns the status code '401' (Unauthorized) in response

Could this be a problem, if yes any pointer on resolving this will be great help!!

former_member200962
Active Contributor
0 Kudos

The problem is with cache itself.....the objects are not activated properly since cache Overview is showing error....check if the user performing activation is locked......check for the status of PIAFUSER.

Regards,

Abhishek.

Former Member
0 Kudos

The user PIAFUSER is unlocked.

former_member200962
Active Contributor
0 Kudos

Can you try testing with this URL format:

http://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?
channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%
5E<SenderMI>

Regards,

Abhishek.