SOAP adapter problems

Hello,
we are trying to use the SOAP adapter to send several RFCs
to the backend, our client uses Apache Axis.
We first tried the url http://
AxisFault
faultCode: Server
faultSubcode:
faultString: Application Error
faultActor:
faultNode:
faultDetail:
QIRF_SEND_REQUIRMENTS_GET_DAT2.Exception:
/code
It seems the message is sent to the backend (because
NO_SUBSYS_DEFINED is one of the exceptions defined for
QIRF_SEND_REQUIRMENTS_GET_DAT2 and I see successful
delivery in the RWB) but the content is not recognized.
The almost identical message sent via the HTTP-adapter
works without problems:
<?xml version="1.0" encoding="iso-8859-1" ?>
<rfc:QIRF_SEND_REQUIRMENTS_GET_DAT2 xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<rfc:T_QAIVCTAB />
<rfc:T_QAIMVTAB />
<rfc:T_QAICATAB />
<rfc:T_QIERRTAB />
<rfc:I_IND_EVALUATE_CHARACTERISTIC>X</rfc:I_IND_EVALUATE_CHARACTERISTIC>
<rfc:I_IND_SET_BLOCK_INDICATORS>X</rfc:I_IND_SET_BLOCK_INDICATORS>
<rfc:I_IND_TRANSFER_USAGE_DEC_CODES>X</rfc:I_IND_TRANSFER_USAGE_DEC_CODES>
<rfc:I_IND_MULTI_TRANSFER_POSSIBLE>X</rfc:I_IND_MULTI_TRANSFER_POSSIBLE>
<rfc:I_QAILS>
<rfc:SATZART>Q40</rfc:SATZART>
<rfc:SUBSYS>ICD564</rfc:SUBSYS>
</rfc:I_QAILS>
</rfc:QIRF_SEND_REQUIRMENTS_GET_DAT2>
Can anyone help ?
Thanks in advance.
PS: What is the technical difference between the two SOAP
URLs and why are they on different ports? Is there
documentation explaining these issues? And what exactly
does "Use query" string" in the configuration tab for a
SOAP Sender communication channel mean? Which parameters
are allowed for this query string?

Hi!!!
The first url you use when you want to send a message to your SOAP adapter.
The second one you use with a plain HTTP adapter - you send a message directly to a pipeline.
Check this link:
http://help.sap.com/saphelp_nw04s/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
Regards,
Andrzej

Similar Messages

Sender SOAP Adapter problem in PI 7.1

Hello Everyone,
I have a problem with Sender SOAP Adapter
In PI 7.0 i am able to receive the messages through sender SOAP Adapter for both HTTP and HTTPS. But when i am testing in PI 7.1 i am unable to receive any messages at Adapter level for both HTTP and HTTPS
All sender leagcy system are getting different error messages like
1. 400 HTTP Bad request.
2. Invalid request.
3. BAPI error message
Could any one please assist me in this problem.
Thanks
Vick

Hi Vick,
Try like this......in ID from your sender agreement in which you have your sender SOAP comm channel, from menu select Display WSDL and then copy the WSDL URL and give it to source applications to use it.............create a service user for them to access PI 7.1 server while sending the SOAP req msg.............
your source applications may have to generate proxy from this WSDL URL in their application and then they can send a SOAP req msg to your PI 7.1 server............
Regards,
Rajeev Gupta

XI Soap Adapter: problems in parsing XML

Hallo,
I call a Web Service using XMLSpy and this is the response (note tag <File>):
 <SOAPSDK4:ExpBaselineResponse xmlns:SOAPSDK4="http://tempuri.org/PRWBS_PRIMAVERA/message/">
 <RESULT>OK</RESULT>
 <File><?xml version='1.0' encoding='UTF-8'?>
<Dati:Parametri xmlns:Dati="Schema">
 <ELSAG xmlns="Schema">
 <proj_id>4623</proj_id>
 <BS_short_name>FS0084AAAA01 - B1</BS_short_name>
 <BS_proj_id>1302</BS_proj_id>
 <TARGET_START>2004-04-01</TARGET_START>
....etc...
If I call the same Web Service from XI, this is the response:
<SOAPSDK4:ExpBaselineResponse xmlns:SOAPSDK4="http://tempuri.org/PRWBS_PRIMAVERA/message/" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAPSDK3="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAPSDK1="http://www.w3.org/2001/XMLSchema">
 <RESULT>OK</RESULT>
 <File><?xml version="1.0" standalone="yes"?>
