Help in SOAP to SOAP scenario

Hi..
can anyone give me a clear idea or if u already have any blogs which will give me a detailed information about a Soap to soap scenario and how will it be possible to handle errors. help me out in understanding a SOAP scenario.
reward points if useful
Thanks
Deepika

hi,
Receiver SOAP Adapter
The receiver SOAP adapter connects XI with an external Web service. To call the Web
service, you need to define a message interface that represents the structure of the
request and response of the Web service. You can create this message interface easily
with the help of a WSDL file that represents the Web service. If this is not possible, you must create the message interface based on data types.
Uploading the WSDL
Since the WSDL describes the message interface, you upload the WSDL into the
Integration Repository. Go to your Software Component Version and open the required
Namespace. Create an External Definition.
In the external definition object, choose Category wsdl and click Import external
definitions.After importing the WSDL file, you can view the included messages on the Messages tab page:
The namespaces of the messages are part of the WSDL description and can
differ from the namespace of the external definition object.
Now you can create a message interface corresponding to the message types from the external definition. You need the message interface for routing the message to the Web service.
In the message interface object, select the message types of the external definition
object by using the input help.
After assigning the output and input message, save and activate your work. Now you can use the message interface for routing and mapping.
Creating a Message Interface Without WSDL
For some scenarios it is not possible to provide a WSDL file. In this case you need to create a message interface according to the message structure of the server. The best way to achieve this is by using an example SOAP message for the request and the response message.
Since the SOAP adapter creates the SOAP envelope you have to extract the SOAP
body. Usually, Web services ignore declarative attributes (xsi:type), therefore you can delete them. The namespace declaration of the root tag must be applied. The XI
message payload should be the following message.
Create a data type, message type, and message interface according to this structure. In the message type, apply the correct name and namespace of the message.
Creating a SOAP Receiver Channel
To call the Web service, you create a communication channel with type SOAP and
direction receiver in the Integration Directory. The obligatory parameters in the
configuration are Target URL and SOAP action. You get the values you have to enter
here from the WSDL file.
You find the target URL at the tag soap:address and the SOAP action at the tag
soap:operation.
If more than one message type is described in the WSDL, several SOAP actions
might also be defined. Check for the correct operation name. If no SOAP action is
defined in the WSDL, you can leave the parameter in the receiver channel empty.
For the receiver SOAP adapter you need at least the following parameters.
If the Web service is outside your system landscape and you need to address a proxy server, select the Configure Proxy checkbox and fill in the corresponding fields.
soap to soap scenario
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
sap to webservice
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
This might help you to get more picture on SOAP
Check these
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
For more details on SOAP..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79c
Thanks,
Vijaya

Similar Messages

HTTP to SOAP scenario, help needed.

Hi friendz,
I am tyring to do HTTP 2 Soap scenario, so can any one tell me how to download "wsdl" file 
i know how to import an existing wsdl file, but i want to know how we ll download, the file from webservices. i hope u understood my question.
If possible , can any one send me the entire steps for the above scenario, please send me the pdf file to my email: [email protected]
regards,
Satish.

so, you are going to consume webservice. First use the wsdl url in the browser and save the content as a file. After saving, go to ESR , use external definition tab and save over there. In IR, at the soap receiver side you have to configure target URL and user credentials over there.
If you have more questions, Please let us know. Hope I answered your question

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

File to SOAP Scenario Using BPM

Hi,
I am doing File to SOAP scenario using BPM.
while doing Integration Process in IR, i got the following error message
"Expression of simple type xsd:string expected"
But i have given xsd:string in the correlation element as well as in Data types.
I dont know why it is getting the error.
could you anyone please help me to sort out?
Regards,
Sai Ch.

Hey,
Check in the correlation editor, where you define the condition.
Whether the data type of the XPath is string and whether it matches with the data type of the messages that you have selected.also make sure the type of the correlation variable is string.
regards,
Milan

Problem in IDOC to SOAP Scenario

Hi All,
we have an IDOC to SOAP scenario in which we have got WSDL from the client for the targets.. Please let us know the WSDL would be the message type and we need to create interface for it . Also the SOAP header is not appearing in the target xml.
Thanks

