SOAP Sender Steps

Hi,
i was trying this Scenario
WebService <> XI <> RFC (BAPI)
A WebService which is already defined, used to Create PO in R/3 System and get confirmation Number as Response back. It Totally Sync Scenario. I am using Z_BAPI_POrder_Insert
I just summerized the Steps to follow, before start working on the system, Help i need is to CORRECT MY STEPS, where i did Wrong and Add steps which i missed.
Procedure
In R/3
1.Create RFC Destination in R/3 to XI System of Type TCP/IP with ProgramID option
in I.R
2.Import RFC Z_BAPI_POrder_Insert
3.Import WSDL into External Definitions
4.Create Message Mappings (Two Required)
5.Create Interface Mapping (One)
6.Activate I.R
I.D >>
7.Create Scenario
8.Assign Business Systems
9.Create Sender Comm Channel
SOAP
Default Interface Namespace
Default Interface Name
10.Create Receiver Comm Channel
RFC
Application System
System Number
R/3 Login Details
11.Create Sender Agreement, Receiver Determination, Interface Determination and Receiver Agreement.
Hope will give a clear reply, with out LINKS.
Thanks
Seshu

Just make sure of the follwoing,
1. You have 2 message mappings and 1 interface mapping. This interface mapping will be used to map SOAP req to RFC req and Rfc res to SOAP response.
for info on how to use a SOAP adapter as a Sender and to use XML spy to send a SOAP message to triiger your scenario,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
REgards,
Bhavesh

Similar Messages

File BPM Webservice IDOC .........Error in BPM workflow(Sync send step)

Hi all,
I have the same type scenario that is file initiates the bpm that invokes the Webservice.the file data goes into bpm as the input data of the webservice and webservice gives the response and then the web-service response is mapped to
idoc and finally posted to R/3.
The interface sI created:
1.outbound Async -
>for file
2. Abstract async----
>bpm reciever step.
3.Abstract sync----
>bpm sync send step.
4.inbound sync -
>for the webservice to recieve the reqst and to send the response to Abstract sync
5.Abstract async----
>to send the data out of BPM
6.inbound async----
for idoc
created 3 communication channel.
1.file adapter: sender
2.SOAP adapter: Recv
3.IDOC adapter: Recv
created 3 reciever determination
Business process instance in ID
reciever agreement(2)
interface determaination
But getting a problem in BPM.
I think the scenario is logically correct as I have seen previous
SDN suggestions.
But getting the problem in BPM's sync step.and the SOAP rec channel is also inactive.in BPM workflow I can see the recv step is getting file req data but after that in the sync send step
its stuck up.getting error.
Please sir suggest me.

Remove the interface you created for Idoc that is inbound async one. use the imported Idoc itself as the interface and also as the message type. Everything else looks good though i did not really evaluate ur ID configuration..
VJ

BPM synchronous send step - Fault message extraction

Hello Experts,
I am developing a BPM with Asynch RFC -> synch Webservice -> Asynch RFC scenario.
I have defined fault message in the synchronous interface used in the send step for web service, and also defined
exception branch where an alert is thrown.
In the alert, i want to send the fault text from the fault message. How can i do that??
Thanks

Hi Mona,
SOAP adapter doesnt support fault messages.
check stephan's reply @ How catch the SOAP Fault Message ?
> SOAP adapter does not support fault message.
> Any fault is treated as error.
> fault messages are only supported for XI messages (ABAP or Java proxies) and RFCs.
Fault message handling is not possible inside BPM.

Error in send step in BPM

Hello,
I ehanced an existing BPM where a send step sends data to a J2EE system. I inserted a switch and put the existing send step to one branche and a new send step to the otherweise-branche. The new send step interrupt with an error:
No exception defined for fault message hostname http://xml.apache.org/axis/
But there is an exception branche defined. An idea what's the problem?
I didn't define a message called hostname, so where he got this name from?
thx
chris

No, everything seems fine.
Here is the payload of response :

<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Help Need on SOAP (Sender) to RFC Scenario(Synchronous Communication)

Hi All
I have a requirement of SOAP(Sender) to RFC scenario(Syncronous Communication). The scenaio goes like this........
I have a web service through which I have to create a SAP Notification in SAP system and the Notification ID created and other details have to be returned back to the webservice from the BAPI. I have identified the relevant BAPI for the scenario.
I have a wsdl file which I have uploaded it. What are the next steps to be done?
Please let me know what all(e.g., Data types, Message Types, Message Interface) I have to create in Integration Repository and what all configurations I have to make in Integraion Directory.
FYI, I have a gone through a list of Blogs, but didn't get enough info.
Please help me out in providing your valuable answers.
Thanks,
Vijay
P.S. Rewards points are sure .....

Hi Vijay,
 If at all you have uploded wsdl file for the webservice you no need to create data types for the same even for the same as RFC also.
 Create message mapping and drag the wsdl file which you have imported as External Definiations and there you will be having request and response parameters..Do the mapping accordingly(according to your requirement).
