Defining a Webservice for an XI SOAP Adapter

Hi together,
i have a little problem with an SOAP XI scenario.
I have build an XML -> XI -> Idoc Scenario.
Everything is working ok with the standard http request.
Now i have made a new SOAP communication channel and set this one up
with my message interface from the http scenario. After that i tried to generate
a wsdl in the xi ( integration directory ). ( Scenario is Webservice -> XI -> Idoc )
I send this file to one of our java programmers. He has to build the webservice
on an other system. But he says that his system can not generate the webservice from the file.
He gets this message in the Log Files:
WSDL part <M2S_ROUTING> points to unavailable element with qname: {}<M2S_ROUTING>.
Its my first time to set up an SOAP communication and i have no knowledge
of java. I have tried to search in the forum, but there was no point for my
problem.
Can i use the normal message interface from my http scenario for the soap scenario?
do i have to change something in the wsdl-file that xi generates?
The url for the generation is ok. this one i have made like shown in "How To
Use the XI 3.0 SOAP Adapter".
I also testet the scenario with XmlSpy and with that its works correct.
Only the other system does not generate the webservice from the file.
( its is an NW2004 SP12 on an other server/network )
Thanks for any answers,
Carsten

redefined question

Similar Messages

Webservice for proxy to SOAP adapter interface

Hi Experts,
we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?

we have scenario Proxy to SOAP for this inteface is it possible to provide the webservice from PI side.
if yes please let me know the steps.
i know the process how to provide the webservice when the SOAP adapter at sender side.
1) through sender agreement---->Display WSDL.
2) Tools---->Disply WSDL -
> yes that is possiable for only sender side as webservice because sender always consumer
is it poassible to provide the webservice when SOAP adapter at receiver end by using 2 nd process?
No that is not possiable to import WSDl File In receiver agreement because receiver always Provider .
in ESR:
wsdl file ll be imported in External defination as external message.
in ID:
in receiver Comm.channel -> call the soap URL and Soap Action(not manadatary)

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

SOAP Adapter = Webservice???

Hi,
I have created a service using the SOAP Adapter. My question is now: Is this service a webservice. If yes, how would I be able to obtain the related WSDL?
The outbound interface is accessed by the following URL:
http://myserver/XISOAPAdapter/MessageServlet?channel=:MY_BUSINESSSYSTEM:MY_COMCHANNEL
simply adding the argument &wsdl to the url doesn't pass back any WSDL.
Kind regards,
Heiko

hi,
>>I have created a service using the SOAP Adapter. My >>question is now: Is this service a webservice
yes having a soap adapter for a particular scenario makes that scenaro accessable by SOAP, ie webservice.
>>http://myserver/XISOAPAdapter/MessageServlet?>>channel=:MY_BUSINESSSYSTEM:MY_COMCHANNEL
>>simply adding the argument &wsdl to the url doesn't >>pass back any WSDL.
i see where u r coming from , unlike ohter development platforms, where if you know the endpoint , adding &wsdl gives you the wsdl. But in XI we are merely exposing the interface to be accessable by a soap sender. Hence you have to generate the wsdl manually from Configuration Drectory. Tools->webservce
cheers,
Naveen

Regaring File to IDOC Useing SOAP Adapter

Hi ,
Can any one please forward me an File to idoc Useing SOAP ADapter Senario.IF i am wrong please send me a simple senario of useing SOAP Adapter.
Regd's
Raj

Hi Raj,
I think i will give you some more information about SOAP adapters,So Please go through the link below and follow the steps mentioned in it while defining the web service.Then you will get to know the actual use of a SOAP adapter.
<a href="http://help.sap.com/saphelp_erp2004/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm">Defining Web Services</a>
Sending a Simple SOAP envelope to XI via HTTP using ASP
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1442 [original link is broken]
More links for SOAP Adapter:
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
http://help.sap.com/saphelp_nw04/helpdata/en/9f/fdca3f01f33e1ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
You can create SOAP Request from WSDL using the following tool.
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916ebc4159c
You've to expose your outbound message interface as a WSDL which can be used by say EP.
Also go thru the following threads
Re: WebService
Re: SOAP Client for Synchronous Scenario
Re: How to test a webservice as a standalone?
Also check this Pdf for the Receiever SOAP Adapter configuration:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
Regards,
abhy