Hi ,
This means when the data is sent to the webservice it will contain the SOAP header just that we cannot see it in Moni . Also
What about the acknowledgement . Our message is successfull but with message that awaiting acknowledgement.
What we basically need a synchronous scenario of IDOC to SOAP but the response not going back to SAP-R3 . We recieve the response only in SAP-PI. Saw some blogs but the message is going back to SAP-R3. Please help us on this
Thanks
Edited by: vishal gadkari on Aug 22, 2009 4:15 PM

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Error in synchronous( abap proxy to soap)scenario

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
configuration steps are
1. only client proxy to soap scenario I have done.
communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
Already we have RFC destination connection and connection type H for proxy to xi.
1.Is it required RFC destination connection for xi to server proxy.
2.Is it required receiver proxy communication channel for server proxy?.
i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
error is:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
Kindly help me.
advance thanks
thanks and regards
elton
Edited by: eltonsaranya on May 9, 2011 10:27 AM

Your exception message shows problem at the webservice side.
Check the following:
a) you need two mappings one for proxy req to soap request and other soap response to proxy response
b) You need to create service interfaces both sender and receiver synchronous .
c) communication channel QOS is best effort for both sender and receiver
d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
f) See your SOAP response structure matches with WSDL provided.
g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI for that web service. So that you know whether problem exists on the target system or not.
Hope that helps.

RFC to SOAP Scenario error

Hello ALL
I am trying to working in RFC to SOAP scenario in sap pi 7.31 single stack system.with help of blog **************** - Scenario on RFC to SOAP
i am trying to pass input values from ECC through RFC to web service .
while sending data using function module from ECC system i got following error
thnx in advance

Hi Ganesh,
are you getting any error is SM58? Please check the below blog for configuration
Michal's PI tips: How do you activate ABAP Proxies with AEX - simplified version
IDOC_AAE To File with all Configurations
the below discussion will be useful
RFC to FILE(7.3) single stack

Rfc to soap scenarios

hi expects ,
can any body send me the rfc to soap scenarios examples.please help me.

Hi Santosh,
Check the following link.. hope it will help u..
Configuring the Synchronous scenario in XI
Regards,
Rohit.
Reward points if helpful.

RFC TO SOAP SCENARIO

Dear Experts,
I am facing the Following error for RFC to SOAP Scenario, i Tried
1. Full Cache Refresh
2.Delete and create Sender Agreement Again
3.Specifying the Program id Again
yet the Scenario is not Working, could you please help me in Resolving this at the Earliest
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'ISU64', toParty '', toService '', interface 'YGVK_SEND_WS_TO_WS', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_YGVK_SENDER_WS_TO_WS' (channelId f1219fd41be734a2a72cd3ddcb779475)
Regards,
Vijay Karthik G

Hi,
copy the sender agreement to the same one but in party field
remove the " * " (it has to be empty)
test it and let me know
Regards,
Michal Krawczyk

File to SOAP scenario question???

Hi,experts
let's take source system is A,target system is B.
I have a File to soap scenario using BPM,the scenario is send file request(from A) to PI,PI will be communicating target system(B) with soap(syn).After that, PI receives the soap response and send the response data to A.
Now the requirement is, we need to archive the file request msg(before sending to B) to a folder and archive the response msg(response from B) to a folder as well.how could it be achived?
any help will be much appreciated!
Thanks

Hello Rajesh_V2009 ,
I am trying to implement exactly the same pi scenario, but having some problems :
File -> file adapter -> ccBPM -> soap receiver adapter -> web service request -> web service response -> ccBPM -> output file adapter.
The web service that I call works file from wsnavigator. I have created all the design and configuration objects
needed for the scenario.
I place a file with following contents:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<pns:GetSetNameWS xmlns:pns="urn:file2soap2fileWSVi">
<pns:name1>ajeet</pns:name1>
<pns:name2>phadnis</pns:name2>
</pns:GetSetNameWS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I look at the process monitor I get this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have no clue about this error. Can you help me with this ?
If yes I can send you more details, if you liked 
Hoping to get help from you,
Cheers,
Ajeet Phadnis

RFC-to-SOAP-Scenario: XIServer:NO_MAPPINGPROGRAM_FOUND

Hey guys,
We've implemented in SAP PI 7.11 a RFC-to-SOAP-Scenario. The whole scenario is sync. WSDL and RFC are imported objects.
Now we're going on to test in backend and call the related remote function module via se37.
The error message is (from xsmb_moni)::
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What we've already done:
-> Cache refresh
-> server restart
-> soap fault mapping
-> dummy changes
-> mapping is available in sxi_cache
-> function module is not dumping in backend
Any ideas how we can go futher with this?
Thank you very much and greetings,
Stefan