Mapping like:
 Wsdl(Request)---->RFC (Input parametrs)
 RFC (out parameters)------>wsdl(Response)
Create message interface with Synchronous for outbound
 No need of DT,MT if at all if you import the wsdl file.
 Hope i am clear.
Please let me know if you have any queries..!
Thanks and Regards,
Chandu.
null
null

SOAP Sender to RFC Scenario WSDL File

Hi,
I am working on SOAP -> PI -> RFC Scenario. I generated WSDL from sender agreement and gave to the client that can consumed by the third party system. But client is not ready to consume the WSDL. He provided WSDL and asking me to use that. Could you please suggest whether WSDL given by the client can be used in SOAP -> PI -> RFC Scenario. If it is possible, could you please provide steps how it can be done?
Thank you.
Regards,
Cdr.

Thank you Hareesh & Divya,
When we generate WSDL from PI, it gives soap action and soap address location based on the interface we use for SOAP -> PI -> RFC.
When we import WSDL given by the client as external definition, we get messages(Structures). But where do we pass the soap action or address location. I do not see any option in the soap sender communication channel. I am not visualize the link.
Can somebody share their knowledge if they have done in this way.
Thank you.
Regards,
Cdr.

Using SOAP Sender adapter in PI 7.1

Hi Guys,
I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
Has something changed in 7.1 for this type of scenario?
Thanks guys,
Olian

Hi! Olian,
I think u r going in a wrong way. The above given URL is wrong and incomplete one.
The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
The generated WSDL contains URL like this>>
"http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&senderService=Business Service&receiverParty=&receiverService=&interface=SenderInterfaceI&interfaceNamespace=http://XXXXXXXX" />
Also follow the below procedure for generating the WSDL.
Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
CREATING THE WEBSERVICE IN XI :
1) In Integration Directory, go to Tools tab --> Define Web Services.
2) Now one Wizard window will opens and follow the below steps:
Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
If there is party then ::
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
4) Specify the Sender Business Serviceu2019s details:
5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
document(WSDL)
6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
URl:
Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
If your working on PI 7.1 means::
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
I hope the above information will give you a detailed information in generating and testing webservice right.
Regards::
Amar Srinivas Eli

IDOCFlatToXmlConvertor in the Module Processor For SOAP Sender CC

Hi Sdners,
Can we use below adapter module for Proxy Communication- SOAP Sender with XI Protocol ?
IDOCFlatToXmlConvertor in the Module Processor
From SAP we getting IDoc as Flat File wrapping it in Proxy Messages. We need to do convert those messages into XML format to do mapping.
Scenario:
SAP Proxy(Idoc flat file in Proxy) --> PI --> 3rd Party

Hi Kiran,
The without java mapping option will force you to use SOAP Axis since you can use IDOCFlatToXmlConverter.
Well there is another alternative, but you will need to use two scenarios.
The first one step would be proxy to file (NFS save in AL11)
The second step would be file (still NFS) to 3rd party (here you can use the converter module in file sender CC)
Regards,
Mark

SOAP Sender URL for Default XI parameters

Hi,
In my scenario i want to use same SOAP sender communication channel for many webservices.So i selected USE QUERY STRING OPTION . But i am not sure about the parameters in URL. I referred SOAP Adapter how to guide. it was helpful to some extent but would be grt if u guyz confirm the URLfor sending the different default XI Interface parameters .https://server:port/XISOAPAdapter/MessageServlet?channel=:<sender service>r:<sender comm channel>&version=3.0&Interface=<????>
Basically i do not know what shud be given for interface name
Regards
Vish

Hi Viswanath -
You're on the right track for your purpose of using one channel and dynamically setting the interface name. The SOAP FAQ Note 856597 spells it out well:
 "Q: Can I set the interface name dynamically from the client?
 Yes. You can overwrite these XI parameters from the client. To
 activate this overwriting mode, you need to turn on option "Use
 Encoded Header" and "Use Query String" in the channel. Then your
 client can append the interface name using parameter Interface.
 For example, interface namespace http://sap.com/test and
 interface Test can be represented by the url-encoded form of
 http://sap.com/test^Test as in
 #&version=3.0&Interface=http%3A%2F%2Fsap.com%2Ftest%5ETest"
I see you already have some of this. Don't forget to check both the "Use Encoded Header" as well as the "Use Query String" option.
>>>>In that case whatz the relevance of namespace in the URL. You mean we can ignore that .Pls advice
When you dynamically set the interface name, yes, you need both the interface name and the namespace. All this information (including the namespace) is needed for the receiver determination step once it reaches XI.
If you're having trouble with the URL, generate a WSDL using the "Define Web Service" option in the Int. Directory with the relevant interface information.
Jin

SOAP Sender with additional header: Interface determination error

