Soap sender Qos

Hi
I am facing error in soap sender posting from soap UI. I want to send the soap request asynchronous.
could you please tell me how to change the QOS,tried with QOS as EO in sender channel.

Hi
Try appending &QualityOfService=ExactlyOnce at the end of your soap URL
http://host:port /XISOAPAdapter/MessageServlet?senderParty=& senderService=FS& interface=IF&receiverParty=&receiverService=TS&interfaceNamespace=IFNamespace
for more Soap related error refer the note 856597
Regards,
Srinivas

Similar Messages

Specifying queue name in SOAP sender channel

Hi
We are on XI 3.0 SP18 - I have a requirement in which a soap webservice exposed out of the XI box - is to be called in an asynchronous mode - the webservice posts - document onto R/3 using an ABAP server proxy.
Now, there is also a need to post documents onto R3 - by serializing through an object key - material number ( say updates to a material ). I saw that there is a queue name in the soap sender channel setting when I choose eoio - qos . Is this queue name static ?
Also, any suggestions on how I can serialize the calls to the webservice based on an object key ( material number is supplied by the soap client ) all the way to R3 ( I am using a ABAP server proxy on the R3 side )

Ravi
I am looking for way to specify a non-static queue name here - so that I could establish a queue based on an object key from the source - web service client all the way to R3 - I wanted to know the options available on specifying the queue name in the communication channel -
Thanks...

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

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

Read user name from Header of SOAP Sender

Hi All,
Is there any way to read value of "sap-user" passed in below URL.
http://<server>:<port>/sap/xi/adapter_plain?namespace=<sender_ns>&interface=<sender_mi>&service=myservice&party=&agency=&scheme=&QOS=BE&queueid=httpclient&sap-user=<sap-user>&sap-password=<sap-password>&sap-client=<sap-client>&sap-language=<sap-lang>
I tried using DynamicConfiguration in my SOAP sender adapter with "SRemoteUser" variable, it did NOT work for me.
Are there other options like Runtime Constants in JAVA Mapping etc.
Thank you,
Smita

Hi Smita,
I am not sure if this is the question you are asking for sender SOAP adapter or HTTP Adapter?
Please refer the below statement.
SOAP Adapter:
The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
HTTP Adapter:
The plain HTTP adapter is used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope). These systems are connected using the Internet communication framework of the SAP Web Application Server. For this purpose, the Integration Engine HTTP inbound channel contains an HTTP service delivered by SAP, called /sap/xi/adapter_plain.
Queries entering the plain HTTP adapter must have the following syntax:
http://<hostname:port>/<path>?<query-string>
The query string contains the following data:
● Sender namespace ?namespace=<namespace>
●Sender interface &interface=<interface>
These details define the sender interface.
●Sender service &service=<service>
Specifies the sender service.
●Sender party (optional) &party=<party>
●Sender agency (optional) &agency=<agency>
●Sender scheme (optional) &scheme=<scheme>
If you are asking for HTTP Adapter, then I can tell you.
Please confirm.
Regards
B.Dheepa

SOAP sender adapter issue

Hi,
We are facing a peculiar issue when using SOAP sender adapter.It is a SOAP-XI-ECC scenario.
We have created WSDL using propose URL. Edited the address location in WSDL and included QoS=ExactlyOnce.
When we are testing from SOAPUI, it is making a asynchronous call, which is the requirement. But when the actual sender is sending the data using the same WSDL, it is making synchronous call. Any idea if Synchronous/Asyncronous decision/setiing is made at XI end or the portal end? And what is the solution?
Thanks,
Vishal

Hi Shabarish,
As mentioned in my query I have already tested it from SOAPUI and it is making asynchronous call.
URL is:
[http://server/sap/xi/engine?type=entry&version=3.0&Sender.Service=BusinessService&Interface=http://namespace^MI_product_oa&QualityOfService=ExactlyOnce]
Regards,
Vishal

EOIO with dynamic queuename possible in SOAP sender ?

The customer has a requirement to pass a queuename parameter within its SOAP message, and our PI SOAP sender adapter (which must use QoS EOIO) should use that queuename. Apart from the question if that makes sense:
is that possible at all ?
If yet, what flags do I have to set in the SOAP sender adapter (query strring, keep attachments and so on) ?
PI 7.0
CSY
Edited by: Christian Sy on Jan 13, 2011 10:14 AM

Interesting. We tried that option before, but got the following strange exception, so we thought that is the wrong way. The sender is PI 7.1, the receiver is PI 7.0.
Is it a problem with the different versions, or a problem with the namespace name (e.g. the "Minus" character) ?
Message-Verarbeitung fehlgeschlagen. Grund: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/MalformedMessageException - Unexpected length of element <sap:Main><sap:Interface @sap:namespace> = http://abcde.com/rd/GL/PA/B2B/SU-OP_IF001-GL/PurchaseOrder/10; nested exception caused by: com.sap.aii.messaging.util.XMLScanException: Unexpected length of element <sap:Main><sap:Interface @sap:namespace> = http://abcde.com/rd/GL/PA/B2B/SU-OP_IF001-GL/PurchaseOrder/10 at com.sap.aii.messaging.mo.xmb.XMBMessageHeader.unmarshal(XMBMessageHeader.java:1184) at com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:964) at com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:624) at com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:616) at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:382) at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:390) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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)
CSY

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.

Use of variable header XHeaderName1 in SOAP sender adapter

Hi all,
I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:
the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)
I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.
I tried with those settings in SOAP adapter configuration:
Keep headers checked
XHeaderName1 = Test
I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)
1. Pass "Test" value xxxx in SOAP Header as a tag
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Header>
          *<Test>xxxx</Test>*
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
2. Pass "Test" value xxxx in SOAP URL
http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&Interface=...&Test=xxxx
Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?
Thanks a lot,
Manuel