SOAP Adapter Error

I am working on a scenario:
SOAP Client <-----> XI <----> Web service.
I am using SOAP Adapter on both sender and receiver side.
I downloaded the WSDL for the webservice and imported it in IR and created Message Interfaces based on it and I am also done with the configuration side.
I am trying to send a soap request to XI via XMLSPY using my XI generated wsdl ( Generated a web service in XI using my scenario).
I am getting an error back in XMLSPY when I send a soap request.
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>DeliveryException</code>
 <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code
500 : Timeout
 at
com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at
com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
 at
com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
I tried to check runtime message monitoring. Here are the details:
Audit Log for Message: d3294f20-b2dc-11da-8994-003048805a88
Time Stamp Status Description
2006-03-13 17:00:46 Success SOAP: request message leaving the adapter
(call)
2006-03-13 17:00:46 Success Application attempting to send an XI
message synchronously using connection AFW.
2006-03-13 17:00:46 Success Trying to put the message into the call
queue.
2006-03-13 17:00:46 Success Message successfully put into the queue.
2006-03-13 17:00:46 Success The message was successfully retrieved from
the call queue.
2006-03-13 17:00:46 Success The message status set to DLNG.
2006-03-13 17:00:46 Error Returning synchronous error notification to
calling application: Received HTTP response code 500 : Internal Server
Error.
2006-03-13 17:00:46 Error Transmitting the message using connection
http://diamond:8005/sap/xi/engine?type=entry failed, due to: Received
HTTP response code 500 : Internal Server Error.
2006-03-13 17:00:46 Error The message status set to FAIL.
2006-03-13 17:00:46 Error Returning to application. Exception: Received
HTTP response code 500 : Internal Server Error
2006-03-13 17:00:46 Error SOAP: call failed:
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Internal Server
Error
Can anyone suggest what could be wrong here?
Thanks,
Shubha.

Hi,
You can first test your Adapter Engine from "Runtime Work Bench".
Follow the steps for testing the SOAP Adapter from XI.
Step 1 :- Component Monitoring--> Click Adapter Engine.
Step 2 :- Select the "Test Message" Tab
Step 3 :- Give details for send to = http://host:port/XISOAPAdapter/MessageServlet?channel=:<service>:<channel> ,interface name, service, namespace
Step 4 :- Payload should be Soap Request. and click send message.
Check the result in SXMB_MONI.
Note : You can create SOAP Request from WSDL using the following tool.
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916ebc4159c
Regards,
Rakesh.

SOAP Adapter without SOAP envelope sets contenttype to application/xml

Hi,
I wrote a adaptermodul for the SOAP adapter to create a SOAP:HEADER.
I disable the SOAP envelope in the communication channel.
Now I get a error from the WebService Provider because the SOAP Adapter sends with Content-Type application/xml and not text/xml. I set the content-type in the adapter module but it seens to not work.
How can I correct this ?
Regards,
Gerald