Hello Experts,
I need to implement a scenario where in sender will add custom header fields and in PI, the values needs to captured. Second step: Based on the custom header value, the receiver needs to be determined.
Scenario: SOAP Sender -> PI -> SOAP Receiver
Request Message:
<RequestMsg>
 <request>
 <Field 1>...</Field 1>
 <Field 2>...</Field 2>
 <Field 3>...</Field 3>
 </request>
</RequestMsg>
Without any custom SOAP header, I have created Request / Response Message, Message Mapping, Service Interfaces (Inbound & Outbound) and Operation Mapping and tested the scenario by triggering call through SOAP UI, it works fine. SOAP Request XML looks like below:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:v1="http://www.test.abc.com/v1">
 <soapenv:Header />
 <soapenv:Body>
 <v1:RequestMsg>
 <request>
 <Field 1>1</Field 1>
 <Field 2>2</Field 2>
 <Field 3>3</Field 3>
 </request>
 </v1:RequestMsg>
 </soapenv:Body>
</soapenv:Envelope>
To use customer fields in SOAP Header, I have checked the option "Do Not Use SOAP Envelope" in the SOAP Sender CC and added "&nosoap=true" to url. SOAP Request XML looks like below:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:v1="http://www.test.abc.com/v1">
 <soapenv:Header >
 <id>REC1</id>
 </soapenv:Header >
 <soapenv:Body>
 <v1:RequestMsg>
 <request>
 <Field 1>1</Field 1>
 <Field 2>2</Field 2>
 <Field 3>3</Field 3>
 </request>
 </v1:RequestMsg>
 </soapenv:Body>
</soapenv:Envelope>
Now, when I invoke the url, I see that the message reaches PI but it throws error: RoutingException: InterfaceDetermination did not yield any actual interface
Please note that I have added a Java Mapping before main message mapping to read the soap header and pass only the request message to the next message mapping.
I am sure, I am missing important steps in the configuration. Please help me in reolving the issue.
Thanks & Regards,
Ankit Srivastava

Hello Hareesh,
Bingo! The second option suggested by Nicolas worked like a charm. I am just copying the same here:
-----In ESR, you set the attribute "Interface Pattern" of the outbound service interface as "Stateless (XI30-compatible)", which does not use operations.----
Thanks a lot. Now, I will be able to concentrate on the next steps.
Regards,
Ankit Srivastava

"NO_RECEIVER_CASE_BE" error with SOAP Sender assigned to a Business Service

Hi all,
we have a strange error with XI3.0
We created a configuration scenario where the initial step is done by a Business System, that uses a SOAP Sender communication channel to send its request. And this works great when testing it with XMLSpy.
But we then needed to shift from a Business System to a Business Service, as the machine sending the SOAP request changed and was not anymore part of the landscape, but elsewhere.
Hence we recreated a SOAP sender which we assigned to this new business service, doing absolutely the same configuration work as for the other soap sender of the former business system.
Yet when testing it through XMLSpy, we everytime get a NO_RECEIVER_CASE_BE error back, stating that "No receiver could be determined". Yet when checking in sxi_cache, receiver determination is clearly there. All the blogs I went into are only refering to Business System for a SOAP sender, so I was wondering if any of you already managed to assign a SOAP sender to a business Service.
Regards,
Cedric

hi,
so you sue SOAP to make a query ? (sync)
or to send the data to XI ? (async)?
if async then make sure
you use Quality of Service other then BE
in your soap adapter channel
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error in send step

Hello,
I ehanced an existing BPM where a send step sends data to a J2EE system. I inserted a switch and put the existing send step to one branche and a new send step to the otherweise-branche. The new send step interrupt with an error:
No exception defined for fault message hostname http://xml.apache.org/axis/
But there is an exception branche defined. An idea what's the problem?
I didn't define a message called hostname, so where he got this name from?
thx
chris

No, everything seems fine.
Here is the payload of response :

<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Another problem with SOAP sender

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

Synchronous SOAP sender

HI Guys,
I had created a synchronous SOAP sender adapter (Webservice -> RFC), the interface is working and it is updating the records in SAP using RFC but iam not getting the response back from SAP. And the other thing which i noticed is when i change the QOS as Best Effort, Iam not getting any message into SXMB_MONI,but the record is updating in SAP. If is use the QOS as Exactly once the message is showing up in SXMB_MONI. Can anyone let me know regarding the config / design steps for the synchronous response ?
regards,
kittu.

Hi,
please see the below links
Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/frameset.htm
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
SOAP webservice directly to IE - /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Chilla.

SOAP sender adapter with client authentication

Hi,
Can you please tell me the steps to be followed to configure SOAP sender adpater for HTTPS with client authentication.
Thanks

Hello,
Check out this SAP NOTE
[Note 891877 - Message-specific configuration of HTTP-Security|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=891877]
Check out below blog for step by step process.
/people/rahul.nawale2/blog/2006/05/31/how-to-use-client-authentication-with-soap-adapter
Hope this will help.
Nilesh
Edited by: Nilesh Kshirsagar on May 28, 2009 11:31 AM

SOAP Sender Steps

Similar Messages

Maybe you are looking for