<Dati:Parametri xmlns:Dati="Schema">
 <ELSAG xmlns="Schema">
 <proj_id>4623</proj_id>
 <BS_short_name>FS0084AAAA01 - B1</BS_short_name>
 <BS_proj_id>1302</BS_proj_id>
 <TARGET_START>2004-04-01</TARGET_START>
....etc....
In my flow, I use a java mapping to parse the content of tag <File> into a message.
My mapping works correctly only with the first option.
Is it possible to change XI Soap Adapter encoding for HTML?
My java mapping uses this parser:
 public void execute(InputStream MyInputStream, OutputStream MyOutputStream)
 throws StreamTransformationException {
 SAXReader reader = new SAXReader();
 Document document;
 try {
 document = reader.read(MyInputStream);
this instruction generates an Exception only with XI message.
Can anybody help me??
Thanks;-)

Hi,
I would suggest you go through this Pdf for the SOAP Adapter configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
And also have a glance on the info for webservices given below,
Just go through these links and they will surely help you learn more about Webservices:
<a href="/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi Webservices using SAPXI</a>
<a href="/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies between SAP System & Webservice Using Proxies</a>
You can Go through these links to get some info about accessing Webservices:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/f9bc3d52f39d33e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/b7/d7baaf1481a349ab723e3acd7334b3/content.htm
Go through these links which will surely help you find an answer to your problem.....
Regards,
Abhy

Sender SOAP Adapter - problem

Hi,
After reading through the forums I understood that SOAP adapter turns green only with the first message.
I have set everything up and sending a test message with XML Spy:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Body>
 <m:SIMPLE_OUT_MI xmlns:m="http://test.com/soapTest">
 <TEXT>TEST</TEXT>
 </m:SIMPLE_OUT_MI>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
XMLSpy returns me an empty message back:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Header/>
 <SOAP:Body/>
</SOAP:Envelope>
I can not see the message in SXMB_MONI and the adapter stays gray.
Where do I look for the problem ?

Hi Vick,
Try like this......in ID from your sender agreement in which you have your sender SOAP comm channel, from menu select Display WSDL and then copy the WSDL URL and give it to source applications to use it.............create a service user for them to access PI 7.1 server while sending the SOAP req msg.............
your source applications may have to generate proxy from this WSDL URL in their application and then they can send a SOAP req msg to your PI 7.1 server............
Regards,
Rajeev Gupta

SP13 : SOAP Adapter Problem

Hi All,
Recently we upgraded from SP9 to SP13. Every since we upgraded to SP13 we are experiencing weird problem with Outbound SOAP adapter.
We have exposed an outbound interface as a webservice, which is consumed by a .Net application. When the .Net application try's to call the webservice, we get soap exception "Server Error".
To make sure the call is reaching XI, we put in wrong credentials and we got authorization error. So the call is getting to XI.
Has anyone encountered this weird problem? Any thoughts or suggestions will be very much appreciated.
Thanks,
naveen

Hi,
There is a tool called SOAPScope from www.Mindreef.com
Its a webservices diagnostic tool. Use this to troubleshoot.you can get a evaluation for 4 days i guess.
Regards,
Sridhar

SOAP Adapter Problem

Hi,
I 've the following scenario:
Legacy (File)->XI-(Split the message)-->Proxy
I receive the file, into XI, I split the message and send one message for each line, and send to proxy.
The communication channel for proxy is not able to with multiple structures, for solved it i have a communication channel SOAP Receiver and SOAP Send.
The systems are:
BS_LEG (Sender)
BS_XI
BS_SAP (Receiver)
In configuration i have:
Sender BS_LEG
Interface: MT_File_OUT
CC: CC_File_Send
Receiver: BS_XI
Interface: MT_File_ABS (Split)
CC:CC_SOAP_Rec
Message send one to one.
Sender: BS_XI
Interface:MT_File_ABS (Split)
CC: CC_SOAP_Send
Receiver: BS_SAP
Interface:MT_File_IN
CC: CC_Proxy_Rec
In Communication channel SOAP Adapter Receiver returns the following error:
SYSTEM_NOT_CONFIGURED_AS_XMB
I have check all configurations and it seems ok.
Please, could somebody help me? Thanks.
Gemma

Hello Gamma,
go thru the below threads might help
SYSTEM_NOT_CONFIGURED_AS_XMB
FTP2IDoc - SYSTEM_NOT_CONFIGURED_AS_XMB
SYSTEM_NOT_CONFIGURED_AS_XMB Error
Cheers
Agasthuri Doss

Receiver SOAP Adapter Problem-HTTP 401 Unauthorized

We are using XI-7.0. We have scenario IDOC >> XI >> SOAP by making asynchornous call.
Vendor has two web server - A and B. Both the servers set up are identical in the vendor system.
Web server "A" works fine from XML spy tool as well as XI for sending service order SOAP messages.
Web server "B", we are able to send SOAP messages from XML spy successfully and vendor also confirms that it updates database in their system.
But we are not able to send SOAP messages from XI on Server "B". We are getting following error message in the adpter engine.
Can someone please help me? Thanks!
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized.
Thanks!
MP

Hi Riya,
For SSL configuration you can check,
Rajendra's blog http://scn.sap.com/people/rajendra.badi/blog/2011/11/23/pi-711-transport-level-secuirty-communicating-with-external-web-service-from-soap-adapter-through-ssl
Khade's blog http://scn.sap.com/people/s.khade/blog/2011/09/06/secured-connection-to-external-web-service-using-sap-xipi.
Regards.

XI Soap Adapter problem

Hello all, I have the following scenario:
Web Service -> XI -> ECC
This of course is using the SOAP adapter and the IDoc adapter. My configuration looks good, the testing tools all verify that it's set up correctly. Something is not working correctly. When I post a purchase order from the web service I am asked to log in (normal) and after entering credentials I receive an error:
<faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
 <context>XIAdapter</context>
 <code>MalformedMessageException</code>
 <text><![CDATA[
com.sap.aii.messaging.mo.MalformedMessageException: No SOAP Envelope but 1 ProcessPurchaseOrder
 at com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1048)
 at com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:620)
 at com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:612)
 at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:380)
 at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:387)
 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: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(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>
I'm not sure what to make out of this. It looks as though the web service is connecting to the SOAP adapter, but if I go to transaction SXMB_MONI there are no messages, so apparently the message isn't reaching the SOAP adapter correctly. I'm using the following url:
http://server:port/XISOAPAdapter/MessageServlet?channel:wosdev_pws:PO_Sender
Where wosdev_pws = the business system I attached as service without party
and where PO_Sender = communication channel for SOAP adapter configuration
Perhaps I have misunderstood the SOAP adapter and misconfigured it. Is that web address correct?

Harriosn,
The url http://server:port/XISOAPAdapter/MessageServlet?channel:wosdev_pws:PO_Sender is incorrect. Instead you use this and check once again:
http://server:port/XISOAPAdapter/MessageServlet?channel=:wosdev_pws:PO_Sender
---Satish

Receiver SOAP Adapter Problem-soap fault: Server did not recognize the valu

I have a scenario for service orders using async call : IDOC-XI-SOAP.
I used the XML Spy tool to test the Service order's web services and it works fine. I imported the same WSDL file in XI. When I send a SOAP message from XI, I get a following error in the adapter engine.
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: AddUpdateCostObjectLevel1.
Can someone please help me...
Thanks in advance!
Mrudula

This problem is resolved by me by passing the "http://company's URL/AddUpdateCostObjectLevel1" in the SOAP action.
Thanks to all for your input.
Mrudula

Receiver SOAP adapter problem

Hi,
I am getting the following error in moni when i try to consume a webservice. Even SOAP scenarios that were working fine before also are throwing the same error.I have checked some threads regarding the same error and did as mentioned in the same, but of no use. I executed that webservice alone and it is working fine. Any help on this will be appreciated.
<?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: invalid content type for SOAP: TEXT/PLAIN</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Sudheer.

Hi Sudheer,
Let me confirm again...From XI , you are making a SOAP call using the SOAP receiver adapter..right ?
If that is the case and you are telling sometimes it works and sometimes it doesnot, it indicates the SOAP service you are invoking from XI due to some reason is sending back non-soap response...
we had encountered scenarios couple of time like this because the user we were using to execute the SOAP call had expired and the SOAP service was returning and HTTP-UNauthorized message back and then in MONI it would show up as the same error as what your are getting.
To check this, (the request/response going back and forth), in my earlier post i suggested using the TCP gateway...
Thanks.

Problem with SOAP Adapter receiver not receiving the proper string

Hi friends
I have a very simple scenario as follows using SOAP Syncronous Call
SENDING SCENARIO
================
ExternalClient --> SOAP ADAPTER --> XI -> RFC ADAPTER --> ZBAPI
RECEIVING SCENARIO
==================
ZBAPI --> RFC ADAPTER --> XI --> SOAP ADAPTER --> ExternalClient
Here External Client is sending a search ID and ZBAPI searches for that record and send the FirstName and LastName.
I am using external Definitions in XSD format as follows.
INPUT XSD is
=========================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://cincom.com/xi/socrates/customerSearch" targetNamespace="http://cincom.com/xi/socrates/customerSearch">
 <xsd:element name="ZBAPI_GET_NAME">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ID" type="xsd:integer" minOccurs="0" />
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
===========================================
Reciving XSD file has
==============================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:socrates.cincom.com" targetNamespace="urn:socrates.cincom.com">
 <xsd:element name="ZBAPI_GET_NAME_RESPONSE">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ADDRESSDATA" minOccurs="0">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="FNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
=========================================================
I HAVE TESTED THE ZBAPI AND IT WORKS WELL ON ITS OWN. ALSO I HAVE TESTED THAT THE MESSAGE SENT FROM OUTSIDE CLIENT IS REACHING BAPI. HOWEVER WHEN I GOTO 'SXMB_MONI' AND CHECK THE
XML STRING THAT THE RECIEVER IS GETTING, I SEE JUST THE FOLLOWING TWO LINES
===================================
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:ZBAPI_GET_NAME_RESPONSE xmlns:ns1="urn:socrates.cincom.com" />
======================================
IF YOU NEED ANY FURTHER INFO, PLEASE LET ME KNOW.
HOPE SOME ONE CAN GUIDE ME WITH THIS PROBLEM.
THANKS IN ADVANCE
RAM

Ram
Can you pls. confirm whether the mapping of your XSD fields & BAPI fields are in same sequence. I mean hierarchy is same or not.
Just to verify, as you said you are using Sync scenario that means you are using ONE Sender Soap & ONE Reciever RFC adapter.
Regards
Lalit

PI 7.1 problems publishing a WSDL of a sender soap adapter

We have upgraded our dev system from XI 3.0 to PI 7.1 and now I'm facing a problem with SOAP adapter. I have searched for answers here for a while but couldnu2019t find them. That why I start an own thread.
I thought with PI 7.1 it is very easy to publish the WSDL of SOAP adapter respectively a sender agreement. All you have to do is to choose your sender agreement and select the menu item "display WSDL" There you can get the WSDL and a WSDL URL. So it would be possible to deliver this URL to my partners. But while checking this URL respectively the delivered WSDL I've found a problem.
First of all the the WSDL URL doesn't look really good:
http://<server>:<port>/dir/wsdl?p=1_1ce2e954fe9632818bfff6c32f370748_portTypeBindingService
But it works. If I call this URL with a browser or with XML Spy I get the correct WSDL. Any chance to get a better readable URL?
The next thing is the proposed soap:address location in the WSDL. It has the following form:
http://<server>:<port>/XISOAPAdapter/MessageServlet?senderParty=&senderService=MYSERVICE&receiverParty=&receiverService=&interface=MYINTERFACE&interfaceNamespace=MYNAMESPACE"
If I compare it with the documentation i can see that the URL is completely different.
http://help.sap.com/saphelp_nwpi71/helpdata/en/43/951aceb1146353e10000000a11466f/frameset.htm
But again if it works all is fine but it doesn't work at least it doesnt work with XML Spy. The reason is the use of "& a m p ;" instead of only "&".
If I create a SOAP request with XML Spy an sent it to the XI I get the following error message: " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=null;AN=null;ANS=null;"
But if I change the SOAP request parameters replacing all the "& a m p ;" with "&" then it works.
Any chance to manage this? If I provide a WSDL on this way I want that my partners can use this "out of the box"

Kulwant
Yes of course I can change that manually but therefore I have to save the WSDL to my local hard disc, change the WSDL and send it to my partner via mail. This is exactly the way I've done this till now. But with PI 7.1 I like to use the new opportunities.
Bhavesh
I have also no Service Repository till now. That's the reason why I want to use the way described in my initial post.
In PI 7.1 you can open the corresponding sender agreement of you SOAP adapter. There you find a menu item "display WSDL". If you choose this you get a window which displays the correct WSDL and an URL where you can find the WSDL too. If you copy this URL to a browser you get the same WSDL too.
http://help.sap.com/saphelp_nwpi71/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm
First part of my question is regarding to this URL. The URL has a strange format.
The second part is regarding to the form of soap:address in this generated WSDL. Here I have problems with the use of this "& a m p ;" string. But I have no influence on it. If I deliver my partners the obove mentioned URL to the WSDL and the WSDL contains this soap:address URL my partner will probably have the same problem like I with my XML Spy.
Gaurav
I don't understand you answer. I know the correct soap address but the IB tool generates it with this "& a m p ;" string instead of only "&". Thatu2019s the point. No idea if and how I can handle this.
But thank you for the note number. Was helpful. The number is in the online documentation too but I've read over it.
To bad that the online documentation isn't correct regarding to the soap address. But believe me the German version is even worse. There you can find the two soap adapter settings (XI parameter: interface namespace, interface) that are no longer existed in PI 7.1
Now I will test if a .NET application can handle this soap address correctly.
Edited by: Gil Ritter on Nov 14, 2008 11:25 AM

SOAP Receiver Adapter problem (client certificate required)

My Scenario is similar to described in https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3721. [original link is broken] [original link is broken] [original link is broken] I have two PI servers running on one machine. I am trying to post message HTTPS with Client authentication via SOAP adapter from one PI system to SOAP adapter of other PI server. I have done the following configuration.
PI Server AXD - (Client) - Receiver SOAP adapter
PI Server AXQ - (Server) - Sender SOAP Adapter.
Steps in AXD
1. I have created a certificate of AXD in the service_ssl view of key storage.
2. I have imported the AXQ public certificate in to AXD in the TrustedCAs of Key storage
Steps in AXQ
1. I have created a certificate of AXQ in the service_ssl view of key storage.
2. I have imported the AXD public certificate in to AXQ in the TrustedCAs of Key storage.
3. I have created a user in AXQ and assigned the certificate of AXD under usermangement in Security provider to this user.
4. I have added the AXD certificate under Client Authentication tab with require client certificate option checked in the SSL Provider.
5. I have assigned the user created in AXQ in the step above to the Sender Agreement.
Now when I post message from AXD with Configure Client Authentication checked (Here I have selected the certificate of AXD and view as service_ssl) I am getting the following error.
Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:884) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3
Any pointer to solve this problem is highly appreciated.
Thanks
Abinash

