SOAP Adapter:target URL

Hi,
to have to call a webservice with different operations, i do the following:
http://host:port/WebService/Config1?style=document&method=SetMaterial
and
http://host:port/WebService/Config1?style=document&method=SetMaterial
in two different comm.channels
but it didn't work.
Some help?
thanks,
Peter Ha

hi,
check whether any authentication is required....
regards,
Sundararamaprasad.

Similar Messages

Receiver Adapter - Target URL/SOAP Action

Hi,
Can I just confirm the following 2 values required on a SOAP Receiver adapter:
Target URL : Location within SOAP:Address tag of WSDL
SOAP Action: SoapAction within SOAP:Operation for relevant Web Service method within WSDL
Cheers,
PaulC.

> Target URL : Value of SOAP:Address tag from web service WSDL
right, it is attribute "soapAction"
> SOAP Action: Value of SOAP:Operation for relevant Web Service method within web service WSDL
right. attribute "location"
check this guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4

SOAP Receiver Adapter - Target URL

Hi,
We have a web service scenario, where the Sender is a III Party Java system and PI is the middleware and ECC as our receiver system. We have a wsdl binding generated from SOAMANAGER. We are using the WSDL Endpoint as the Target URL in our SOAP Receiver Adapter. The scenario works perfect with desired results.
Now that webdispatcher comes into place for load balancing and the BASIS team has given a different URL to use in the Target URL of the SOAP Reciver Adapter. The scenario throws the following eorr:-
Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
Has anyone come acrossed such issues. Looking forward for a solution.
Thanks & Best Regards.
Kris

> Now that webdispatcher comes into place for load balancing and the BASIS team has given a different URL to use in the Target URL of the SOAP Reciver Adapter. The scenario throws the following eorr:-
>
> Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Redirect
>
> Has anyone come acrossed such issues. Looking forward for a solution.
I wonder why your basis team is not able to help you.
It seems that the web dispatcher is not set up correctly.
http://en.wikipedia.org/wiki/HTTP_302

SOAP Receiver adapter target url and method details

Hi Friends,
I am working on file to SOAP interface.
I know using SOAP receiver adapter , we need to have target URL and action.
Here, how client need to give target url and action as they are not aware of these things..please suggest.
Also if we are generating inbound service interface,how they have to handle this from their end.
Thanks
Kishore

Get the WSDL file from ur Third party client and u can use the WSDL file as an External definition in PI and WSDL file also has WSDL URL which u can use in SOAP receiver adapter.
For INbound SOAP case-
Generate the WSDL file in XI and give that WSDL file to ur third party client which will send the data using the WSDL URL mentioned in the file.
refer below blog for understanding in detail:-
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
chirag

Soap Receiver adapter , Target URL and Soap Action

HI all,
WIll anyone tell me regarding Soap action, casue , they have given a URL which i have put in Target URL, but i am not able to understand what is SOap action what need to be put in this
Thankign you
Sridhar

i Sridhar,
In XI SOAP adapter we need two things:
SOAP URL: which is endpoint to the webserver.
SOAP action: describes particular method name we wanted to excute on that web applicaiton hosted on the webserver.
WSDL file has normally multiple operations(methods) , so we execute particular method by giving particular action name.
Action is not mandatory parameter i guess, this is in case , when wsdl is exposing only one method(action).
:Normally you can find SOAP Action element under element <SOAP:operation name = "XXX">
Hope this clears.
Cheers,
Div

Soap receiver target url

Hi guys,
I'm having some doubts on a soap receiver adapter.
Imagine, you use the ID to define a webservice.
Two simple synchronous interfaces, meaning, you send a string and receive another string via SOAP.
In the ID you define the comm channels, the soap sender and receiver.
My doubt is in the receiver side, you have tou specify the target URL. The problem is, how can I know the target URL, since the service will only be defined later. Meaning, I want XI to answer to a sender client which will use the WSDL generated after by the ID tool.
Where should XI answer to?
I've seen some blogs concerning some similar issues, but none concerning the problem I'm facing.
Can you guys help me or give me any hints on how to work around the problem...

Hi,
If you have a SOAP client sending a request message to XI and expecting a Response message, you need to configure SOAP sender adapter only. You do not need SOAP receiver adapter in this scenario. Sender adapter doesnt require any URL, moreover when you define a webservice in XI, you have to construct a URL where this web service can be reached.
You need the SOAP receiver adapter (where u need to mention the URL of teh service) if the receiver system exposes a webservice to which you are trying to connect from XI.
What are ur sender and receiver systems?
praveen

Error when setting dynamically the target URL in receiver SOAP Adapter

