Exception handling in client proxy

Hi
Can someone please help me with exception handling in ABAP client proxy.

HI
Welcome to SDN
Check this link you wil get information regarding ABAP Proxy http://help.sap.com/saphelp_nw04/helpdata/en/c9/74246d8ad2447799063d39013e9a11/content.htm

Similar Messages

Exception Handling in Client/Server Application

Hi All,
My application is a Server application that receives socket connections from a client which pass an image file, the server saves the file in a specified directory..
Some errors may appear during writing the file by the server, Socket or IO Exception may occurr( i.e. the network connection cut, no space on the disk....)
i noticed that the server terminates when an exception occurs. I catch this exception and handls it just by printing the exception message to the command line.
So when it occurs server prints the exception message then the application terminates.
I want to handle the exception in a way the server doesn�t terminate and also can receives more connections?
Note: i tried the case in wich there is no enough memory space so the server will copy the passed image file on the drive a.(floppy disk)
Here are my Server, Client source code ...
Server.java
import java.io.*;
import java.net.*;
import java.awt.*;
import javax.swing.*;
class Server{
public static void main(String[] args){
try{
System.out.println("Server Started.........");
ServerSocket ss = new ServerSocket(9999);
while(true){
Socket s = ss.accept();
System.out.println("Socket from : "+s.getInetAddress().getHostName()+ " "+s.getInetAddress().getHostAddress());
BufferedInputStream bis = new BufferedInputStream(s.getInputStream());
FileOutputStream fis = new FileOutputStream("a:/abc1.bmp");
BufferedOutputStream bos = new BufferedOutputStream(fis);
int c;
c = bis.read();
while( c != -1){
bos.write(c);
c = bis.read();
bos.flush();
bos.close();
fis.close();
bis.close();
s.close();
System.out.println("Complete");
}catch(SocketException se){
System.out.println("Socket Error : "+se.toString());
catch(IOException ioe){
System.out.println("IO Error : "+ioe.toString());
Client.java
import java.io.*;
import java.net.*;
import java.awt.*;
public class Client{
public static void main(String[] args){
try{
FileInputStream fis = new FileInputStream("abc.bmp");
BufferedInputStream bis = new BufferedInputStream(fis);
int available = bis.available();
byte[] b = new byte[available];
int read = bis.read(b,0,available);
bis.close();
fis.close();
Socket s = new Socket("localhost",9999);
BufferedOutputStream bos = new BufferedOutputStream(s.getOutputStream());
bos.write(b,0,available);
bos.flush();
bos.close();
s.close();
catch(Exception e){
System.out.println(e);
System.out.println("Complete");
thanx in advance.
shelal

Get the try catch block inside the while loop. In that case, even if an exception occurs, it is going to continue in the while loop.
Server.java
import java.io.*;
import java.net.*;
import java.awt.*;
import javax.swing.*;
class Server{
public static void main(String[] args){
try{
System.out.println("Server Started.........");
ServerSocket ss = new ServerSocket(9999);
catch(Exception e)
System.out.println("Server socket creation failed");
// you may wish to exit here.
while(true){
try
Socket s = ss.accept();
System.out.println("Socket from : "+s.getInetAddress().getHostName()+ " "+s.getInetAddress().getHostAddress());
BufferedInputStream bis = new BufferedInputStream(s.getInputStream());
FileOutputStream fis = new FileOutputStream("a:/abc1.bmp");
BufferedOutputStream bos = new BufferedOutputStream(fis);
int c;
c = bis.read();
while( c != -1){
bos.write(c);
c = bis.read();
bos.flush();
bos.close();
fis.close();
bis.close();
s.close();
System.out.println("Complete");
}catch(SocketException se){
System.out.println("Socket Error : "+se.toString());
catch(IOException ioe){
System.out.println("IO Error : "+ioe.toString());
}

Exception handling in synchronous proxy - web service scenario

Hi Gurus,
I have a synchronous scenario in which SAP is sending a request via XI using SOAP and receiving a response back. As part of this scenario, I am consuming standard web service APIs provided by the third party.
Since, every request has to contain the connecting user id and password provided by the third party, I am sending/receiving messages without SOAP envelop (achieved by clicking 'Do not use SOAP envelope' checkbox in SOAP Receiver Communication Channel).
For this scenario, we are including the user id and password in the request message using XSLT mapping and the request number using simple message mapping.
The fault message of the web service is being mapped to the fault message created in XI under Fault Message Types.
The interface mapping page has got 3 tabs, one each for Request message mapping, Response message mapping and Fault message mapping.
When I trying to test a failure scenario by giving an incorrect request number(since this is the only input parameter in gthe request message apart from user id and password), it is throwing up "MAPPING">EXCEPTION_DURING_EXECUTE error.
Actually, for such requests, I am getting a proper fault response back from the third party which I can see in XI (in moni) as response to my request but when I am looking at the message in moni in SAP, I am only seeing "MAPPING">EXCEPTION_DURING_EXECUTE. Even I can see the exception in the trace section of my response in moni in XI.
My feeling is that the fault message mapping is not getting executed at all.
I also thought to do a 2:1 multimapping in which, the target side will contain the response message type created in XI but the source will contain two messages, i.e. Normal response message structure provided by third party and Fault message structure provided by third party but I am not sure whether this is possible without using BPM.
Please suggest the best way to resolve this issue.

The Fault message raised from 3rd party service, is structured as follow ??
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
Content-Length: nnnn
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
       <SOAP-ENV:Fault>
           <faultcode>SOAP-ENV:Server</faultcode>
           <faultstring>Server Error</faultstring>
           <detail>
               <e:myfaultdetails xmlns:e="Some-URI">
                 <message>My application didn't work</message>
                 <errorcode>1001</errorcode>
               </e:myfaultdetails>
           </detail>
       </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Take a look here:
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
and to this standard document:
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/5946db5f693912e10000000a42189b/content.htm

Handling streaming attachments in Client Proxy

I'm no java programmer in any shape or form so I'm really struggling with a web service that I've created that utilizes streaming attachments. THe OEM test web page returns the attachment perfectly well in the SOAP response but I'm unable to harness the Java to deal with it in the client proxy code.
I created a proxy using the wsa command line utility but there is some java expertise required to code the 'main' class. Does anyone have an example of java code that takes the 'oracle.webservices.attachments' and returns it in a useful form to a calling application? In essence, what I'm looking to do is to call the proxy from pl/sql, and return the attachment as a CLOB.
Does anyone know of any examples of proxy java code handling this type of thing?

I've managed to create a proxy that saves the streaming attachment to a local directory (thanks to the info at this post: Re: Streaming Attachments
The problem I have is that I have to hardcode parameters into the HttpSoap11Client code like this:
public static void main(String[] args) {
try {
getxmlweb.proxy.HttpSoap11Client myPort = new getxmlweb.proxy.HttpSoap11Client();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
String pResId = null ;
String pFileName= null;
String pFilterStr = "sepa_region='North'";
String fileName = "/tmp/plain1.txt";
AttachmentFactory factory = AttachmentFactory.newInstance();
Attachments atts = factory.createAttachments();
myPort.getClob(pResId,pFileName,pFilterStr, atts);
The last line here is the call to the method that creates the response, I need to pass parameters to this call DYNAMICALLY. I've tried setting up parameters in the 'public void main' signature but it doesn't compile telling me it must be public static void main(String[] args). This is where my lack of JAVA skills are letting me down.
Can anyone see a way around this?

Abap Proxy exception Handling

Hi guys,
I've implemented the following scenario:
BPM Process where I've got a async receive (from a file receiver), a sync send (to an ABAP PROXY) and a send async (to a file sender).
The scenario is working great, I've catched 'Communication exceptions', and the proxy contemplates the necessary exception throwers too, but I'm now trying to Handle one specific exception. Imagine you force a dump, with a divide by zero in the proxy code...the proxy will dump and the XI gets a mapping exception (like is supposed to).
The exception is:
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
The thing is, I want to catch this exception on the mapping and handle it, so the bpm process sends the handle response with the file sender.
I've looked to Alessandro Guarneri blog, but it's a little bit different, because I don't want to throw an exception but I'd like to handle it....
Can you guys help me with this question?

Hi Vijaya,
I was able to catch the exception like you said, on the proxy side.
I'm trying to conceive some real and feasible dumps scenarios and for that I'm forcing dumps, and catching exceptions. Divisions by zero was one of the examples.
For division by zero I was able to catch it with a cx_sy_no_handler exception, but I've another example which I'm not being able to catch it.
I'm sendind an message e001(zisa), which will exit automatically from the function module. Am I able to catch that message? Meaning, can I catch it and treat it, instead of the system exiting the function and showing the corresponding message?Is there any cx_* ?
Even better, on sxmb_moni I get:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html> <body> <H1> 500 SAP Internal Server Error </H1> <B> Error message: </B> O centro nao existe ou nao esta preenchido. ( <B> type of termination: </B> ERROR_MESSAGE_STATE ) <BR /> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Internal Server Error Error when sending by HTTP (error code: 500, error text: Internal Server Error)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
So, the SOAP adapter receives something. If it's not possible to catch this exception on the abap proxy side, can I catch and map that soap adapter error text on the BPM side?
Thanks a lot for all of your attention

Exception Handling in Inbound Synchronous ABAP Proxy

Hi All,
I am implementing inbound synchronous proxy which has inbound ,outbound and fault message ( same of SAP-PI).
I am calling a FM inside inside the method. All the business logic is coded in the FM which also handles the exception.
The exception raised in the FM is captured in the MESSAGE table of type BAPIRET2.
During testing I found that the exception raised inside the FM( Message Table) is not passed to Fault message
which is in the proxy method( If sy-subrc 0, raise excption type MT_FaultMessage was coded after FM).
I found 5 instance under the Fault message exception.IF_MESSAGEGET_TEXT , IF_MESSAGEGET_LONGTEXT ,IF_AI_APPLICATION_FAULT~GET_RT_FAULT_TEXT,
GET_SOURCE_POSITION and CONSTRUCTOR.
Kindly provide the input how to pass the error text captured in MESSAGE TABLE of FM to the exception message MT_FaultMessage of Proxy
Regards
Alice Rebecca

Hi Alice ,
Please have a look at the below document which contains ways to handle different errors and exception.If you still have doubts please revert back .
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502a7f0e-e5d9-2910-5aa2-976a8ed8384f?QuickLink=index&overridelayout=true]
For more specific i.e to handle the retrun message from a BAPI go through the below link .I assuming that you have exception class already created and it is available in the Exception tab of the execute_synchronus .
[http://help.sap.com/saphelp_nw04/helpdata/en/25/a45c3cff8ca92be10000000a114084/frameset.htm]
Thanks,
Anjaneya .
Edited by: Anjaneya Bhardwaj on Jan 13, 2012 6:26 AM

Fault message handling in abap client proxy

Hi experts,
i have scenario like this SAPECC---XI---WEBservice
i was decided to using the ABAP CLIENT proxy in sender side and soap adapter communication in receiver side
i will be get the wsdl file form client
problem is i am in bit of confusion like am i need to create fault message for this asychronous scenario?
how can i create the fault message for this scenario(that WSDL) and how the abaperwill handle those error
thanks in advance

Hi.
You can use fault message but it won´t return a error to your ABAP Proxy because your interface is ASSYNC. The fault message generated will stop in Adapter Engine.
If you need a return of the error, you have to change your interface to Sync mode.
To get more information, follow the link below:
Fault Message Type
http://help.sap.com/saphelp_nwpi711/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
Best Regards.
Bruno

Client proxy Null pointer exception

Folks,
I have a problem with ABAP client proxy. The scenario runs fine, but a few messages does not enter XI pipeline with a null pointer exception in RWB. When I click on Message Content of these errored messages, I get
500 Internal Server Error
SAP J2EE Engine/7.00
Application error occurred during request processing.
Details: Error [javax.servlet.ServletException: null], with root cause [java.lang.NullPointerException: null].
Exception id: [00096BDD38BA00480003206B00002EE7000447B40745C832]
The strangest thing is if I retrigger the same message for processing from ABAP proxy, the message gets processed successfully.
Even in the successfully reprocessed errored message, I am not able to view the message content. I am able to view the message content in SXMB_MONI with out any problem.
Any ideas what could be the reason.
Thanks in Advance.
Regards,
Jaishankar

Hi Ramakrishna,
I doubt Timeout is the cause for this problem coz. we used to get Time out errored messages apart from the Null pointer Exception messages. When I resend a Timedout message from RWB it gets processed sucessfully. But when I resend a null pointer exception message from RWB, the same error occurs again. Only if I resend the message from R/3 it is getting processed successfully.
I will try this setting too. Thanks for sharing.
Regards,
Jaishankar

Exceptions while creating ABAP client Proxy

Hi Experts,
I tried to create a client proxy on the CRM system for a web service URL (where the WSDL exists), in the transaction SE80.
When I tried creating this, i got exception as follows.
Exception occured in communication framework:error in HTTP framework:404 conn failed http://inld50054696a:8080/clearspace/rpc/rest?forumservice?wsdl
Please let me know, how to tackle this problem.
What are all the settings that needs to be done in this regard.
Regards
Lakshman

Have you verified that your SAP system is set up to be able to send messages out over http? Our firewalls caused the same problem- by configuring proxy settings in transaction SICF we worked around the error.
Hope that helps!
Abby

Exception when creating ABAP client proxy using WSDL

Hi Experts,
I tried to create a client proxy on the CRM system for a web service URL (where the WSDL exists), in the transaction SE80.
When I tried creating this, i got exception as follows.
Exception occured in communication framework:error in HTTP framework:404 conn failed http://inld50054696a:8080/clearspace/rpc/rest?forumservice?wsdl
Please let me know, how to tackle this problem.
What are all the settings that needs to be done in this regard.
Regards
Lakshman

Hi Vasanth,
There are many threads and blogs on this topic.
Choose the search Forum on the Forum page and select "All categories" in the Category field and enter your topic "ABAP client proxy from WSDL" in the search field.
Rgds,
Sam Raju

Exception handling in outbound ABAP proxy

Hi All,
i need to catch exception in outbound abap proxy in two cases:
1. if RFC dest in R3 which is pinging to XI goes down.
2. IF xi server is down.
in both the cases i need to catch the exceptions.
now i written the code in this way:
DATA: v_exceptions TYPE REF TO cx_ai_system_fault.
TRY.
CALL METHOD zirco_o_msg_if_as_req_details=>execute_asynchronous
EXPORTING
output = s_reference.
COMMIT WORK.
CATCH cx_ai_system_fault INTO v_exceptions.
WRITE: 'Exception CX_AI_SYSTEM_FAULT caught'.
WRITE: / v_exceptions->errortext.
WRITE: / v_exceptions->code.
but this code is not working.
can anybody tell me how can i acheive this?

Hi All,
I need to log the error when receiver syatem is down.
Its like this:
Outbound proxy >>>XI>>>File adapter..
Now if xi goes down....means message is succussefully sent from ISD and get stuck in XI then i need to catch this exception in ISD.
Is it possible?? if yes then how??
Kunaal

Error while creating Client Proxy from SE80

Hi all,
I am trying to create Client Proxy with WSDL through SE80. There is no involvement of XI to create the Proxy.
I am using the option 'Local file' and uploading the wsdl file.
But I am getting the following errors.
"Proxy-Generierung: Fehler aufgetreten"
"Exception occurred in library handler"
"Illegal syntax: Element header has invalid enhancement attribute
http://schemas.xmlsoap.org/wsdl/:required"
If any one could understand them and worked in a similar scenario, pls help me out.
regards,
teja.

hi,
you might want to post the WSDL in question for us to have a look at.
but actually, the error message tells a lot:
http://schemas.xmlsoap.org/wsdl/:required
the second colon(, the one between wsdl/ and required, makes this expression an illegal one in any kind of a URI-like meaning (namespace, ref-URL, ...)
anton

Client Proxy Question

Hi all,
Initially, when we have created a client proxy in ECC 5.0 with Oracle on Windows,
we have chosen Local File as the WSDL source. We had the WSDL saved locally.
This way we have generated a Client Proxy in SE80.
Then we created a logical port using LPCONFIG.
Since this the default logical port, we just saved it with all the settings imported
from the WSDL definition.
This way the Client proxy was working fine.
The doubt that I have is, later on, if we want to just change the URL under
call paramters in LPCONFIG to the URL of the WSDL residing on some
other server(Non SAP), will the client proxy work?
Regards,
Vishnu

Hi Gaurav,
Looking at the error below, the binding is happening.
However, there is a return code 503. And SAP is not able to access the
Webservice located at the other server(Non-SAP).
INFO 01:44:43: SOAP SESSION Protocol CL_SOAP_SESSION_PROTOCOL
->IF_SOAP_PROTOCOL~PRE_PROCESS() SOAP Session Protocol
preprocessed
INFO 01:44:43: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT
->IF_SOAP_TRANSPORT_BINDING~SEND() Try to send message ( DEST =
,PATH = ,URL = http://server name:portno/ ,SOAP Action = "ROI_R3
_DF.roiSAPCreateOrder" )
INFO 01:44:43: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT
->IF_SOAP_TRANSPORT_BINDING~SEND() Message sent
INFO 01:44:43: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT
->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message
INFO 01:44:52: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE
_STATUS_CODE() Received return code 503 ( not available )
ERROR 01:44:52: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE
_PART~INIT_FOR_DESERIALIZE() A SOAP Runtime Core Exception
occurred in method XP_READ_TAG of class CL_SOAP_XP at position id
1 with internal error id 112 and error text no extended error
message (SOAP_ESERVER) (fault location is 1 ).
Regards,
Vishnu

Error when create client proxy in ABAP

hi all
when I tried to create a client proxy through wsdl: http://www.webservicex.net/geoipservice.asmx?wsdl , I got and error message "Exception occurred in library handler", what's the really matter with this error ?
thanks very much!

You need to copy the WSDL file to a local file and edit it. The WSDL file contains non-SOAP bindings and that's what the generator is choking on. Use the 'Local file' option to generate the proxy class after editing the file.

Exception handling with fault message type not working

Hi,
I have a sync proxy to proxy scenario and I have created a fault MT and specified in the outbound and Inbound service interface...
*In Inbound proxy I have the following code--*......
RAISE EXCEPTION TYPE z_cx_test_fault
EXPORTING
standard = l_standard_data.
In the sender side abap code which calls the outbound proxy I have the follwing code -
CATCH cx_ai_system_fault INTO lo_cx_ai_system_fault.
txt = lo_cx_ai_system_fault->get_text( ).
WRITE txt.
CATCH z_cx_test_fault INTO lo_cx_test_fault.
txt = lo_cx_standard_message_fault->get_text( ).
WRITE txt.
CATCH cx_ai_application_fault INTO lo_cx_ai_application_fault.
txt = lo_cx_ai_application_fault->get_text( ).
WRITE txt.
when i test the inbound proxy separately I get the custom fault message properly...
however when i run the proxy to proxy sync scenario and the custom exceptionz_cx_test_fault is raised inside the receiver proxy .......control goes to CATCH cx_ai_application_fault and not CATCH z_cx_test_fault .
I understand that cx_ai_application_fault is the super class of all the exception class but why does control go to its exception handling when a custom exception is raised...
Edited by: hema T on Feb 26, 2012 1:16 PM
Edited by: hema T on Feb 26, 2012 1:17 PM

Hi
I tried changing the sequence also but it did not work...
I can see an appropriate response coming from the receiver in SXMB_MONI of PI...this response has the "fault response "
"fault detail" data that I want.....however when the control goes to the sender why does it go to CATCH CX_AI_APPLICATION_FAULT and not not my CATCH z_cx_test_fault .
My observation - If I change the scenario to SOAP to Proxy sync..then the sender SOAP client gets the appropriate custom fault message back.
Edited by: hema T on Feb 27, 2012 1:17 PM
Edited by: hema T on Feb 27, 2012 1:17 PM

Exception handling in client proxy

Similar Messages

Maybe you are looking for