Hi Hemant,
I have couple of questions. Why do we need to import certificate for SOAP WS-Security and from where I can get it?
As far as my scenario goes I am not using message level security.
Secondly what do you mean by TRUSTED/WebServiceSecurity? I don't see any such view inside the Key Storage. I can see a view named just WebServiceSecuity though.
Also I don't have a decentralized adapter installation rather I have two separate PI instances having their own central adapter engine.
Abinash

SOAP Receiver Adapter problem

Hi guys,
I have problem with ABAP Proxy->XI->SOAP scenario. I send data from R/3 via Proxy. I see in the monitor, that message has been processed successfully, however, the SOAP adapter does not send this message to the target. I tried to run a listener on on my local machine on port 80 and sent data from SAP. Again, in monitor successful, but no action in the listener - the message did not arrive. (the adapter was set up to send data to ma local PC). The scenario is async.
Any idea, what could be wrong?
In the receiver SOAP adapter - hoe to set up Target URL? http://<machine>:<port> or w/o port and it is automatically sent to port 80?
Thanx for answers!
Olain.

Hi guys, thanx for answers..
All the systems are in the local network, so no proxy is there. However, in the communication channel monitoring I get error: connection timed out , can be due to invalid adress.. However, If i try to reach the WS from the SOAPui tool, this web service works...
Any other idea?
Olian

