Default XI parameters in 7.1, soap sender.

Hi,
I have a quick question about Default XI Parameters in Soap sender adapter in PI 7.1.
Why are they not present in PI 7.1( sender interface and sender NS )?
which are mandatory parameters in 7.0.
I was guessing that , this ways we can create a generic soap sender CC.
Does anyone have a exact answer as why it was removed?
Regards,
Venkat..

> Even in PI 7.0 we will add interface name and CC to the URL.
> 1. Do you mean that we are supposed to have NS too along with above entries?
Yes, you should add interface and namespace as it is mentioned in SAP Note 856597
> 2. What do you mean by aligning behavior of SOAP adapter with other adapters?
Other adapters (File, JMS) get interface and namespace from a sender agreement connected to a sender channel. The behaviour of the SOAP adapter was different before.
I was told by development that migrated channels from 7.0 work without any change. If this is not the case, open an OSS ticket for this.
For new channels you have to call the SOAP adapter always with interface name and namespace. The online help is not correct.
Regards
Stefan

Similar Messages

XI 3.0 Sender SOAP Adapter Default XI Parameters

Hi all,
I've noticed when posting to an inbound comm channel using the sender SOAP adapter that unless I specify a namespace and interface under the 'Default XI Parameters', an error is returned indicating I need to specify default values for the namespace and interface.
This doesn't make sense. I don't want to set up a new inbound comm channel for every interface for the same sender service. As long as the SOAP address location is correct, i.e. sender service and interface are specified correctly, why should I need to set a default namespace and interface? Also, what is the expected behavior of the default XI parameters? Should it override what's passed in the SOAP location string?

Hi,
I think you have to add:
Optional: xml.addHeaderLine 0
Obligatory: try to put the ; between quotation marks like:
Hope this helps.
Cheers,
Paul

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

Defalt VI Parameters in SOAP Sender Channel Config

Hi all,
I have configured soap sender channel with Default XI Parameters as * for both Interface name space and Interface name.
SOAP adapter sends the message with * as the interface namespace and interface and fails with the error "No receiver could be determined".
Why is SOAP adapter is using the default XI parameters from the channel instead of the parameters passed with the SOAP message.
I could make this work specifying the Default XI parameters with correct name space and interface, but my problem is I have 2 different interfaces from the same service and cannel, I don't want to create a separate channel for each of the interfaces.
Please help.

Hi Pratat,
you have to set the
Use Query String to true and the adapter will take the service/interface data from the query string instead of the Default XI Parameters
Regards,
Nicolá

Default namespace in the SOAP sender adapter

Hi All!
Sorry for the following really easy question but what is the default interface name and default namespace in the SOAP sender Adapater? The name of the interface to where the adapter should forward the received SAOP message?
it means that for every soap message a new communication channel should be created. Or only one channel is enough?
And in the receiving case only one is enough or for every web services a new receiving communication channel need to be created?
Thank you for your answer.

Hi,
q) what is the default interface name and default namespace in the SOAP sender Adapater?
Ans) Soap Sender does not have any default namespace and interface. That can be set at Sender Agreement.
q) The name of the interface to where the adapter should forward the received SAOP message?
Ans : That message is forwarded to Adapter Engine and then to integration Engine. That takes interface in sender agrement and Namespace.
it means that for every soap message a new communication channel should be created. Or only one channel is enough?
Ans: For sender, 1 communication channel is enough. For Receiver, if you have 10 different systeems, then you need to create those many receiver communication channels .
And in the receiving case only one is enough or for every web services a new receiving communication channel need to be created?
Ans : Same as above
Note Soap message is not criteria for creating channels.... Please note that .. soap communication channels creates soap messagae.
-Subbu

Soap Sender Channel Config

While configurting Soap Sender channel, what should we use for "Deafult XI Parameters" section values for
'Default Interface Namespace' and 'Default Interface Name' ?
Thanks

HI,
Input Message Interface name and Namespace of the interface created (NameSpace of the object)
Just to cross check-
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
blog e.g-
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Regards,
Moorthy

SOAP sender endpoint problem

Hi all,
I'm now fighting for quite a time with a SOAP sender channel.
I generated a WSDL in the configuration. I used this wsdl in XMLSPY in order to send a request to XI.
And I must confess that I'm totally confused with the URLs. Which one do I need to take (we're using XI 3.0):
http://server:3400/sap/xi/engine?type=entry&version=3.0&Sender.Service=service&Sender.Interface=urnInterface
or
http://server:50000/XISOAPAdapter/MessageServlet?channel=party:service:channel
What is the difference between those URLs?
And for the Java URL (port 50000): Which channel do I have to announce? The Name of the SOAP sender communication channel?
Since XI proposes the url with 3400 port I think this one is appropriate. But whenever I use it I receive a RCVR_DETERMINATION.MESSAGE_INCOMPLETE error and the message is indicated in the monitoring as coming from "AnonymousClient". What do I do wrong? I also tried to force the SOAP adapter to use the parameters by checking the option "Use Query String" in the channel config.
Please help!
Thanks in advance.

