Debugging invokeMethod call

Dear All
When debugging OAF code using JDev, I normally use F8, F7 and/or SHIFT+F7 to step through the code.
The question is how do you 'Step Into' a method that is called using the an Application Module's invokeMethod API.
For example :
String result = (String)paapplicationmoduleimpl.invokeMethod("MyFunctionCalc",response);
now if I use the F7 when that line of code is being executed, I step into the actual invokeMethod source code, rather then MyFunctionCalc.
The work around I guess is to place debug merssages, i.e. System.out.println("..."); in that method and view the debug messages in the OC4J window.
It would be nice to step through the called method, when it was being called using the invokeMethod style.
Your help is appreciated.
Thanks
Patrice

So I place a break point in my MyFunctionCalc method in my AMImpl.
Then I just run the debug mode.
The execution will be halted at the point method.
Do I still use F8 to step through the code in MyFunctionCalc ?, or was F9.
Let me know
Thanks
Patrice

Similar Messages

Debugging RFC Calls

I was going thru the Blog
/people/michal.krawczyk2/blog/2006/01/17/xi-debugging-rfc-calls-from-the-xi-not-possible-who-said-that-
I am not understanding what Michal is trying to say? Would some one explain me please.
I understand that when we are talking to an RFC and error occurs how XI is going to handle.
Thanks

Thanks Michal.
Just I have listed what I have understood, please correct me. (I got confused with your naming conventions)
1) Existing RFC    : RFC-OLD (XI calls RFC_OLD)
2) Copy            : RFC-OLD_Copy
3)                 : Delete the function code in RFC-OLD
4)                 : RFC-OLD Calls RFC-OLD_Copy
DATA: queue_name like TRFCQOUT-QNAME.
*setting the queue name
queue_name = 'DEBUG_QUEUE'.
    call function 'TRFC_SET_QUEUE_NAME'
      exporting
        qname              = queue_name
      exceptions
        invalid_queue_name = 1
        others             = 2.
    if sy-subrc <> 0.
    endif.
*call the new function in the background *and passing all the parameters from the old RFC! *so we'll be able to debug the RFC with correct *parameters
CALL FUNCTION 'RFC-OLD_Copy'
in background task
destination 'NONE'
as separate unit
TABLES
    TABLESAMPLE       = TABLESAMPLE.
*remember about the commit work
Commit Work.
Endfunction.

How to debug dynamic calls

Hi Gurus,
Can any one tell me how to debug dynamic calls?
The scenario is:
I know the message that is getting fired from a message class.
I didnot find its usage from the where-used list, as it says - possible dynamic calls.
How do i know, from where this message is getting fired?
Pls suggest.
Thanks, Rashmi

Hi,
Just try this
In the new debugger Breakpoints --> Breakpoint at --> Breakpoint at Statement
give MESSAGE
This will set break point at all message statement. Execute till you get the message
Regards

Debugging inbound call - need debug command

I am debugging what I believe to be a dial plan issue on PGW but want to run a debug command on the ITP to show the actual called number of the inbound call.
What is the best debug command to use to see the inbound called and calling numbers of a call.

You are better off capturing an mdl trace from the PGW using per call tracing or using snoop and opening the call in Wireshark.
The ITP will only dump hex values and you will need to decode them yourself since it is not concerned with ISUP layer. You can use the cs7 paklog feature to attach an access list to a linkset and then send the raw data to a syslog server for decoding.
For example:
cs7 paklog x.x.x.x dest-port xxxx src-port yyyy
access-list 2700 instance x permit si all
debug cs7 mtp3 paklog 2700

Debug dynpro + call script form