Problems using access control in sender agreement for SOAP adapter 7.1

I am trying to use Access Control Lists to restrict user access to web services/interfaces which are exposed via PI. This can be configured via the Integration Builder Directory using the u201CAssigned Usersu201D tab of both Communication Components (Business System) and Sender Agreements.
The configuration is via the above mentioned components. However, I understand that itu2019s the adapters which at runtime are responsible for actually applying these checks.
I have been having problems getting the access control to work using a setup involving a SOAP adapter of type SAP BASIS 7.10.
The symptom of the problem is that although the access control works as expected at the Business System level, any settings at the Sender Agreement level appear to have absolutely no effect whatsoever.
I have confirmed that I have no problems if I use an adapter of type SAP BASIS 7.00. However, I really need to get this working on 7.1.
I have looked on the SAP support portal but can not find any notes that relate to this.
Has anyone else had a similar problem? And have you found a fix for it?
Any suggestions would be welcome.
Edited by: Malcolm Dingle on Jun 17, 2009 1:08 PM

Hi Shai,
Please have a look at the following link and see if it helps you .
It deals with SOAP adapter installation and activation
Re: SOAP adapter installation and activation
Best Regards
Edited by: Prakash Bhatia on May 8, 2009 11:51 AM

SOAP adapter problems

Similar Messages

Maybe you are looking for