Hi
Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
but it is worth a try to check if the URL encoding works.. though I have not tried..
for example sending the hex value of the "?" - %3F%
URL is a generic topic, you can search that to get more information
(ex : http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
Regards
Vishnu

SOAP Adapter And Protocol issue

Why and when we use SOAP adapter ? Does Xi uses processed XML messages using SOAP protocol ? I am new to Xi and confused over the issue. Can anyone please explain this to me. Thanks for your time.

HI KM
When you want to Send Data to XI from a Webservice and vice versa, your SOAP adapter is used.
Check these links for reference...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
A SOAP adapter is used in order to post messages to a webservice or provide a web service for receiving messages.
How ToUse the XI 3.0 SOAP Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
Please follow stefan's weblog
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
SOAP adapters are used for communicating with the WEB SERVICE. Web service is a software system designed to support interoperable Machine-to-Machine interaction over a network. Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services. In common usage Web Service refers to clients and servers that communicate using XML messages that follow the SOAP standard. So we communicate the WEB SERVICE using the SOAP adapters.
This is an example WEB SERVICE which follows the SOAP standards
http://www.webservicex.com/CurrencyConvertor.asmx?op=ConversionRate
A scenario using SOAP adapter..
RFC -> XI -> WebService - A Complete Walkthrough (Part 1) by Shabarish Vijayakumar
RFC -> XI -> WebService - A Complete Walkthrough (Part 2) by Shabarish Vijayakumar
SOAP , we will use for Webservices.. for sender and receiver side..also
one example from Webbrowser to XI to receiver ...system
another example is we can send it to end point URL..
Webservice
http://help.sap.com/saphelp_nw04/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
/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
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Soap adapter?
Regards
Abhishek Agrahari

Receiver SOAP adapter SSL error - client certificate required?

Hi all,
Problem configuring SSL in XI 3.0 NW04 SP17....
I have followed the config steps from Rahul's excellent weblog at <a href="/people/rahul.nawale2/blog/2006/05/31/how-to-use-client-authentication-with-soap-adapter">How to use Client Authentication with SOAP Adapter</a> (my Basis team have done the Visual Admin steps) and am going through his example as it closely matches my requirement. So, I have a test receiver SOAP adapter sending messages to a web service URL defined for a sender SOAP adapter. My test scenario is:
Sender File -> Receiver SOAP -> Sender SOAP -> IDoc Receiver -> IDocs in R/3
The problem components are in italic and underlined above. My Receiver SOAP Adapter has the web service URL, Certificate Keystore Entry and View entered. If, in the Sender SOAP Adapter, I have an HTTP Security Level of HTTPS Without Client Authentication, the interface works fine (note that Rahul suggests you untick the User Authentication in the Receiver but with this Security Level, it seems to work with or without it).
The problem is when I set HTTPS With Client Authentication in the Sender. I then get the following error in the message monitor:
SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException - com.sap.aii.af.mp.module.ModuleException: java.security.AccessControlException: client certificate required caused by: java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1111) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103) at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:250) at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103) at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:166) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:421) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Caused by: java.security.AccessControlException: client certificate required at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:843) ... 22 more
Has anyone got any idea what this could be caused by?
Many thanks,
Stuart Richards

Have you configured the https port with that keystore entry?
Check out these links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/881e3e3986f701e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/5c/15f73dd0408e5be10000000a114084/frameset.htm
Regards,
Henrique.

Modification of the SOAP Adapter

Hi all,
my problem is still the same as posted in the last thread. I have a webservice request submitted to the XI, which has no header element. So i have the problem that the message does not reach the XI due to an authorization error.
Now i had the idea to implement an own adapter. But instead of developing it from zero, i could modify the original SOAP Adapter. Is there a possibility to get the SOAP Adapters source code or has anyone an idea how i could resolve this problem without an own adapter.
I am not allowed to turn authorization off for the whole SOAP Adapter.
Thanks in Advance
Dieter

Hi Dieter,
1. add the credential (user and password) in the sender application, how to do this depends on what platform you use in the sender application.
2. following the link below, you find the document on how to develop a module.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
I don't think you need to develop a ADAPTER for this problem.
Regards,
Hui

Plain J2SE Adapter Engine - SOAP Adapter

Which reasons are there for using the soap adapter at the plain j2se adapter engine instead of the soap adapter at the central adapter engine (XI 3.0)? Which benefits are there? Which cases are known?

The J2SE adapter is a relict from XI 2.0
You may still use it, especially for migration from XI 2.0 to XI 3.0, but it is recommended to use the J2EE adapter engine.
Regards
Stefan

Error using SSL on Receiver Soap Adapter

