Timeout in synchronous SOAP-Proxy communication

Hi,
I have a synchronous SOAP-Proxy communication (3rd party - XI - ERP). 3rd party is always the initiator of the communication.
Is there a general rule about who should set a timeout? Does it should be set by a 3rd party, XI, or ERP? In our scenario it shouldn't be longer than 30 seconds.
If it needs to be set on SAP side, where it should be defined? On XI or on ERP, or on both systems?
Which SAP parameter is used for setting the timeout for synchronous communication that does not affect other already working ways of communication, like asynchronous.
Thanks for answers.
Janos

Hi,
The timeout property needs to be set at XI level. For SOAP sender timeout check sap note no. 856597 which reads as 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.
Thanks!

Similar Messages

Alert in synchronous SOAP- PROXY scenario

Hi,
I am woking on a synchronous SOAP- PROXY scenario. The XI outbound interface has been exposed as web service which is invoked by .NET application to send the request. The inbound interface is ABAP proxy which is retrieving the data from R3 tables based on the selection criteria in request and sending back the same as response. Now it is required to send an alert to the specified recipient in case there is any application error on the receiver side.
Please help.

Now it is required to send an alert to the specified recipient in case there is any application error on the receiver side.
Check this thread on similar topic....see my reply: Re: raising sap alert in case of "Application Error"
Regards,
Abhishek.

Error in synchronous( abap proxy to soap)scenario

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
configuration steps are
1. only client proxy to soap scenario I have done.
communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
Already we have RFC destination connection and connection type H for proxy to xi.
1.Is it required RFC destination connection for xi to server proxy.
2.Is it required receiver proxy communication channel for server proxy?.
i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
error is:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
Kindly help me.
advance thanks
thanks and regards
elton
Edited by: eltonsaranya on May 9, 2011 10:27 AM

Your exception message shows problem at the webservice side.
Check the following:
a) you need two mappings one for proxy req to soap request and other soap response to proxy response
b) You need to create service interfaces both sender and receiver synchronous .
c) communication channel QOS is best effort for both sender and receiver
d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
f) See your SOAP response structure matches with WSDL provided.
g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI for that web service. So that you know whether problem exists on the target system or not.
Hope that helps.

Synchronous abap proxy to sysnchronous soap: complex problem

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
client proxy to soap(request) i have configured. But when I am doing the configuration for soap to server proxy(response) I am not able to get the message interface name in the configuration.
Note: In the soap BS_HRS_DEV business system receiver only we will get the message interface.
but we cannot get sender side in the same business system BS_HRS_DEV find message interface. as we are aware as a synchronous scenario both side we have to get the message interface(sender and receiver BS_HRS_DEV).
2. what are the configuration steps i have to do for response message
Kindly help me.
advance thanks
thanks and regards
elton

Hello,
client proxy to soap(request) i have configured. But when I am doing the configuration for soap to server proxy(response) I am not able to get the message interface name in the configuration.
In a synch scenario, you only need to configure it like it is an asynch scenario. The only exception is that the service interfaces are synchronous. Each synch service interface requires at least two messages (request and response), fault message is optional. So for your scenario, at least four messages are required
1.) 1st message (Outbound request) -> Proxy message type request that will be entering PI
2.) 2nd message (Inbound request) -> Soap request message type going to the webservice
3.) 3rd message (Inbound response) -> Soap response message type from webservice going to PI
4.) 4th message (Outbound response) -> contains the message type that has the values that you want
So the flow could be like this (fault messages not shown)
Outbound SI (1) -> PI -> Inbound SI (2)
(4) <- PI <- (3)
what are the configuration steps i have to do for response message
No additional steps in ID. Just make sure you handle the mapping of response message in ESR (if you have one)
Hope this helps,
Mark
Edited by: Mark Dihiansan on May 3, 2011 10:01 AM

SOAP------ PROXY--ASYNCHRONUS communication

iam working on SOAP-> Proxy (asynchronus) scenario, my requirement is send change master data from client system to SAP via PI, once the data is updated in SAP, need to sendback the status/eror messages , here the iam using the same XML structure for input and output,
can you please explain in details, what are steps need in developed in design and configuration.
Thanks for your time
Regards
neeru