Hi,
I'm setting dynamically (from the mapping) the target URL in the receiver SOAP adapter:
String url = "http://mosxd30:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=DUM&receiverParty=&receiverService=&interface=SI_OA_CustomInvoiceData&interfaceNamespace=urn:repsol.com:laboratory:firma";
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(key, url);
The receiver adapter fails with:
"invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized"
Reading weblogs, etc, the most probable cause for this is a wrong target URL, but then what I did was to set it as a fixed URL in the C.Channel, and it worked, so the URL is fine.
In the communication channel, I'm using "Configure user authentication", with a user and password, and what I think it's happening is that if I use another different URL dynamically, the channel is ignoring the user authentication settings.
Any ideas?
Thanks

I forgot to say that I've checked the SAP note "FAQ Soap adapter", and it says:
Q: I get an authorization error "401 Unauthorized" from the adapter's servlet. What went wrong?
           A: The adapter's servlet is protected by default. You must use one of the user names assigned in security role xi_adapter_soap_message for component XISOAPAdapter. Please consult the documentation for Visual Administrator to view and change the security setting.
           The user authentication of the SOAP adapter is not part of the SOAP adapter but of the web container of the J2EE engine. The default authentication setting is defined in the web.xml descriptor file of the SOAP dapter web application. This setting may be modified from Visual Administrator with some restriction. Please refer to the security documentation for the J2EE engine.
           Please note that 710 onwards there is no Visual Administrator instead the Netweaver Administrator is to be used to assign the roles to the user to access the SOAP adater servlet.The user must be assigned one of the following roles SAP_XI_IS_SERV_USER, SAP_XI_APPL_SERV_USER, SAP_XI_DEVELOPER_J2EE, SAP_XI_ADMINISTRATOR_J2EE.
The target URL is a sender soap adapter (the result of one interface is sent to another one via soap adapter), and it's this one which is complaining because of the authentication I think. But I don't know why it's ignoring the user authentication flag I'm using.

Sender SOAP Adapter with HTTPs call

Hello,
Our scenarion is .. we will have a sender SOAP adater .. but it needs to be called using HTTPs(SSL).
Now considering we have the certificate generated and installed ..and that integration server is HTTPs enabled....What URL should the sending system call..?
For normal HTTP call the inbound address for inbound Adapter is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
For the case of HTTPs just changing the htttp to https and the port number in in the calling system will suffice? Or is there other configurations that needs to be done??
Thanks and Regards,
Himadri

Hi Himadri,
Firstly as suggested by others you can call using https and give the https port in the soap adapter servler URL. Secondly you need to do the following configurations:
1) If its PI 7.0/3.0, deploy the latest version of the SAP Java cryptography toolkit.
2) Configure SAP PI as the server for HTTPS calls. In short
      Using the SSL Provider service:
                            a.      Select whether the J2EE Engine should:
                               ■      Request (but not require) that the user presents a client certificate for authentication.
                               ■      Require that client certificates are to be used for authentication.
                            b.      Import the CAu2019s root certificate into the Trusted Certification Authorities list. (Choose Add.) using the following For all the steps, link is mentioned below for XI 3.0, you can find similar ones for PI 7.0
http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/content.htm
3) If you want to enable client authentication then you would need to add the client certificate in the TrustedCA keystore view of the SAP J2EE engine.
4) In the SOAP Adapter sender channel, configure Inbound Security level as HTTPS or HTTPs with client authentication based on your scenario.
Best Regards,
Pratik

Issue while passing Target URL dynamically in SOAP Receiver Adapter

Experts,
I am stuck with an issue while passing the Target URL dynamically.
The UDF required for this works just fine. I can see the Target URL in Dynamic Configuration header(The Key is TServerLocation) in SXMB_MONI but the request that I am sending is not reaching the web service.
Some posts have suggested to hard code the Target URL as http://.
Below is the error that I am getting when I hard the Target URL as http://:
<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>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
When I hard code the Target URL as Test (any dummy value), the error that I get is different. (Detailed error shown below)
<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>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: no scheme
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I've referred the post [Dynamic URL for SOAP receiver adapter;.
I am on PI 7.0.
Any help in this regard is highly appreciated.
Best Regards,
Vijay

Issue resolved... by doing this:
DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TAuthKey");
conf.put (key2, "username");
In the advanced tab of the communication channel, set the flag "View Authorization keys", and then added "username" (user to access the dynamic target url) and the password (2 times).
That's it...

SOAP adapter and dynamic target URL

My scenario: synchronous communication ABAP Proxy <=> XI <=> External WebServices.
There is a need to have configurable (dynamic) target URL for SOAP Adapter. This target should be configurable from ABAP Proxy. Any idea how can I achieve my goal?
Some additional notes why I need configurable target URL. I've multiple WebService instances which has identical interfaces and the only difference is target URL. I see no need to define for each webservice different SOAP Adapter. The other thing is that customer want to have configuration of destination (target) url on backend system (where ABAP Proxy is used).

