SAP跨系统的DEBUG方法(轉)

    有2个条件必须满足

    1. 系统间连接的RFC 用户是dialog用户

    2. 你的用户有可以设置这个debug用户的权限

    debug过程如下

   

1． 設置 external breakpoint

 

 

2．Utilities －》setting －》debugging，設置users id，并且active

3．請外部系統執行，他們那邊call到rfc時，會停下來，而我們這邊會彈出一個debug窗口。這樣就可以monitor傳入的參數及傳出參數了。

 SE30:

There are also often situations where you need to trace HTTP or RFC requests or processes of other users. Let me give you some examples.

Imagine there is an online flight booking system. If a user wants to reserve a flight, his HTTP request arrives in your backend system. And you need to trace the reservation process which is running in your ABAP backend system. In such case you don't know which ABAP backend process handles which HTTP request and have no idea when the HTTP request will reach your ABAP backend system. Therefore it is difficult to capture such a request for debugging in the appropriate ABAP backend process.

Another good example would be frequent RFC requests which reach your ABAP system and last only several hundred milliseconds. It is quite hard to trace such short-lived requests.

Maybe you also have to deal with a batch job that runs under another user, which always starts at a different time and aborts sporadically with a short dump. How can you trace something like this?

The ABAP Runtime Analysis (SE30) provides an answer. It lets you schedule a trace for any user on the current server.  

1. Start ABAP Runtime Analysis (SE30).
2. Create your trace variant and set aggregation to "None" again to get the Call Hierarchy.
3. Press "For User/Service" button in the "Schedule" area of the initial screen.
4. Press "Schedule measurement" button on the Overview of Scheduled Measurements screen.

The transaction presents a popup on which you can schedule an asynchronous trace according to these criteria:

• User
• Client
• External session (choose "Any" if you are not sure in which session the application will run!)
• Process Category (dialog, batch, RFC, HTTP, ITS, etc.)
• Object Type (transaction, report, function module, any, etc.)
• Object (e.g. only transaction se38)
• Max. No. of sched. Measurements (specify the maximum number of traces)
• Expiration Date and Time (specify the time frame. when the trace shall be active)

When the trace is scheduled, the ABAP Runtime Analysis automatically starts the trace as soon as session that meets your criteria is started on the system. The user you have specified logs on to the system and executes his task, and the ABAP Runtime Analysis starts to write the trace. The trace results can be analyzed - as usual - in the ABAP Runtime Analysis (using the "Evaluate" button on initial screen).

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/22575590/viewspace-625725/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/22575590/viewspace-625725/