Hello ,
I have a req, I need to debug the few dynpro, and one of the dynpro is calling a form and I have to figure it out, which form is this ( and from where it is called ). I have never worked with script form before, can any one let me know how I can figure it out that ( how to call a form, I mean it should be statemnt like, call form .... or ) ?
One another thing, I went into the coding, and there I see the screen ( in execution mode, the screen shows some button, ( e.g show , and after pressing this button show ,the form appers ), but when I went in flowlogic of the screen, I cant see those button ?
Any idea....
Regards,

Shah,
Do like this.You might be pressing some push button after which the smart form or script is appearing.
do screen debugging.
enter /h in the command field and press enter.
now press the push button.
this will take you to the logic in the driver program where the smartform or script is getting invoked.
if it is a smartform you will see a function module SSF_FUNCTION_MODULE_NAME.
smartform name will be stored in LF_FORMNAME
put a watch point here to get the smartform name.
if it is a script you will come across the following functional modules.
open_form,write_form,close_form.
Script name will be given in the open form functional module.
If any doubt revert it.
K.Kiran.
Message was edited by:
Kiran K

Can we debug programs called in background job?

Hi Everyone,
Here is my question:
I set some breaakpoints in program A which is call by another program B.
And in B, it defines a background job to run A.
but when i run program B , the berakpoints set in A don't work,why???
(I can not run A directly, for it needs a large amount of parameters which can't be input manually)
How to solve it? Thanks
Regards.

Hi,
Yes if it is a custom program.
Here how it works.
- Put a endless loop in your code.
- Run the program.
- Go to SM50 and select your process.
- Then go to Program/Session->Program-> Debugging.
- It will open the debugger. Now come out of endless loop by changing values and check whatever you want.
Regards,
pranaya

Automatically debugging when calling a script from a menu item

Hi All,
I'm coming accross an issue that I was wondering if anyone can help me with or point me in the correct direction.
I have two start up scripts.
One runs in the "session" target engine and setups ups some custom menu items and actions which call some other custom scripts.
The other runs in my own custom session and is used to initialize and share common constants and functions between my custom scripts.
This all appears to run as expected and clicking on the new menu item calls the correct script however even without the ExtendedScript Toolkit running as soon as i click on the menu item it will load up the ESTK and break on the first line of the script. If I press F5 to continue processing it will finish and runs fine.
I am currently using the excellent extendables package (http://extendables.org/) to do some HTTP and simplify UI creation which does not specify a session.
Does anyone know what is causing the scripts to be automatically debugged or is there a setting that might be set to cause this?
Is this being caused by "session" calling "customSession" using code that will run in the default "main" session?
this really is irritating me at the moment so if anyone can help it would be much appreciated.
This is all done using JavaScript in InDesign CS 5.5
Thanks in advance

just a quick update.
After stripping back and stubbing out some code I have been able to trigger a "session" going to my "customSession" then to a non-session (the default) so this is not causing my issue.
As I mentioned above i am using the extendables package and this appears to be where my issue is arrising. as soon as i include the package:
#include "extendables/extendables.jsx"
i get the strange behaviour of it going into debugging mode on the first line of the script being run by my menuItem eventHandler.
This is without actually using any of the modules available in the extendables package just including it.
I will try to post a message on the website for this package but if anybody has any ideas about what might be in there that is causing this I would appreciate any ideas/suggestions/theories.
Cheers

Debug RFC called from external system with no dialog user

Hi all,
We need to debug the rfc function module which is called from the external system( Siebel ) .
The user id is not dialog user so can not set external debugger.
Need you help.
Thanks,
Anmol.

Hi Suhas,
Nice to know you became Moderator...
Hmmm the solution you provided was the last option..
Any ways the issue is resolved we changed the user to dialog user and then debugged the code.
Thanks a Lot,
Anmol.

Debugging RFC-call in ERP-system

Hi experts,
I've a similar problem as decribed Values for FM structure not delivered as expected - but the opposite direction:
we send data from PI, which received a FTP-file, to ERP by RFC-Function.
last week we enhanced the output structure for this fm in PI (resp. in ERP: input structure)
result: the field is filled in the xml-file, which leaves PI - but the field comes blank into ERP-system
we've already emptied PI-cache!
is there any chance to debug the process in ERP-system???
thank you and regards
Andreas from germany

Hi Andreas,
We had the same problem.
Clearing all the caches and even restarting the PI system did not help.
Reactivating all the configuration objects for the specific scenario fixed the problem.
This means:
- sender agreement (if existing)
- receiver determination
- interface determination
- receiver agreement
- communication channel
If you want to debug the rfc that is called, insert an external breakpoint on the userid that is connecting from PI towards ERP (configured in receiver communication channel). You can change this userid via:
Utilities --> settings --> abap editor -->debugging --> external debugging userid
Hope this helps.
Kind regards
Joris
Edited by: Joris Verberckmoes on May 31, 2010 9:33 AM
Edited by: Joris Verberckmoes on May 31, 2010 9:36 AM

How to (can I?) debug EJB called from ABAP?

I have developed a small bean that I am calling remotely from ABAP. I have done the development work in the WebAS 6.40 Sneak Preview NetWeaver Dev. Studio. I cannot figure how (or even if it's possible) to debug this bean.
I have followed the instructions on debugging referred to elsewhere in this forum, but I'm hung up at the point where I'm to create a debug configuration. E.g., what kind of configuration should I specify? (EJB is not one of the choices.) If I try any of those that <i>are </i> available, I always get to a point where it says that it can't connect to the JVM. Well, that's not what I'm trying to do, is it?
Has anybody successfully done such debugging? If so, can you get me past this sticking point?
Thanks...

Hi David,
prerequisite to use debugging is, that the server you want to connect to runs in debug mode:
Open "Window->Show View->Other->J2EE->J2EE Engine". The configurated J2EE engine is displayed. Use the context menu of the "server0" entry to "Enable debugging of process". The server restarts then. If it's (already) running in Debug Mode, this is visible on the right side "Debug Mode = ON".
I suggest to define a "Remote Java Application" configuration like this:
Name: Whatever you like
Project: The project containing the classes to debug.
Connection Type: Standard
Host: Hostname or IP of J2EE server host
Port: 50021
Choose "Apply" and "Debug".
Set breakpoints for example by double-clicking on the frame on the left side of the Java editor (or using the context menu -> Add Breakpoint there). There's a very good documentation about debugger usage in the NWDS online help.
Trigger the remote call from the ABAP system. As soon as a line with a breakpoint is hit, the debugger displays the line and stops the active thread.
Hope that helps.
Regards
Stefan
PS: As soon as you don't need debugging any longer, disable debug mode of the engine, since it slows down everything.

Debugging EJBs called by JWS?

We built a stateless session EJB in Eclipse, deployed it to workshop domain,
and added the jar file to Workshop project's WEB-INF/lib. Our JWS calls this
EJB through an EJB control. Everything runs fine.
The question is: Is there a way to use WLW 7.02 debugger to single-step from
JWS into EJB's source code?
Thanks!
Ray

Hello Ray,
Unfortunately there is no mechanism by which you can debug into the EJB code
in WebLogic Workshop 7.0
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Ray Yan" <[email protected]> wrote in message
news:3ecec8fa$[email protected]..
We built a stateless session EJB in Eclipse, deployed it to workshopdomain,
and added the jar file to Workshop project's WEB-INF/lib. Our JWS callsthis
EJB through an EJB control. Everything runs fine.
The question is: Is there a way to use WLW 7.02 debugger to single-stepfrom
JWS into EJB's source code?
Thanks!
Ray

How can I debug the Call Library Function at run-time

I've written a VI using the CLF to call a DLL which was compiled off-site by another engineer using MSVC. Even though the VI runs without flagging any errors, the VI is not doing what I expect. Is there any way of finding out if the DLL is been called correctly? The first function that is called doesn't return any value, but I think that it should. Does this mean that the DLL is not being called correctly? Note also that the DLL works fine with a JAVA GUI.

Make sure that you are specifying the proper function prototype in the call library function. If you are slightly off the call will not work properly. Ask the offsite engineer to provide you with this data. Another tip is to build the dll with the option to show front panel when called. You can actually popup the dll like you would a subvi. If you design it with test indicators showing on the front panel that is a great way to determine if it is working. Hope this helps.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

Difference between invokeMethod vs direct call

I'm working in a company where there seem to be two ways that the developers called AM functions:
Direct Calling:
CompanyTakeoffAMImpl thisAM =
(CompanyTakeoffAMImpl)pageContext.getApplicationModule(webBean);
thisAM.runSalesFunction(pageContext.getSalesId());invokeMethod calling
CompanyTakeoffAMImpl thisAM =
(CompanyTakeoffAMImpl)pageContext.getApplicationModule(webBean);
Serializable[] userParam = { new Integer(pageContext.getSalesId()) };
Class[] userParamType = {Integer.class};
am.invokeMethod("runSalesFunction", userParam, userParamType);Is there any advantage / disadvantage to why we're doing this basic task in two different ways?
Which way is recommended?
Thanks

From the developer's guide:
+"If you need the server code to do some work for you, always route your calls through the root application module using the generic "remoteable" invokeMethod() method on the oracle.apps.fnd.framework.OAApplicationModule interface, or create an interface for your application modules so you can call typed methods, whose invocation can be checked at compile time. The application module can delegate or implement the logic as required."+
+"Note: The OAApplicationModule interface is in the oracle.apps.fnd.framework package and therefore, does not violate the rule stated in the first sentence of this bullet-point. All classes, interfaces, and exceptions in the oracle.apps.fnd.framework package can safely be used in both client and server code. If you opt to create an interface for your application module instead of using invokeMethod(), create this interface in the package directory immediately above your implementation. For example, the EmployeeAM interface for the oracle.apps.fnd.framework.toolbox.labsolutions.server.EmployeeAMImpl application module should be created in the oracle.apps.fnd.framework.toolbox.labsolutions package."+
Although I can't seem to find it at the moment, the developer's guide give the reason why you should not use AMImpl's from the controller. If I remember correctly, it has something to do with that it can't be assumed that the controller code will executed on the same tier at the AM.
The easiest thing to do it to create an interface as mentioned in the dev guide excerpts. This is quite easy to do. Double click your AM, then go to Client Methods, and shuttle over the ones you want to call from your controller. If your AM is custom.oracle.apps.fnd.server.MyAppModAMImpl, your interface will be custom.oracle.apps.fnd.MyAppModAM.
Just import custom.oracle.apps.fnd.MyAppModAM in your controller, and do:
MyAppModAM am = ( MyAppModAM ) pageContext.getApplicationModule( webBean );
This will also allow you to have compile time type checking.

When is it safe to call invokeMethod?

Working from the Trace.java example in the JPDA demo, I tried to insert some invokeMethod calls in one of the event handlers, to get supplementary information about the source of the event, but this always leads the tracer VM to hang in mid-air (i.e., the printout can be interrupted in the middle of a string) after a while, even though no exceptions are thrown.
The documentation for JDI is just awful: nowhere could I find anything amounting to a decent tutorial. Does anybody know when it is safe to make calls to the VM being traced and why I am seeing this behaviour?

I have to say that the lack of response on this forum and the scant documentation that come with the API reflect very poorly on JPDA.

How to get the debug sqlserver procedure calling from powerbuilder

How to get sqlserver debug while calling the procedure from PowerBuilder. Please can you help
Many Thanks
Pol

You are better off doing this through the native SQL server tools. You can debug your PB code to find the variables being sent to the stored proc (if any) from PB and then use them in SQL Server Management Studio or similar.

Debugging invokeMethod call

Similar Messages

Maybe you are looking for