Hi Frank,
thank you for your answer.
I added the default XI parameters.
Concerning the userID and Password: I am asked to enter login/pwd if I call the service. Is this what you mean?
Unfortunately this does not affect anything...
The response I get is the following:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
 <faultstring>System Error</faultstring>
 <detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context/>
 <code>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</code>
 <text/>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
What amases me is that the ns is http://sap.com/xi/WebService/xi2.0. I used the url including the part &version=3.0
Does this url work for you (I mean including the version)
Could the error also be related with other configuration errors (wrong receiver agreement) - I do'nt thnik so but sth goes definetively wrong.
Greets,
Joachim

Variable Transport Binding - Soap Sender

Hello all,
I'm trying to retrieve a parameter from the HTTP header of a SOAP request.
I have created a SOAP sender communication channel, checked "Set Adapter-Specific Message Attributes" and "Variable Transport Binding", and entered the name of the parameter in Variable Header (XHeaderName1).
When I send the SOAP request, DynamicConfiguration exists with all standard parameters, but there is no XHeaderName1...
If I try the same with sender HTTP adapter, it works fine.
In the other way, if the dynamic configuration parameter XHeaderName1 already exists, and I try to add it in a HTTP header parameter in a receiver SOAP CC, that works.
Does somebody know why this doesn't work in the sender one?
Thanks,
Greg
PS: I'm using PI7.0 SP14

Hello,
I can see in dynamic configuration, with the namespace http://sap.com/xi/XI/System/SOAP, the standard HTTP parameters like SServerHost, SRemoteUser, etc...
But if I add a HTTP header parameter in the SOAP request, and I try to retrieve it with the SOAP sender CC, the parameter is not added in the dynamic configuration. If the name of the added HTTP header parameter is "TestParam", I put "TestParam" in the XHeaderName1 field of the sender CC, but the value is not added in the dynamic configuration. This is my problem.
Thanks,
Greg

SOAP sender adapter and XI adapter reusablity

Hi,
We are having good amount of interfaces using SOAP sender and XI Adapters (WS to Proxy scenarios).
My question is :
we can make reuse of Sender SOAP and Rcvr XI adapters in all scenarios.
If we reuse these adapters in all our interfaces what are the limitations and any problems we may face in future?
Replies will be highly helpful.
Thanks
Kishore
Edited by: kishore kumar on Jan 21, 2010 7:23 PM

SOAP sender depends on the Sender Message Interface and Namespace (in versions lower than SAP PI7.1) so if your scenarios satisfy these parameters then you can (rather should) re-use the channels.
Similarly for the PROXY receiver channel....if the proxy is being hosted on one particular receiver SAP ECC system then the details in all the channels that you create will be the same and wont be recommended....hence even this can be re-used.
There is no issue in re-using the channels....just that you should closely monitor these channels to ensure that they do not stop/ fail causing all the involved interfaces to stuck.
Regards,
Abhishek.

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

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

HTTP Error 501 with SOAP Sender channel

Hello,
i've am simple Question:
I want to call the following SAP XI SOAP Sender channel "MySoapSenderChannel":
XI-Parameters:
namespace: <myInterfaceNamespace>
Interface: <myAsynchInterface>
QoS: Exactly Once in Order
Queue: MY_QUEUE
We do not care about the Response - so the processing is asynchron.
Thus my interface mapping maps to asynch interfaces. The desitnation
is an ABAP Proxy. The configuration has been done and tested.
Here my question:
according the documentation, the URL has the following syntax:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel.
In our case:
http://<myHost>:8002/XISOAPAdapter/MessageServlet?channel=:MyService:MySoapSenderChannel.
But when i generate a WSDL for the interface out of the Configuration, the address is:
<soap:address location="http://<myHost>:8002/sap/xi/engine?type=entry&version=3.0&Sender.Service=MyService&Interface=...
and so forth.
But was is the difference between these 2 possibilities?
Why do i get HTTP Error 501 when i use the URL from the documentation (the first one)?
Thanx in advance
Gunnar

Gunnar,
I will suggest you to go through it once to check all your connection.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Sarvesh

PI 7.1 URL for SOAP Sender incorrect

Hello experts,
I have a SOAP sender agreement and generated the WSDL from the "Display WSDL..." option on ID, now the problem is that the soap address tags for HTTP_Port and HTTPS_Port are being created with the hostname of my PI server without domain, but all other url's in the wsdl file and including the WSDL URL of the wsdl file have the correct server name and domain, so when somebody gets the wsdl file from the file location and upload it to even Eclipse or just consume it from any other composite cannot reach the service exposed in PI, so I was wondering if any of you experts can help me with where can I find the parameters that Integration Directory use to create the soap address urls fro HTTP and HTTPS automatically, I've checked all the exchange profile and all the reference to server have the domain, I'm not a basis consultant and our basis team cannot find the problem, if anyone can help me with where can I find these parameters would be really appreciated, thanks in advance for your answers.
Rergards,
Julio