Hi Neeru,
Using the message ID and the CL_PROXY_ACCESS=>GET_ACKNOWLEDGMENT( [Message ID] ) method you can get and evaluate the acknowledgment object.
Using the acknowledgment object you can query whether acknowledgments were received.

JDBC to Synchronous ABAP Proxy

Hello,
I have one scenario where i am sending data from JDBC Adapter(Communication Channel 1) to ABAP Proxy(Sync)(Communication Channel 2) and as response ABAP Proxy send back data to JDBC Adapter(Communication Channel 3). So is it possible without BPM?
And in above scenario in SXMB_MONI of R/3 and PI 7.1 it shows "Type = Asynchronous" and in R/3 it shows Payload in Response but when i check in PI 7.1 SXMB_MONI there is no message in Payload of 'Response' .
Please suggest me the solution.
Thanks in advance.
RP

YES , WE CAN ...
We can use JDBC Adapter at your DB Side and At R/3 side we can have RFC or Proxies for Sync
By default JDBC Adapter dont have the nature of requesting the Ack(Response from the receiver)
So to make it Sync We have to use BPM
JDBC Synchronous call using BPM
How to uses JDBC Adapter for the following scenario ?
Steps to be followed for the same:
SYNCHRONOUS SOAP TO JDBC - END TO END WALKTHROUGH
ABAP proxies have many advantages for instance; they communicate with the XI server by means of native SOAP calls over HTTP (RFC does not, so you have to convert from SOAP to RFC calls and vice versa). ABAP proxies supports two different protocols; XI and Web Services. Most important is that they can be used for both synchronous and asynchronous communication (RFC/BAPI is basically only intended for Synchronous comm. which asks much more system resources from your XI system).
step by step RFC to JDBC scenario
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/step%2bby%2bstep%2brfc%2bto%2bjdbc%2bscenario

Error in the SOAP Receiver communication channel

Hi ,
My scenario is RFC - to -SOAP (synchronous ) i have specified the TARGET URL inthe SOAP receiver comminication chanel.. but while testing the interface by providing the test data from R/3 .. I'm not getting any Respose.. ..
If I check in the SXMB_MONI in i'm getting the following message .. but the URL whicjh i provided that is fine.. but my doubt is through XI may be it's not able to connect the Target System... .. so, please suggest me...
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: www.webservicex.net</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
regards
Jain

By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Also have a look here
SAP Note 856597
reward points if solution found helpfull
regards
chandrakanth

Error in calling SOAP receiver communication channel in a syncronous comm

Hi I am getting the following dump..when I am sending some employee data from SAP to a webservice through a SOAP reciver communication channel.
It is a syncronous communication.
ShrtText
    Access with 'ZERO' object reference not possible.
What happened?
    Error in ABAP application program.
    The current ABAP program "CL_PROXY_FRAMEWORK============CP" had to be
     terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_REF_IS_INITIAL', was
     neither
    caught nor passed along using a RAISING clause, in the procedure
     "XI_PROCESS_PAYLOAD" "(METHOD)"
        The reason for the exception is:
    There was an attempt to access a component using a 'NULL' object
    reference (points to nothing).
    An object reference must indicate an object (an instance of a class),
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using a
    CLEAR statement.
Trigger Location of Exception
    Program                                 CL_PROXY_FRAMEWORK============CP
    Include                                 CL_PROXY_FRAMEWORK============CM011
    Row                                     46
    Module type                             (METHOD)
    Module Name                             XI_PROCESS_PAYLOAD
I think this error is coming while sending the response..can anybody tell me how to correct this error...
Thanks in advance...

No in the adapter monitoring...
It shows the messages for all other adapters...
But there is not even a single processing message for this SOAP communication channel...it only shows active..that means I think there is no processing of messagethrough this ..is it ?...but why not there is any error in the SXMB_MONI..
Earlier it was giving an error saying the proxy authentification required..but that doesn't work...now I have removed the proxy settings ..and it takes the program to dump..

Problem with Synchronous abap proxy time out

Hi there.
I have the following scenario:
                  sync                   sync