FYI...
Apparently, this error message can sometimes be misleading.
I found in another thread that this message came after a short dump in the ABAP function. After viewing ST22 in our backend system I noticed short dumps corresponding to the times when I make the SOAP call.
[NO_MAPPINGPROGRAM_FOUND SOAP RFC Adapter]
We can call SE37 with the same parameters and there is no ABAP error. So the search for root cause continues, but maybe this info will help someone.
-Aaron

SOAP to SOAP scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario?
Mainly need info for Receiver SOAP Adapter...
Any document for the same?
Regards
Sara

Hi,
Receiver SOAP Adapter
The receiver SOAP adapter connects XI with an external Web service. To call the Web
service, you need to define a message interface that represents the structure of the
request and response of the Web service. You can create this message interface easily
with the help of a WSDL file that represents the Web service. If this is not possible, you must create the message interface based on data types.
- Uploading the WSDL
Since the WSDL describes the message interface, you upload the WSDL into the
Integration Repository. Go to your Software Component Version and open the required
Namespace. Create an External Definition.
In the external definition object, choose Category wsdl and click Import external
definitions.After importing the WSDL file, you can view the included messages on the Messages tab page:
The namespaces of the messages are part of the WSDL description and can
differ from the namespace of the external definition object.
Now you can create a message interface corresponding to the message types from the external definition. You need the message interface for routing the message to the Web service.
In the message interface object, select the message types of the external definition
object by using the input help.
After assigning the output and input message, save and activate your work. Now you can use the message interface for routing and mapping.
Creating a Message Interface Without WSDL
For some scenarios it is not possible to provide a WSDL file. In this case you need to create a message interface according to the message structure of the server. The best way to achieve this is by using an example SOAP message for the request and the response message.
Since the SOAP adapter creates the SOAP envelope you have to extract the SOAP
body. Usually, Web services ignore declarative attributes (xsi:type), therefore you can delete them. The namespace declaration of the root tag must be applied. The XI
message payload should be the following message.
Create a data type, message type, and message interface according to this structure. In the message type, apply the correct name and namespace of the message.
Creating a SOAP Receiver Channel
To call the Web service, you create a communication channel with type SOAP and
direction receiver in the Integration Directory. The obligatory parameters in the
configuration are Target URL and SOAP action. You get the values you have to enter
here from the WSDL file.
You find the target URL at the tag soap:address and the SOAP action at the tag
soap:operation.
If more than one message type is described in the WSDL, several SOAP actions
might also be defined. Check for the correct operation name. If no SOAP action is
defined in the WSDL, you can leave the parameter in the receiver channel empty.
For the receiver SOAP adapter you need at least the following parameters.
If the Web service is outside your system landscape and you need to address a proxy server, select the Configure Proxy checkbox and fill in the corresponding fields.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

Problem with SOAP Scenario

Hi,
I am trying a http to soap scenario.
In the receiver soap adapter, I have specified the following:
Target url: http://test.abc.com/
Action: handleLogin()
When I send the request, I get a "time out error" as the response in the http client tool.
However, in sxi_monitor, I get a webpage as the response(A web page is being displayed in the monitor).
What I was expecting is a response message that matches the wsdl.
I have tried using "" and a blank value for the Action field in the soap adapter, but no luck.
Any help would be appreciated.
Thanks,
Smitha.

Hi Shabarish,
Thanks for your response.
I provided the operation name in the soap adapter as specified in the blog, but I am getting a http_adapter exception. (500 internal server error)
Any clues?
Thanks,
Smitha.

HTTP 401 Unauthorized, error in proxy to SOAP Scenario

Hi all,
We got the below error in our proxy to SOAP Scenario.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
We configured User Authentication,Proxy and Proxy User Authentication for the Receiver Communication Channel correctly still we are getting this error.
So please let me know what could be the possible reasons behind it and how to resolve it.
Waiting for your valuable response.

Hi,
Consider the parameters connection pool size and connection wait time:
ume.r3.connection.master.poolmaxsize
ume.r3.connection.master.poolmaxwait
These parameters are described in the note below:
#821026 - AdapterEngine messaging URL returns HTTP 401 under high load
Also, ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Please kindly check the note below:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Regards,
Caio Cagnani

Help in SOAP to SOAP scenario

Similar Messages

Maybe you are looking for