SOAP scenario (WSDL)

Hi ALL
I need to approach for below scenario .
   SOAP - XI - RFC
CASE 1.
Sender
    2 Business services ( a. Development Service third party b. Quality Service Third party)
    1. SAP XI/PI system ( Only 1 SAP -XI/PI system Both Development & Quality are in same system)
    2. Business system ( a. ECC Development system b. ECC Quality system
   My question : Do i need to provide 2 WSDL to 2 Business services or Do I need to provide single WSDL for Both Services .
                          If it is single WSDL is there any conflicts for response message.
CASE 2.
    1 Business services ( Only one system for Development / Quality for third party)
    1. SAP XI/PI system ( Only 1 SAP -XI/PI system Both Development & Quality are in same system)
    2. Business system ( a. ECC Development system b. ECC Quality system
   My question : How do system identify from which Service data has been trigger .
Please suggest me on CASE1 & CASE2 .
Thanks in Advance.
Regards
Ravi

CASE 1.
Since you deal with one sap PI system, you just need one wsdl and that can be shared for both develop and quality third party sender system.
CASE 2.
> create a field in the structure that provides key value to determine dev or Quality. Using context value in the receiver determination decides the target system.

Similar Messages

RFC to SOAP Scenario - WSDL-Import really needed?

Hey @all,
we like to feed a webservice via SAP Backend. As middleware we use SAP PI 7.1.
The planned scenario is RFC to SOAP. The wsdl of webservice (NON-SAP) has no filled soapAction-Parameter and the operation with name "process" occures three times in it with the same name, but each operation "process" has it's own Request / method (axis), like "Request1", "Request2", "Request3". Each request has it's own response.
In this case it is not possible to import the wsdl as external references correctly - the import gaves an error caused of the identical names of the three operation-parameters.
The question is:
Is it possible to work this out without the import of wsdl and without soapAction-Parameter?
How could we call the correct operation?
Thanks very much in advance,
Stefan

Hi,
Maybe you could try to editing the WSDL and import it three times e.g for process (1) here is the WSDL (1) --> Make sure you delete the other process.
Make message mapping for each process and its corresponding response. So that would be, 6 message mappings (request and response) and 3 operation mappings.
In Integration Directory, call the correct operation in Interface Determination by using xPath.
http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination
although the blog above is for receiver determination, the xPath conditions for interface determination are the same.
For the without SOAP Action parameter, I guess it is okay to leave blank. I have not used the SOAP Axis though (I used the PLAIN_HTTP adapter for that). Just to be sure, test it in SOAP UI.
Hope this helps,
Mark

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

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

IDOC to SOAP scenario and transport process

Scenario:-IDOC to SOAP:
We got the WSDl file from Target system and our current scenario is working perfectly fine in Dev.
Requirement:
I have to send the same IDOC to two different SOAP target system with different SOAP URL WSDL structure is same only the URl differ.
Solutions which I thought of:
1) Separate Design for both the scenarios in IR and one CS with two SOAP channel, interface and receiver determination and agreement.
2) Use the same WSDL file structure for both the case. this will avoid the separate IR configuration. in this case there will be common MM,IM. In ID the configuration will remain the same as the case one.
In 2 case I would like to know whether I can use the WSDL file which has the details of first SOAP target for the second SOAP target. Will this WSDL file act simply as structure? Does the URL mentioned in the WSDL file will create any problem?
Transport process:
SOAP WSDL file has different URL for DEV,QA and PROD. when I transport the IR from Dev to QA the Dev WSDl file will be reflected in QA as external definition, I wanted to know what is the best method to do the transport in the above situation.
Solution which I thought of
1) Go to QA IR and import the QA WSDL file.
2) Go to Dev and import the WSDl file of QA and import it in QA which avoids manual import in QA, if I go by this way will this affect the testing of my interfaces in Dev system.
What is the best method we do the transport for the above scenario.
Need ur suggestions?
chirag
Edited by: Chirag Gohil on Oct 1, 2008 1:29 PM

Hi Chirag,
As far as i know there wil not be any target URL in the WSDL File which we bought from the webservice application.
Can u please paste the WSDL File which u have .....
If we come to Dynamic URL Config means, as per my concern
You have only 2 Target locations to receive the Idoc. so its better to go a head with ur existing approch itself.
Why becase for Dynamic URL Config.....
we have to maintain the target URL's in One Table and need to use RFC lookup to pick this URL Dynamically based on some value from the Input file.
And also we need to use Standard UDF code for Dynamic config in Mapping .
And need to check the option Use ASMA in the Receiver SOAP CC.
Regards
Seshagiri

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.

Soap action: in Proxy to soap scenario

