Debugging a RFC call using JCo API, Part-2

In my previous weblog Debugging a RFC call using JCo API I wrote about how to analyse the dump of RFC call. In case the result is not what is expected we can further drill down to debugging into the function module’s ABAP code.

In order to enable the ABAP debugging we need to call the function setAbapDebug(boolean) defined in JCO.Connection with true as parameter.

Code snippet:

// Defining a conncection variableJCO.Client connection; // Creating a JCO.Client objectconnection = JCO.createClient(“000”, // SAP client “USERID”, // userid “passwd”, // password “EN”, // language (NULL for default language) “appserv.host.corp”, // app. server host name “016”); // system number// Opening the connectiontry { connection.connect();}catch (Exception ex) { ex.printStackTrace(); System.exit(1);}JCO.Repository mRepository; mRepository = new JCO.Repository(“MyFunctions”, connection); IFunctionTemplate ft = mRepository.getFunctionTemplate (“ZANY_RFC_MODULE”); JCO.Function function = ft.getFunction(); connection.execute(function); connection.setAbapDebug(true);

This will launch the ABAP debugger in a separate window when the Java program is run.

ABAP debugger:

Further details about how to use the ABAP Debugger can be found at ABAP Debugger Documentation.

4 Comments

You must be Logged on to comment or reply to a post.

Former Member October 3, 2005 at 1:04 am

also in production scenarios(when setAbapdebug(true) cannot be turned on) if in some cases the ABAP processing initiated from java is under some sort of infinite loop then navigate to SM50 click on the rogue work process and initiate debugging through menu Program -> Debugging

like (0)
Former Member January 3, 2006 at 1:13 am

I tried to start debug ABAP code from java by placing a statement mConnection.setAbapDebug(true), but still it doesn’t show the expected results.

Are there any pre-requisites to be done, like starting ABAP RFC in debug mode or java program in debug mode. I tried both these options but didn’t get any result.

Your help is greatly appreciated.

The code is as follows :

          try {
               mConnection = JCO.createClient(“005”, // SAP client
               “TEST_USER”, // userid
               “initial”, // password
               “en”, // language
               “us4456.wdf.sap.corp”, // application server host name
               “77”); // system number
               mConnection.connect();
               mRepository = new JCO.Repository(“test”, mConnection);
               JCO.Function function1 = this.createFunction(“ZSTATUS_TRANSLATE”);
               function1.getImportParameterList().setValue(“DONE”, “IV_STATUS”);
               mConnection.execute(function1);

               mConnection.setAbapDebug(true);
               String output1 =     function1.getExportParameterList().getValue(“EV_STATUS”).toString();
               System.out.println(“The output of the RFC is “+output1);
               mConnection.disconnect();
          }
          catch (Exception ex)
           {
               ex.printStackTrace();
               System.exit(1);
          }

like (0)
1. Former Member January 3, 2006 at 7:14 pm
  
  The problem is solved by doing two settings :
  
  1) There is change in the code given in the blog, the connection.setAbapDebug(true) should be given before execution of the function.
  
  2) enabled external debugging in the backend, go to Utilities -> Settings -> Debugging and check the External Debugging check box, and enable HttpSession Debugging.
  
  This starts Abap Debugger :))
  
  like (0)
  1. March 23, 2006 at 1:03 pm
    
    Just curious where you are setting external debugging as I don’t have that on our backend we are on 4.6C is there a trxn code to start from or another screen besides the first one after log in
    
    Thanks so much 🙂
    
    Cheers,
    Devlin
    
    like (0)

Debugging a RFC call using JCo API, Part-2

Former Member

4 Comments

Leave a Reply Cancel reply