Hi Manuel,
Could you give a bit more detail on how you handled the SOAP message yourself.
I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.
At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.
Could we use the XI Adapter and ABAP proxy in a similar way?
Thanks,
Tim J.

Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
<http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

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

Variable Transport binding - SOAP Sender Adapter

Hi All
have a scenarion where Sender System is sending Custom SOAP Header as below into P through SOAP Sender ChannelI.
And the requirement is to access the values coming in Header fields, example within Message Mapping need to Map Headername1 value to Outgoing structure.
<soapenv:Header>
     <Header1>S1</Header1>
     <Header2>S2</Header2>
     <Header3>S3</Header3>
</soapenv:Header>
   <soapenv:Body>
     u2026..
   </soapenv:Body>
Have checked the Paramter KEEP Headers in SOAP Adapter and in Adapter Specific Message Attributes have defined the following
Variable Header (XHeaderName1) = Header1
Variable Header (XHeaderName2) = Header2
Variable Header (XHeaderName1) = Header3
Now need to know what should be mentioned in the UDF in the Message Mapping for accessing Dynamic Configuration. Will these headers mentioned will be a part of Dynamic Configuration or not ?
Using the below UDF and its failing in Message Mapping - kindly suggest the corect way of achieving the same
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "XHeaderName1");
String value = conf.get(key1);
return value ;
Appreciate response in this regard
//Swetank

Hi Abhishek
Its failing at runtime at Message Mapping stage. The real problem is that I can't see the Header1 in my Dynamic Configuration header - it has all the other fields like SServerHost, SRemoteUser, but not my Header1 (S1) field. Thus either the UDF is wrong or any configuration in SOAP Sender Channel needs to be adjusted.
Further I am not sure whether Custom SOAP Header fields can be a part of Dynamic Configuration or they only show fields which are part of HTTP header.
//Swetank

Adapter Module in SOAP Sender Adapter

Hi All,
To Confirm, Is it possible to use Custom Adapter Modules in SOAP Sender Adapter. If so, where exactly custom module has to be placed in communication channel with respect to the standard bean of SOAP Adapter.
Thanks in advance.
Regards,
Sudharshan N A

Hi,
The sender adapter cannot be extended Check this
http://help.sap.com/saphelp_nwpi711/helpdata/en/43/951aceb1146353e10000000a11466f/frameset.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/frameset.htm
Regards
Suraj

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

SAP PI 7.1 SOAP sender 500 internal server error

Hello!
We would like to receive messages from our business partner. As the partner sends EDIFACT we have to use the conversion from EDIFACT-text to EDIFACT-xml. That's why we have to use SOAP instead of plain HTTP.
As the partner already sent messages over X.400 we just added a SOAP communication channel and used this channel in the sender agreement instead of the X.400 communication channel.
We sent the following link to the customer:
http://<server>:<j2ee port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<SOAP sender communication channel>
One question: is the <service> the communication component used for the partner?
At the moment the partner receives a 500 error message. Due to our network partner the message reaches the PI system.
Due to the information I found that also a message parsing error can cause a 500 error message I would like to add the processing sequence:
Does anyone have an idea how to solve this problem?
Thanks a lot!
Regards
Christian

Hi Christian
You can refer to the following SAP Library link on how to configure the SOAP sender.
Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK - SAP Library
For the URL, the <service> is the Communication Component that the SOAP channel belongs to.
Using the example below, the value would be P_B2B_:BC_:CC_S_SOAP_
Actually SAP recommends a new alternative for the URL. If you scroll right to the end of the library link above.
You have configured the sender SOAP adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.
http://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelnameIf you have not created a party, enter channel=servicename:channelname.
http://hostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<&interface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<&interfaceNamespace>=name of the interface namespace
You can get this by generating the WSDL from the Sender Agreement object (Sender Agreement -> Display WSDL). The generated URL will be at the last section of the WSDL.
Also, please note that modules cannot be added to the SOAP sender adapter, also mentioned in the link.
You cannot add your own modules to this adapter.
An alternative would be to receive the EDIFACT Flat file as it is, and write it to at temporary File/FTP location. Then have a second channel pick it up, you can configure the second channel with module to convert it to EDIFACT XML.
Lastly, regarding the issue about the partner getting HTTP 500 error. Please check if you are able to see any error logs in the communication channel. It might give you some pointers as to what might be wrong - invalid sender agreement, etc, etc.
Rgds
Eng Swee

Soap sender Qos

Similar Messages

Maybe you are looking for