Skip to Content
author's profile photo Former Member
Former Member

Degugging on a 4.6C Custom BSP_Framework (using Model View Control with HTML and JAVA) on Server X and HR/PY BAPI Application Functions on Server Y

We are struggling with the best way to DEBUG the RFC function calls from the MVC (Seibel) Z_BSP_Framework on our 4.6C system, which is using RFC calls to the BAPI HR/PY application Functions, which are primarily custom in nature. Due to the remote connectivity through the DCOM we have a very limited amount of time to debug. Generally the appliction will TIME OUT long before we have gotten to the program source which is causing a problem or is a suspect.

What is the best method or special technique we could us or exploit for debugging?

Also, how can we veiw the RFC calling sequence post motem? After the connection is lost!

Add comment
10|10000 characters needed characters exceeded

1 Answer

  • Posted on Feb 18, 2004 at 01:13 PM

    Usually debugging from a BSP application into another SAP system works straightforward. You just step into the RFC and continue the debugging in the back end system.

    The user used for the RFC in backend system needs debugging rights, of course.

    But you mentioned Java and DCOM, therefore I assume that several other parties are involved?


    Add comment
    10|10000 characters needed characters exceeded