HI JULIO,
SOAP sender agreement and generated the WSDL from the "Display WSDL..." option on ID
Q. HOW TO CHECK THE JTTP SENDER SIDE URL........WE HAVE ONE OPTION IN ID.....CHECK THE BELOW PROCESS FOR REF.....
ID-->TOOLS>DEFINE WEB DERVER->CONTINUE->PROPOS URL (CLICK)>CONTUNUE-->SELECT THE INTERFACE
NAME (NAME NAME SPACE SOFTWARE COMPONENT NAME)---->CONTINUE --->(THEN SERVICE , INTERFACE
NAME ,INTERFACE NAME SPACE)-->CONTINUE->OVERVIEW
THIS IS THE PROCESS TO GET THE SENDER SIDER URL
REGARDS,
KESAVA

Soap sender adpater issue missing sender interface and namespace in the msg

Hi Expert,
I got a problem when try to using soap sender adapter.
Here is the sceanrio:
Http web service client call ---PI soap sender adapter -some routing data-business system inbound.
Sytem information:
SAP_ABA     700     0019     SAPKA70019     Cross-Application Component
SAP_BASIS     700     0019     SAPKB70019     SAP Basis Component
PI_BASIS     2005_1_700     0019     SAPKIPYJ7J     PI_BASIS 2005_1_700
ST-PI     2008_1_700     0001     SAPKITLRD1     SAP Solution Tools Plug-In
SAP_BW     700     0021     SAPKW70021     SAP NetWeaver BI 7.0
ST-A/PI     01L_BCO700     0000          -     Servicetools for other App./Netweaver 04
Here is my problem. I use soapui trigger a test msg to PI system. But in the sxmb_moni, only sender service is there.
The sender interface and sender namespace is missing. And the msg has error called: :INTERFACE_REGISTRATION_ERROR.
Which means I do not have a inbound interface to process the msg.
But I suppose to redirect the msg to business system.
Here is the configuration:
reciever determination: soap sender service, soap outbound interface, soap interface namespace --> reciever business sytem.
Interface ditermination: soap sender service, soap interface --> receiver interface, receiver namespace.
Sender agreement: soap service, soap itnerface --- soap communication channel
receiver agreement, soap service---> receiver sevice, receiver interface, reciever namespace and reciever cummunication channel
define of soap sender adapter:
soap sernder, with use encoded header and use query string checked and qos as exactly once.
Anyone has any idea here? Many thanks! And most strange thing is yesterday it works and today it failed.
Please kindly help here.
Thanks a lot,
Leon

Hi guys,
thanks for the input.
Hi Sven,
I have input default interface and namespace.
Hi sivasakthi,
Regarding mistype, it may happen, I will do it again right away.
And the URL is generated by the wsdl toolkit in the directory.
I marked use encoded header and query string in the communication channel.
I will generate the wsdl again and test it again.
Regarding URL(endpoint of web service):
http://hostname:50000/XISOAPAdapter/MessageServlet?channel=:AGSSAL_SOAP:AGSSAL_SOAP_CC&version=3.0&Sender.Service=AGSSAL_SOAP&Interface=urn:a1s_saplivelinkcontent.service.sap.com^MI_O_AS_DELIVERNOTIFY_SOAP
Again thanks for you guys help.
Best regards,
Leon

Web Service SOAP Sender Authorization

Hi all
I have been implementing a Web Service (SOAP Sender CC) that should be consumed by an external party. I have been testing it successfully using XMLSpy with the drawback of the authentication box coming up even though I have added sap-user and sap-password to the URL as following:
http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:SOAP_Service:CC_SOAP_Sender&sap-user=<name>&sap-password=<pass>
The user that I have created for this has the profile SAP_XI_APPL_SERV_USER assigned.The request is successfully executed when I enter <name> and <pass> in the box. My understanding of it would be that the box does not show up if the login parameters are provided with the URL. Do I have to do any additional settings so that the login information will be taken from the URL parameters automatically instead bringing up the authoritzation box?
My CC settings are as following:
Adapter Type: SOAP (SAP BASIS 7.00)
Sender
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Server
HTTP Security Level: HTTP
Conversion Parameters: Keep Headers
Quality of Service: Best Effort
Any feedback would be appreciated.
Thank you,
Daniel

Hello Daniel,
1. You can add username and password to the SOAP URL and expose your XI Interface as a webservice. Just that the URL is different than the one you are using and you do not need a Sender SOAP adapter but the blog I have listed above.
2. You can turn of Basic authentication on Sender SOAP adapter's but it is not recommended as it would turn off all authentication for SOAP scenarios and it can lead to security risks.
I have seen a few forum threads describing how to turn of Basic authentication for SOAP adapters but from what I have heard from SAP, they do not recommend using this option.
Regards
Bhavesh

Default XI parameters in 7.1, soap sender.

Similar Messages

Maybe you are looking for