3rd party <--> PI    <--
> ERP
                   http                    abap proxy
In the implementing class on the abap proxy i'm calling an standard BAPI, followed by a commit and returning the result.
The 3rd party app has a mechanism that when a message fails, he'll retry each 5 mins until it gets the response.
Last night there where some delays on ERP that cause the sync mesages to timeout, the 3rd party retried about 10 times to send the message until it finally went off. This morning i check and i have the same message 11 times on ERP!!, to my understanding if the sync comm timed out the process will abort and the message will not be processed on ERP, does anybody knows if im missing some configuration for this to work this way??.
Kind Regards,
Roberto.

Hi Roberto.
There are a lot of time out configures in PI .
Follow the link that explain about this:
How to Investigate Timeouts In Synchronous XI PI Scenarios
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747
I hope to help you.
If you still keep this problem, you can ask me more about it.
Regards..
Bruno.

Error handling using fault message type in outbound synchronous ABAP proxy

Hi,
We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
Source Structure
Req_Proxy
    req (0..unbounded, string)
Response Structure
Resp_SOAP
Resp (0..Unbounded)
       respString (0..1, String) (carries the actaul response message)
      status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
Please calrify.
Thanks.
Rohit

For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
for valid and 2 for invalid accordingly.
Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
Regards,
Abhishek.

Synchronous SOAP to RFC

Hi All,
I have a doubt that in a Synchronous SOAP to RFC/PROXY interface that is it we need to configure the entire Interface and then have to test the Webservice for the response from Altova??
I have configured SOAP at the sender and RFC at the receiver but my Customize BAPI is not yet ready but I want to test the Webservice from Altova,Is it so that i need to configure the whole scenario and test it.
Isnt it enough if I do basic Configuartion??
Thanks & Regards,
R.K

hi,
if u want to test u r WEBSERVICE using altova spy... u need not configure whole scenario.. configure simple soap to file scenario and check u r webservice..
if u want to check syncronous scenario... for the testing use a BAPI which is already existing..
Thanks,
Madhav
Note:Points if useful

Synchronous SOAP: Get fault message on ABAP side

Hi,
I've a synchronous ABAP Proxy => PI 7.11 => SOAP scenario.
The SOAP receiver is a third party application using AXIS 1.4.
When I call the SOAP receiver with bad input via SOAP UI I receive an error message like that:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server.userException</faultcode>
         <faultstring>com.ZZZ.exception.ZZZException: Employee not found: 9999911111</faultstring>
         <detail>
            <com.ZZZ.exception.ZZZException xsi:type="ns1:ZZZException" xmlns:ns1="http://exception.ZZZ.com"/>
            <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">server.YYY.com</ns2:hostname>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>
When I call the SOAP receiver through my ABAP proxy, I just get this exception message in SXI_MONI:
<?xml version="1.0" encoding="UTF-8"?>
<com.ZZZ.exception.ZZZException xmlns:ns1="http://exception.ZZZ.com"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:ZZZException"/>
Nevertheless I see the error in SXI_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>Application</SAP:Category>
    <SAP:Code area="SOAP">FAULT</SAP:Code>
    <SAP:P1>http://schemas.xmlsoap.org/soap/envelope/</SAP:P1>
    <SAP:P2>Server.userException</SAP:P2>
    <SAP:P3/>
    <SAP:P4/>
    <SAP:AdditionalText>com.ZZZ.exception.ZZZException: Employee not found: 9999911111</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="">com.ZZZ.exception.ZZZException</SAP:ApplicationFaultMessage>
    <SAP:Stack/>
    <SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the WSDL of the SOAP receiver there's just the ZZZException without fields faultcode or faultstring:
<complexType name="ZZZException">
<sequence/>
</complexType>
Do I have to add the fields faultcode or faultstring to the WSDL myself?
I tried the following, but it didn't work:
<complexType name="ZZZException" abstract="true">
    <xsd:sequence>
        <xsd:element name="faultstring" type="soapenc:string">
    </xsd:sequence>
</complexType>
Thanks in advance!