Hi there,
I'm having some problems on connecting to a third-party application running a webservice (meaning, through Receiver Soap Adapter). The third-party appl. demands us to use a SSL connection (its url starts with https), with user authentication through certificate.
We've installed SAP Java Cryptographic toolkit and have a proper certificate configured on the KeyStorage entry, on Visual Administrator.
On Soap Adapter, I've configured HTTP Transport Protocol and have selected the "configure certificate authentication" option and selected the certificate, filled the mandatory fields (target URL and soap action) but I keep getting this error message on SXMB_MONI: "com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket".
Is there anything else than installing SAP Java Cryptographic Toolkit to enable SSL on Soap Adapter? Is there another configurations that need to be done?
Thanks in advance,
Henrique.

Hi
can u please tell me, how u r able to resolve the problem
i am also stuck in the same error
basically i am working on SSO b/w three systems.
EP>XI>R/3
i am able to do the SSO between the EP-->XI
but when i try with EP-->XI->R/3 it is giving me error at the receiver side means receiver soap adapter is not accepting the SAP Logon Ticket.
can u please tell me what entries should be given in the certificate authentication fields.
please provide the solution.
Thanks & Regards
Rinku Gangwani

Configuring the SOAP Adapter

Hi Folks,
I have a sceanrio where an AXIS client needs to talk to the XI SOAP Adapter.
How do I configure the SOAP adapter?
I tried to access the help docs for configuring the SOAP adapter. I understand that the adapter depends upon the plain J2SE Adapter Engine which should be available on port 8000.
But when I try to access
http://<hostname>:8000 I get an access denied error
Please help!
Thanks in advance,
Shailesh

Hi Shailesh,
Maybe your 8000 Port is in Use. So you can chance the port to 8200 or something else.
You Change port in "GUIBrowserEngine.properties" file.
And try to patch the Plain J2SE Adapter Engine with "SP 10 for XI Connectivity SE 3.0"
Regards,
Robin

SOAP Adapter - Guaranteed delivery

Hi ppl,
I have a requirment where we are exploring the possibility of the source system being able to expose its data in http format so that we can get use XI SOAP adapter to get the same over https. As SOAP adapter would access the data through WAN, what would happen to the data if the WAN is broken? How does the guaranteed delivery work in case of SOAP adapter?

>
Ethan Hunt wrote:
> thanks for your reply. For inbound messages, how will the data be recieved by SOAP adapter in case of broken WAN. If the source system is exposing the data once in every minute and the WAN is broken for 10 min, when it comes up again, will SOAP adapter recieve all the messages sent by the source system during the connectivity failure? I am not sure how the expose of data in http format works.
From your comments, it seems that the source system acts as a client, and PI (SOAP Adapter) will receive the data from the client.
You can configure the "Quality of Service" of the sender soap adapter with 3 possible options:
- Exactly once (async)
- Exactly once in order (async)
- Best effort (synchronous)
In the first two cases, your client will get an HTTP 200 response (with an empy SOAP message), while in the last case it will get as a response the message you have configured in PI. Take into account that in the first two cases, even if there is an internal error in PI (mapping error for example) your SOAP adapter will still have delivered an HTTP 200 response, as the SOAP adapter did its mission (received the message and delivered it to the Integration Server).
If the client can't reach PI, it won't get an HTTP 200, it will get an HTTP 500 or other error code, so it's your client responsability to retry sending the message until it gets the proper response.
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Edited by: Jorge Lopez on Jul 13, 2009 3:20 PM

SOAP Adapter details

hi all,
i am doing R/3>PI1>PI2-->File scenario.(i am working at PI2)
here i am importing the XSD's into PI2 through External definitions,for this what SOAP Adapter details i need to provide to PI1.
another interface
File>PI2>PI1-->R/3
for this scenario what SOAP Adapter Details i need to provide to PI1.
Thanks in advance
AVR

Hi AVR,
>>R/3>PI1>PI2-->File scenario
Here It will be a SOAP receiver, so the path will be as per help.sap http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
>>File>PI2>PI1-->R/3
Here in SOAP sender you need to mention the Sender interface and namespace details and set other parameters as help.sap
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Regards
Suraj

Defining a Webservice for an XI SOAP Adapter

Similar Messages

Maybe you are looking for