Hi experts,
I have a senario of Proxy to webservices.
I have imported the wsdl file as external defination, and have to use two message inside 1) to Insert 2) To Update.
Now proxy will run twice a month with same data structure,
I have to do insert action first and 2nd time Update.
I have only one receiver. So How to achive this in communication channel >> Soap Action.
1> Is is possible to provide two Soap action in a single communication channel.?
2> do i need to create 2 mapping and two interface ? My Source coming from Proxy is with one structure.
Regards,
Sumit Gupta

>
sumit gupta wrote:
> Hi experts,
>
> I have a senario of Proxy to webservices.
>
> I have imported the wsdl file as external defination, and have to use two message inside 1) to Insert 2) To Update.
>
> Now proxy will run twice a month with same data structure,
>
> I have to do insert action first and 2nd time Update.
>
> I have only one receiver. So How to achive this in communication channel >> Soap Action.
> 1> Is is possible to provide two Soap action in a single communication channel.?
> 2> do i need to create 2 mapping and two interface ? My Source coming from Proxy is with one structure.
>
> Regards,
>
> Sumit Gupta
You can either go for dynamic configuration and configure the action or you can go for two different Communication channels with separate actions.
In the proxy use a field as an indicator for the required action i.e INSERT or UPDATE and based on XPATH in your interface determination call the required channel or in case you are using a single channel create the dynamic action in your mapping based on that field.
Ref:
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/suraj.sr/blog/2006/01/05/multiple-inbound-interfaces-within-a-service
/people/shabarish.vijayakumar/blog/2009/03/26/dynamic-configuration-vs-variable-substitution--the-ultimate-battle-for-the-file-name

Idoc to soap scenario - soap response error

hi
i am using pi 731 single stack.
the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
the message is failing in mesage monitor and communication channel monitor. error is -
Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
This scenario is async scenario. How to soap remove this response message error.
rgds

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

Sync File to SOAP scenario

Hey guys
i m doing a Sycn FIle to SOAP scenario(i guess i need BPM for that,right?)
lemme know if my configuration is correct
For sender FIle:
DT_sender,MT_sender,MI_sender,AI_sender(async)
For SOAP
DT_soap,MT_soap,MI_soap,AI_soap(sync)
For Receiver file
DT_receiver,MT_receiver,MI_receiver,AI_receiver.
and BPM would be
start>>Receive>>Sync send>>send>>stop
and ofcourse i need to import the WSDL for the webservice.
is this all,or i need to do some other designing too?
thanx
ahmad

Ahmad,
The weblog says you are sending a request from R3 using RFC. Then it gives back you the response from the webservice.
So first you have two scenarios:
Request:
Source: No datatype needed because you are importing the RFC.
Target: For this you need the datatype. Just create the datatype what he has mentioned.
Response:
Source : Just copy and paste the xsd. You import as an external definiton.
Target: Since your RFC is a synchrounous you will have the response for it. That is your target.
Then after that you do message mappings for request and response and then the interface mapping.
You dont need to have BPM for this interface. So dont worry about BPM for this interface.
Then you complete all the steps given in his weblog2. Then test it out.
---Satish

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 to SOAP scenario error

Hi guys,
I have developed an HTTP to SOAP scenario, in order to invoke a Web Service.
I am trying to test the scenario by using an HTTP client.
However, I am getting the following message, in the result:
Result:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Pipeline specified in URL attribute (type) not existing</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code><SAP:P1>/sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&interface=GetStockQuote_Sync_OB&service=HTML_Service&party=&agency=&scheme=&QOS=BE&sap-user=xiappluser&sap-password=++++&sap-client=100&sap-language=EN</SAP:P1><SAP:P2>ENTRYNAMESPACE=HTTP%3A//FAMAR.GR%3ADEMOS</SAP:P2><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Pipeline ID ENTRYNAMESPACE=HTTP%3A//FAMAR.GR%3ADEMOS which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&amp;interface=GetStockQuote_Sync_OB&amp;service=HTML_Service&amp;party=&amp;agency=&amp;scheme=&amp;QOS=BE&amp;sap-user=xiappluser&amp;sap-password=++++&amp;sap-client=100&amp;sap-language=EN)
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Do you have any ideas?
Also, I am not able to see in SXMB_MONI the messages that are generated.
This is only possible in Message Monitoring in RWB.
Thank you
Evaggelos

Hi Evaggelos,
The URL you used to generate the WSDL for your webservice is wrong:
URL = /sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&interface=GetStockQuote_Sync_OB&service=HTML_Service&party=&agency=&scheme=&QOS=BE&sap-user=xiappluser&sap-password=+++++&sap-client=100&sap-language=EN
It should be of the type:
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>
Thanks,
Varun

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

SOAP scenario (WSDL)

Similar Messages

Maybe you are looking for