Hi Eddie -
Do I have to add the fields faultcode or faultstring to the WSDL by myself?
>>> No. Even though you add - it doesn't work as it's the webservice which returns the message.
For sending the fault messages, Have a look at the below blog -
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI

R/3 to xi connection for proxy communication

hi guys,
can anyone provide me with the settings on both the ends, of the xi server with an r/3 server for proxy communication as i am having difficulty setting the systems up.
it would be really g8t if someone could give a step by step procedure to followed at both the ends.
thanking you in advance,
regards,
rajeev

Hi,
Applications based on SAP WEB AS version 6.20 or higher can communiate with the XI in the native XI-SOAP format via proxies. All other applications, including "legacy" SAP systems (those on the Basis releases lower than version 6.20), communicate with the XI via Adapters.
ABAP Proxy Scenarios:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
--Archana

Synchronous server proxy trigger

Hi All,
i have a interface like webservice <--> SAP XI <--
> SAP (Synchronous).
we decided to go SOAP ---Proxy interface is it correct way?
if it is correct then how we trigger the SAP report when we got the input from the webservice it should online.
when ever user enter the input it should come to SAP and based on that input SAP will provides the inforamation related to that input.
please let me know about do we need to do any ABAP coding for trigger?
thanks In advance

>> i have a interface like webservice <--> SAP XI <--
> SAP (Synchronous).
>> we decided to go SOAP ---Proxy interface is it correct way?
Yes
>> if it is correct then how we trigger the SAP report when we got the input from the webservice it should online.
You don't need to trigger anything( XI will take care of it at runtime )
>> when ever user enter the input it should come to SAP and based on that input SAP will provides the inforamation related to that input.
User will provide input which will be pushed to XI via SOAP adapter. XI will push the input to SAP via proxy
>> please let me know about do we need to do any ABAP coding for trigger?
You need to do ABAP coding for the server proxy i.e you need to do coding for the business logic( converting input to output as per requirement); no coding for trigger etc
You could proceed as follows:
1. Built two service interfaces in XI - one outbound( for SOAP) and another inbound( for Proxy)
2. For the inbound interface, generate the proxy in the SAP system
3. Within this proxy, embed ABAP code for business logic
4. Do configuration for adapters
5. Generate the WSDL from outbound interface and provide it to the user
rgds

Undesrtanding Proxy communication with the Integration Engine

I want to understand all the process in a client proxy communication. I know that the Local integration engine sends a PI-SOAP to the Central Integration Engine, and the local integration engine makes the communication with the ICM in the SAP PI side. My question are the next:
1. SAP documentation mentions that the XI Adapter is necessary. Where is it located?, after or before of the ICM in the SAP PI side. What is it function?, because the message is already in PI-SOAP format.
2. How does the local integration engine send the PI-SOAP message? Does it need an XI-Adapter ?.
Thanks in advance.

HI,
1. SAP documentation mentions that the XI Adapter is necessary. Where is it located?, after or before of the ICM in the SAP PI side. What is it function?, because the message is already in PI-SOAP format.
2. How does the local integration engine send the PI-SOAP message? Does it need an XI-Adapter ?.
-->XI Adapter is necessary only at the receiver side not at the sender side, by using proxy pre-configuration steps and proxy framework message from the sender system(Client proxy) will reach PI system. So, in this case XI adapter is not necessary(adapterless communication).
Proxy Framework which consists of Proxy Generator and Proxy Runtime:
Proxy Generator- Converts ABAP corresponding elements to WSDL corresponding elements and viceversa and by using Proxy Runtime, local Integration will be connected to Central Integration.
When a request is sent form client proxy-->ABAP corresponding elements will be converted to WSDL elements and local integration engine will be connected to central integration engine and whole process will be done.
If the receiver system is SAP, and since there can be many SAP systems connected to PI, to send data from PI to that particular receiver SAP system, PI needs the receiver system details like business system name etc. So, XI adapter is manadatory only at the receiver side.
check out this blog for more info:
[http://www.****************/Tutorials/XI/ABAPProxy/page1.htm]
Regards,
Sunitha

Timeout in synchronous SOAP-Proxy communication

Similar Messages

Maybe you are looking for