SOAP Sender timeout

Hello guys i have a simple problem :
SOAP <=>XI<=>RFC ; where as this states SOAP is sender, everything works fine but when sending SOAP request using XML spy the request reaches XI and becoz of large data its returning , the xml spy is timing out saying HTTP post error but indeed XI is processing this message and i see response coming back in sxmb_moni?
Any help will be greatly appreciated.
Reddy

Hi,
Refer SAP Note - 856597 Question No1 , 893713 ( for Receiver timeout)
ALso look into this blog
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
REgards,
Moorthy

Similar Messages

SOAP: "XI.Timeout" module in the sender adapter

Hi,
Could you please explain in detail, how to enter the XI.timeout module in the soap sender adapter.
Regards,
Vishnu.

Hi Vishnu,
The default timeout value for synchronous calls is 5 minutes. You can increase this value by setting parameter XI.Timeout in the module parameter table of the SOAP adapter. The value must be given in milliseconds. For example, value 600000 represents the timeout value of 10 minutes. This parameter is not recognized in systems prior to SP13.
In the Module tab of the Communication channel you can find Module Parameters can be specified under Module Configuration section.
Add the XI.Timeout Parameter with some Parameter Value.
regards
Ganga

'Keep Header' Option in SOAP sender adapter not working

Hi all
I have exposed a webservice using a SOAP sender adapter in XI. A SOAP client is sending request to this service.
The SOAP request has some elements in the header like wssecurity and ws addressing tags.
When I remove the header elements and send the request my scenario works as expected but when I include the header fields I get a time out in my soap client application and cannot see any message, any where on XI. Can somebody help me understand why this is happening.
Thanks
Dilip

Hi Stefan
In my scenario it is ok if XI ignores the soap header tags it does not understand. I want the system to ignore the header tags and go ahead and process only the payload.
But unfortunately I keep getting a time out whenever I send a request with the header tags. When I remove the header I can sucessfully post documents.
I tried increased the time out to 5 min but still continue to get the problem. So am sure the problem is not exactly related to timeout, but due to the header tags.
What do you suggest?
Regards
Dilip

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 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.

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...

Problem: Original Attachment Name from SOAP Sender changes to attachment-1

Hi everybody,
we have a scenario where a SOAP sender receives a xml message describing several documents. Each document has a mime type and a file name, size, md5 checksums etc as attributes.
The documents are send as attachments with the same Web service in SWA(SOAP with attachment style).
The web service calls an ABAP proxy provider class in a R/3 backend.
The ABAP proxy class will save the attached documents for further processing and must use the original document names.
At the soap communication channel monitoring(Java Stack) we still see the original attachment names in the message content tab.
At the Integration Server(sxmb_moni) the attachment name changes to attachment-1, attachment-2 and so on.
Using the method
IF_AI_ATTACHMENT ->GET_DOCUMENT_NAME
in the provider ABAP proxy class returns the name attachment-1.
We can see that there is a mapping of the new attachment-1 name to the old, original name in the manifest section of this message on the Integration server.
Is there a way to access the manifest section at a provider ABAP proxy class? Or otherwise a PI configuration setting to preserve the original attachment names.
Thanks a lot,
Heiko
=> PI 7.1 SP9

Hi Stefan,
(I was hoping you would find that thread ...)
I see a good reason why the attachment names are changed as the PI message protocol sends the main document as an attachment as well. So no problem with that because the information of the mapping old to new names still exists in the manifest part and is visible at the sxmb_moni.
We see a manifest part like this (Sorry cant post the whole xml doc as the formatting for longer messages isn't working in the forum)
<SAP:Payload xlink:href="cid:4cc43edd-839f-423f-b7c6-7e44294d663a_sig.p7m">
<SAP:Name>attachment-1</SAP:Name>
<SAP:Description>attachment</SAP:Description>
<SAP:Type>ApplicationAttachment</SAP:Type>
</SAP:Payload>
The (red) cid entry is the original file name. This manifest is from the sxmb_moni in the r/3 backend. So all the information is there.. The question is how to retrieve this information .. Any idea?
Best Regards,
Heiko Bergmann

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

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

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

SOAP Sender to RFC Scenario WSDL File

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

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

SOAP Sender timeout

Similar Messages

Maybe you are looking for