Check http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm
It's possible to set the URL for Soap dynamically.
To process adapter attributes in the message header of the XI message, set the Use Adapter-Specific Message Attributes indicator and the Variable Transport Binding indicator.
You can evaluate the following attributes in the message header:
Description: You can set the entire URL.
Technical name: TServerLocation

Target url for receiver soap adapter

Hi everybody
where will I get the target url to enter in the receiver soap adapter parameters? I got the link from wsdl under "address location"..But when I open the link from the internet explorer I could see an empty wsdl
<faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received</faultstring>
thanks
Ramya

Hi Ramya,
When you try opening the URL using web browser, you are not sending any data and hence in response you get an empty message.
But at the same time, the message shows you that the service corresponding to that URL is invoked, activated and running.
Give the same URL in your receiver communication channel and try execcuting the scenario, as far as receiver URL is concerned, it should work.
-Tanaya.

Target URL - Receiver SOAP Adapter

Hi experts,
I would like to know if the "Target URL" parameter in the Receiver SOAP Adapter is a case sensitive one.
Point will be given,
Tks
Daniela Machado

From my experience, I have used the Receive SOAP adapter to contain the URL of the Sender SOAP adapter of XI itself and in these calls the URL was not case sensitive ( the hostname and port are not case sensitive ) but the Business System , Comm Channel Name , Interface Name and Namespace are case sensitive.
When calling a true webservice, I never paid real importance to the case sensitivity as I used to take the URL from the WSDL provided by the Webservice.
Though not the answer to your question hope it helps.
Regards
Bhavesh

Target URL in the Receiver SOAP channel in PI 7.11

Hi
I have designed integrated Configuration in PI 7.11 and i have SOAP sender and SOAP receiver. SOAP sender is fine but for SOAP receiver i have an issue with the target URL that i selected.
Initially the receiver was ABAP proxy with HTTP connection as we dont have ABAP related adapters in AAE i used SOAP. But i have used the same URL that is the Target host configured in the HTTP ABAP connection to the target system. Then i am getting the following error at the receiver comm channel
Message processing failed. Cause: com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme
I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs to be done here.

..I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs >>to be done here
You are using Integrated configuration with PI 7.1 EHP1 version. That means SOAP supports as PI native protocol (XI) for PROXY scenario. So, you have to create soap receiver adapter and choose message protocol as XI.
Integrated configuration occurs in java stack engine and XI adapter(proxy) not exists there. Only if you do classical processing (IE) then you can use XI adapter at the receiver side. Thats the reason you dont find XI adapter in the integrated configuration.
Hope I answered your question

SOAP Receiver Adapter - Dynamic URL

Has anyone tried modifying SOAP URL dynamically using UDF in the mapping?. I searched Forum and couldn't get right answer. Does it work with Adapter Specific settings and variable transport binding? Please donot post links to other posts unless it got an answer or atleast close to being answered. We are on PI7.0. Thanks

Hi,
I have similar situation. My target URL lookslike this
http://devlsales.test.com:8000/soap/services/AdapterService which is a working right now.
With Variable transport binding ( TServerLocation ), Can I change http://devlsales.test.com from above URL to
http://devlprofits.test.com and remaining text same resulting
http://devlprofits.test.com:8000/soap/services/AdapterService by using UDFs.
Thanks
ST
Thanks

WSDL url for sender and receiver SOAP adapter

Dear Experts,
I am working on SOAP --> SAP PI --> SAP ECC synchronous scenario. That means I have to create 2 Cc for SOAP i.e. Sender as well as Receiver adapter. I am responsible for creating the Request as well as Response structure in SAP PI. The sender application team is dependent on me to get the WSDL file.
Please provide the suggestions on the below.
Sender SOAP adapter.
1. I will create the WSDL from Sender Aggreement. How to get the url and what is the navigation step? Should I provide the    same url to sender application team to call the service.
Receiver SOAP adapter:
2. In the receiver SOAP adapter , Should I have to get the web service parameter of the sender application. As mentioned , I am creating the response structure as well. That means I can not import the WSDL from the sender application. How to get target url in the receiver SOAP Cc.
I refered to the forum SOAP SENDER - test in soapui but its not clear.
Regards
Alice Rebecca
Edited by: Alice@xi on Dec 20, 2011 5:48 PM

Dear Bhaskar,
For synchronous scenario
                                                            Request
MS Application (SOAP)<--> SAP-PI <--
> SAP ECC.
                                                                                Response
I am creating the Request as well as Response structure in SAP-PI and its agrreement for both
the ways.
So for the MS appl team, I will give the WSDL url from the sender agreement to make the request to SAP-ECC.
Now for receiving the response from SAP ECC, from where I should find the value to enter in the target url of SOAP
receiver channel.
1.Should I take the target url value from the MS Application team?
2.How to know whether the MS Application or SAP ECC is hosting the web service?
Regards
Alice

SOAP Adapter:target URL

Similar Messages

Maybe you are looking for